DSM 7.0 Synology Package Center cannot be installed
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
@rednoah
I just installed them both without any problems, filebotnode opens as before, also gave the new internal user "Filebot" access to my download & media folder.
Now I will do some testing and report back.
I just installed them both without any problems, filebotnode opens as before, also gave the new internal user "Filebot" access to my download & media folder.
Now I will do some testing and report back.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
Follow up:
Filebot is running and I can open Filebotnode, however when pressing dry run / executing & scheduling is not working, I gues due the lack of admin rights?
On the Tools menu license/configure/help is working but system info not.
When activating license, I can select the license but when pressing activate I gues nothing happens.
Then did ssh to my NAS --> filebot --license "mylicensefile" (who was not in a directory who has FileBot internal user rights) and FileBot was activated.
Let me now if I can do some other tests.
Filebot is running and I can open Filebotnode, however when pressing dry run / executing & scheduling is not working, I gues due the lack of admin rights?
On the Tools menu license/configure/help is working but system info not.
When activating license, I can select the license but when pressing activate I gues nothing happens.
Then did ssh to my NAS --> filebot --license "mylicensefile" (who was not in a directory who has FileBot internal user rights) and FileBot was activated.
Let me now if I can do some other tests.
Last edited by Kopernikus on 21 Dec 2020, 09:43, edited 1 time in total.
Re: DSM 7.0 Synology Package Center cannot be installed
Yep, that just means that the app that is running inside your browser is served by DSM, but that app then can't connect to the node service running inside the NAS, which is expected since we can no longer install the reverse_proxy configuration ourselves.Kopernikus wrote: 21 Dec 2020, 09:19 Filebot is running and I can open Filebotnode, however when pressing dry run / executing & scheduling is not working, I gues due the lack of admin rights?
Since we cannot do the reverse_proxy configuration ourselves anymore due to limited permissions, we now have to rely on DSM APIs doing it for us, in some unknown pre-defined manner:
https://github.com/filebot/filebot-node ... f/resource
I'd start by checking if DSM has created nginx configuration files in the default location in response to installing our package:
Code: Select all
ls -l /usr/local/etc/nginx/conf.dCode: Select all
find / -name '*.conf' &2>/dev/null-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
I'd start by checking if DSM has created nginx configuration files in the default location in response to installing our package:Code: Select all
ls -l /usr/local/etc/nginx/conf.d
Code: Select all
Nico@KOPERNIKUS-NAS:/volume1/Drivers-Settings/Software license/FileBot$ ls -l /usr/local/etc/nginx/conf.d
total 36
drwxr-xr-x 2 root root 4096 Jun 6 2019 c76f017d-b2b4-4721-b4e3-a7cc03205b90
-rw-r--r-- 1 root root 122 Sep 29 11:34 dsm.filebot-node.conf
lrwxrwxrwx 1 root root 81 Dec 21 10:23 dsm.pkg-static.Docker-70163528.conf -> /usr/local/etc/nginx/conf.d-available/d44dc603-a33c- 4554-a012-02b3f6261cf9.w3conf
lrwxrwxrwx 1 root root 81 Dec 21 10:23 dsm.pkg-static.SynologyApplicationService-1255611987.conf -> /usr/local/etc/nginx/conf.d-av ailable/d5670998-384f-4bf7-96b3-085b4303b3ef.w3conf
lrwxrwxrwx 1 root root 81 Dec 21 10:23 dsm.ssdp.conf -> /usr/local/etc/nginx/conf.d-available/4742606b-98b6-4896-b2cf-a5d004639a3e .w3conf
lrwxrwxrwx 1 root root 81 Dec 21 10:23 dsm.syno-app-portal.FileStation.conf -> /usr/local/etc/nginx/conf.d-available/aac22f75-8816 -4a42-a5fa-3c1dcb472a32.w3conf
lrwxrwxrwx 1 root root 81 Dec 21 10:23 dsm.syno-app-portal.SynologyPhotos.conf -> /usr/local/etc/nginx/conf.d-available/cb08a435-0 3ad-4712-842b-5476cb609554.w3conf
lrwxrwxrwx 1 root root 81 Dec 21 10:23 dsm.syno-app-portal.Virtualization.conf -> /usr/local/etc/nginx/conf.d-available/e547ff23-d ac6-483e-8e4d-74887bca620d.w3conf
-rw-r--r-- 1 root root 0 Nov 27 10:29 events.origin.conf
-rw-r--r-- 1 root root 0 Nov 27 10:29 main.origin.conf
lrwxrwxrwx 1 root root 81 Dec 14 09:21 ssl.compress.conf -> /usr/local/etc/nginx/conf.d-available/24b93e1a-2596-4267-8ad7-0958bf64 ee3f.w3conf
Code: Select all
location /webman/3rdparty/filebot-node/ {
proxy_pass http://127.0.0.1:5452/;
proxy_set_header X-Real-IP $remote_addr;
}
Re: DSM 7.0 Synology Package Center cannot be installed
1.
dsm.filebot-node.conf has a suspicious Last-Modified date. Probably just a left-over from a previous installation on DSM 6.
If you uninstall FileBot Node, does this file disappear?
If you delete this file, and then install FileBot Node DSM7, is this file created anew?
2.
The logs might indicate if reverse_proxy configuration was done, or not, or if there was an error... or it might not, worth a try though:
dsm.filebot-node.conf has a suspicious Last-Modified date. Probably just a left-over from a previous installation on DSM 6.
2.
The logs might indicate if reverse_proxy configuration was done, or not, or if there was an error... or it might not, worth a try though:
Code: Select all
sudo cat /var/log/synopkg.logCode: Select all
sudo cat /var/log/packages/filebot-node.log-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
You where right it was a leftover from DSM6.rednoah wrote: 21 Dec 2020, 09:57 1.
dsm.filebot-node.conf has a suspicious Last-Modified date. Probably just a left-over from a previous installation on DSM 6.
If you uninstall FileBot Node, does this file disappear?
If you delete this file, and then install FileBot Node DSM7, is this file created anew?
2.
The logs might indicate if reverse_proxy configuration was done, or not, or if there was an error... or it might not, worth a try though:Code: Select all
sudo cat /var/log/synopkg.logCode: Select all
sudo cat /var/log/packages/filebot-node.log
Uninstalled Filbotnode, file still present, so I deleted it, reinstalled Filebotnode but no new file was created.
I'll do a search for .conf file in other locations and see if I can find something related to Filebotnode.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
The logs might indicate if reverse_proxy configuration was done, or not, or if there was an error... or it might not, worth a try though:Code: Select all
sudo cat /var/log/synopkg.log
Code: Select all
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin preinst
2020/12/21 11:04:03 install filebot-node 0.3.2 End preinst ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mkdir -p /volume1/@app store/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mkdir -p /volume1/@appst ore/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /volume1/@appst ore/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /volume1/@appstor e/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pk ginstall/extract.q5Fa2Y/package /volume1/@appstore/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkgi nstall/extract.q5Fa2Y/package /volume1/@appstore/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /var/packages/f ilebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /var/packages/fil ebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mkdir -p /var/packages /filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mkdir -p /var/packages/f ilebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/touch /var/packages/fi lebot-node/installing
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/touch /var/packages/file bot-node/installing ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pk ginstall/extract.q5Fa2Y/INFO /var/packages/filebot-node/INFO
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkgi nstall/extract.q5Fa2Y/INFO /var/packages/filebot-node/INFO ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /var/packages/f ilebot-node/scripts
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /var/packages/fil ebot-node/scripts ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pk ginstall/extract.q5Fa2Y/scripts /var/packages/filebot-node/scripts
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkgi nstall/extract.q5Fa2Y/scripts /var/packages/filebot-node/scripts ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /var/packages/f ilebot-node/conf
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /var/packages/fil ebot-node/conf ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pk ginstall/extract.q5Fa2Y/conf /var/packages/filebot-node/conf
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkgi nstall/extract.q5Fa2Y/conf /var/packages/filebot-node/conf ret=[0]
2020/12/21 11:04:03 Acquire systemd-unit for filebot-node when 0x0001 (ready)
2020/12/21 11:04:03 Acquire systemd-unit for filebot-node when 0x0001 (done)
2020/12/21 11:04:04 install filebot-node 0.3.2 Begin postinst
2020/12/21 11:04:04 install filebot-node 0.3.2 End postinst ret=[0]
2020/12/21 11:04:04 install filebot-node 0.3.2 successfully
2020/12/21 11:04:31 start filebot-node: begin to start version 0.3.2
2020/12/21 11:04:31 Acquire usr-local-linker for filebot-node when 0x0008 (ready )
2020/12/21 11:04:31 Acquire usr-local-linker for filebot-node when 0x0008 (done)
2020/12/21 11:04:31 start filebot-node 0.3.2 Begin start-stop-status start
2020/12/21 11:04:31 start filebot-node 0.3.2 End start-stop-status start ret=[0]
2020/12/21 11:04:32 start filebot-node: start version 0.3.2 successfully, result 0
Code: Select all
sudo cat /var/log/packages/filebot-node.log
Code: Select all
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin preinst
2020/12/21 11:04:03 install filebot-node 0.3.2 End preinst ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mkdir -p /volume1/@appstore/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mkdir -p /volume1/@appstore/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /volume1/@appstore/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /volume1/@appstore/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/package /volume1/@appstore/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/package /volume1/@appstore/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /var/packages/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /var/packages/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mkdir -p /var/packages/filebot-node
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mkdir -p /var/packages/filebot-node ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/touch /var/packages/filebot-node/installing
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/touch /var/packages/filebot-node/installing ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/INFO /var/packages/filebot-node/INFO
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/INFO /var/packages/filebot-node/INFO ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /var/packages/filebot-node/scripts
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /var/packages/filebot-node/scripts ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/scripts /var/packages/filebot-node/scripts
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/scripts /var/packages/filebot-node/scripts ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/rm -rf /var/packages/filebot-node/conf
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/rm -rf /var/packages/filebot-node/conf ret=[0]
2020/12/21 11:04:03 install filebot-node 0.3.2 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/conf /var/packages/filebot-node/conf
2020/12/21 11:04:03 install filebot-node 0.3.2 End /bin/mv -f /volume1/@tmp/pkginstall/extract.q5Fa2Y/conf /var/packages/filebot-node/conf ret=[0]
2020/12/21 11:04:04 install filebot-node 0.3.2 Begin postinst
2020/12/21 11:04:04 install filebot-node 0.3.2 End postinst ret=[0]
2020/12/21 11:04:31 start filebot-node 0.3.2 Begin start-stop-status start
2020/12/21 11:04:31 start filebot-node 0.3.2 End start-stop-status start ret=[0]
Re: DSM 7.0 Synology Package Center cannot be installed
Acquire usr-local-linker for filebot-node that suggests that we should see log entries for all our resource entries. But no log related to webservice / service / reverse_proxy / etc so I guess it's a dead end for now.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
I've found nothing either only a a file dsm.filebot-node.conf in var/tmp/nginx/test/plugin_config/conf.d but dated 29/9/2020 so I gues also a leftover of DSM6 (same content as posted above).
I think for the moment I will use Filebot as a command line tool, and run task through task manager I gues.
If you find anything I'll check this forum now and then so I can test.
I think for the moment I will use Filebot as a command line tool, and run task through task manager I gues.
If you find anything I'll check this forum now and then so I can test.
Re: DSM 7.0 Synology Package Center cannot be installed
You could try contacting Synology support. They might be able to tell us how reverse_proxy configuration is supposed to work on DSM 7.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
@rednoah
Did you already read the DSM7.0 developer guide?
https://global.download.synology.com/do ... 0_Beta.pdf
I saw your post on the community forum, also did a post in the DSM 7.0 beta discussion and made a support ticket with Synology.
I'll keep you informed.
Did you already read the DSM7.0 developer guide?
https://global.download.synology.com/do ... 0_Beta.pdf
I saw your post on the community forum, also did a post in the DSM 7.0 beta discussion and made a support ticket with Synology.
I'll keep you informed.
Re: DSM 7.0 Synology Package Center cannot be installed
Yep, that's the docs I'm looking at. In any case, I've ordered a DS120J for testing so maybe we can make some progress once I have my own test device.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
Cool thx.
I got an answer from Synology but nothing new, typical support people anwser:
"Since DSM7.0, we limited the permission of packages.
Packages will not be able to access the root permission due to security concerns.
We are sorry for this inconvenience."
You want me to ask something more detailled while ticket is still open?
I got an answer from Synology but nothing new, typical support people anwser:
"Since DSM7.0, we limited the permission of packages.
Packages will not be able to access the root permission due to security concerns.
We are sorry for this inconvenience."
You want me to ask something more detailled while ticket is still open?
Re: DSM 7.0 Synology Package Center cannot be installed
Well, their Developer documentation explicitly mentions a reverse_proxy service / web service / resource which is supposed to work without root permissions, and that seems to not quite work yet work as advertised for unknown reasons. You could ask them to forward the question to a developer so that you might get a technical answer and not a canned response.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
Ok, I'll keep you informed.
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
I got this answer from Synology:rednoah wrote: 23 Dec 2020, 09:49 Well, their Developer documentation explicitly mentions a reverse_proxy service / web service / resource which is supposed to work without root permissions, and that seems to not quite work yet work as advertised for unknown reasons. You could ask them to forward the question to a developer so that you might get a technical answer and not a canned response.
"Hi Customer,
Thank you for contacting Synology support.
Would you please provide us the document you saw about this statement?
"According to the DSM7.0 developer documentation wich explicitly mentions a reverse_proxy service / web service / resource which is supposed to work without root permissions"
I could double confirm it with developers."
What should I answer?
Re: DSM 7.0 Synology Package Center cannot be installed
DSM_Developer_Guide_7_0_Beta.pdf ➔ Section 1.7.4.4.11 ➔ Page 125 ➔ reverse_proxy service
https://global.download.synology.com/do ... 0_Beta.pdf
https://global.download.synology.com/do ... 0_Beta.pdf
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
Ok, thx.
Replied to them with the given info, I'll keep you informed.
Btw, happy holidays!
Replied to them with the given info, I'll keep you informed.
Btw, happy holidays!
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
Merry x-mas!
Got an answer from Synology:
Developers have installed filebot and filebot-node in DSM6.2 but they cannot see request "webservice" in resouces.
Since you have mentioned this could work before, would you please provide us more detailed info?
The version of filebot is 4.9.2 and filebot-node is 0.3.1.
Got an answer from Synology:
Developers have installed filebot and filebot-node in DSM6.2 but they cannot see request "webservice" in resouces.
Since you have mentioned this could work before, would you please provide us more detailed info?
The version of filebot is 4.9.2 and filebot-node is 0.3.1.
Re: DSM 7.0 Synology Package Center cannot be installed
We have a DSM 7.0 package (FileBot Node 0.3.2) here:
https://github.com/filebot/filebot-node ... /tag/0.3.2
And it's using the resource config here:
https://github.com/filebot/filebot-node ... f/resource
The main question is:
* Where does DSM create the corresponding nginx configuration file?
https://github.com/filebot/filebot-node ... /tag/0.3.2
And it's using the resource config here:
https://github.com/filebot/filebot-node ... f/resource
The main question is:
* Where does DSM create the corresponding nginx configuration file?
-
keepwalking
- Posts: 3
- Joined: 09 Dec 2020, 12:53
Re: DSM 7.0 Synology Package Center cannot be installed
How do you use the "user-defined script" when editing this task for the filebot to run? I mean, I think I know what attributes to use for the AMC to work, but how do you get to the filebot program and execute it from the task manager?Kopernikus wrote: 21 Dec 2020, 10:41 I think for the moment I will use Filebot as a command line tool, and run task through task manager I gues.
Would you mind sharing how your "user-defined script" is?
Mine is still from the DSM 6 version and since updating to the new DSM 7 filebot node version it does not work anymore, but it still is: "/usr/local/filebot-node/task 10"
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
Quite simple, make sure Filebot is working, then with an editor make a file "name".sh put in there your filebot command, go to Synology task manager and make the script run when you want.keepwalking wrote: 25 Dec 2020, 15:53How do you use the "user-defined script" when editing this task for the filebot to run? I mean, I think I know what attributes to use for the AMC to work, but how do you get to the filebot program and execute it from the task manager?Kopernikus wrote: 21 Dec 2020, 10:41 I think for the moment I will use Filebot as a command line tool, and run task through task manager I gues.
Would you mind sharing how your "user-defined script" is?
Mine is still from the DSM 6 version and since updating to the new DSM 7 filebot node version it does not work anymore, but it still is: "/usr/local/filebot-node/task 10"
-
Kopernikus
- Posts: 34
- Joined: 03 Feb 2019, 20:07
Re: DSM 7.0 Synology Package Center cannot be installed
@rednoah
So here's a link to a screenshot of the answer: https://1drv.ms/u/s!ArQhL4LigQi2kK4yocp ... A?e=U5G0Ci
Otherwise give me your email adress and I email it to you.
I got an answer from Synology, but I can't paste it here or send it by PM, the forum gives me internal server error (think because it contains chinese characters).rednoah wrote: 25 Dec 2020, 08:30 We have a DSM 7.0 package (FileBot Node 0.3.2) here:
https://github.com/filebot/filebot-node ... /tag/0.3.2
And it's using the resource config here:
https://github.com/filebot/filebot-node ... f/resource
The main question is:
* Where does DSM create the corresponding nginx configuration file?
So here's a link to a screenshot of the answer: https://1drv.ms/u/s!ArQhL4LigQi2kK4yocp ... A?e=U5G0Ci
Otherwise give me your email adress and I email it to you.
-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
Is there any news? I would like to use FileBot again on my NAS. So far I understand it does still work but only the GUI doesn't work? I reinstalled the program so my previous tasks are probably gone. What is the best way to get up and running again?
Re: DSM 7.0 Synology Package Center cannot be installed
DSM 7 beta build for FileBot is available here:
https://get.filebot.net/filebot/BETA/
DSM 7 beta build for FileBot Node is now available here:
https://github.com/filebot/filebot-node ... /tag/0.3.2
https://get.filebot.net/filebot/BETA/
DSM 7 beta build for FileBot Node is now available here:
https://github.com/filebot/filebot-node ... /tag/0.3.2
Re: DSM 7.0 Synology Package Center cannot be installed
Thansk RedNoah
Going to try to install it now
Going to try to install it now
Re: DSM 7.0 Synology Package Center cannot be installed
Tried to install 4.9.3 OVER 4.9.2 it failed
uninstalled 4.9.2 and install 4.9.3 status is RUNNING
Installed filebot node 0.3.2 OVER the 0.3.1 without issue
Opened file bot not pop out in a new tab port 5452 with same IP (should not it be in a windows inside the DSM 7 ?)
I could set my preferences, like paths, naming conventions
I loaded my licence
I can see now there is a menu "tools ->configure" for open subtitle credentials
Closed that tab, reopen firlebot node everything looks like there
click execute nothing, apparently (in the tasks low part of the screen), going to look for the logs
uninstalled 4.9.2 and install 4.9.3 status is RUNNING
Installed filebot node 0.3.2 OVER the 0.3.1 without issue
Opened file bot not pop out in a new tab port 5452 with same IP (should not it be in a windows inside the DSM 7 ?)
I could set my preferences, like paths, naming conventions
I loaded my licence
I can see now there is a menu "tools ->configure" for open subtitle credentials
Closed that tab, reopen firlebot node everything looks like there
click execute nothing, apparently (in the tasks low part of the screen), going to look for the logs
Re: DSM 7.0 Synology Package Center cannot be installed
Oups forgot I dont have JAVA (from RedNoah) installed doing it now
-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
First of all, thanks for releasing a new version. I've installed the new versions on my NAS (DS218+). I did a full reinstall of everything including your java package. Java is confirmed installed and FileBot commands work in the SSH teminal and it has permissions configured to access the folders. But for some reason FileBot node isn't doing anything. The console stays empty no matter where I click. Is it confirmed working on your NAS?
EDIT:
I found that the GUI is trying to retrieve the information from a JS file but it gets a 401 unauthorized error https://prnt.sc/x4eo7x
EDIT:
I found that the GUI is trying to retrieve the information from a JS file but it gets a 401 unauthorized error https://prnt.sc/x4eo7x
Last edited by peppershade on 18 Jan 2021, 11:26, edited 1 time in total.
Re: DSM 7.0 Synology Package Center cannot be installed
What does the filebot-node.log say? What does the network console (i.e. Chrome ➔ View ➔ Developer ➔ Developer Console) inside your browser say?
-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
There is nothing in the log but I did find that the app.js is not accessible and gives a 401 (Unauthorized) error on load and when executing a task.
Here is a more detailed screenshot of the network tab: https://prnt.sc/x4fmvd
Here is a more detailed screenshot of the network tab: https://prnt.sc/x4fmvd
Last edited by peppershade on 18 Jan 2021, 11:36, edited 1 time in total.
Re: DSM 7.0 Synology Package Center cannot be installed
1.
There is always something in the log. Because it'll print something on startup.
2.
401 Unauthorized likely means that the node service is generally running, but somehow Synology DSM login integration doesn't work. If you login into DSM, then those session cookies should allow you to use FileBot Node. It works for me. Let's see if it works for other random users, or not.
There is always something in the log. Because it'll print something on startup.
2.
401 Unauthorized likely means that the node service is generally running, but somehow Synology DSM login integration doesn't work. If you login into DSM, then those session cookies should allow you to use FileBot Node. It works for me. Let's see if it works for other random users, or not.
Re: DSM 7.0 Synology Package Center cannot be installed
at my place error report isrednoah wrote: 18 Jan 2021, 11:23 What does the filebot-node.log say? What does the network console (i.e. Chrome ➔ View ➔ Developer ➔ Developer Console) inside your browser say?
Code: Select all
Failed to load resource: the server responded with a status of 401 (Unauthorized)
:5452/version?_dc=1610969692048:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
app.js?_dc=20210118153103:1 Uncaught RangeError: Maximum call stack size exceeded
at RegExp.exec (<anonymous>)
at RegExp.[Symbol.replace] (<anonymous>)
at String.replace (<anonymous>)
at Object.encodeString (app.js?_dc=20210118153103:1)
at Object.doEncode [as encodeValue] (app.js?_dc=20210118153103:1)
at encodeObject (app.js?_dc=20210118153103:1)
at Object.doEncode [as encodeValue] (app.js?_dc=20210118153103:1)
at encodeObject (app.js?_dc=20210118153103:1)
at Object.doEncode [as encodeValue] (app.js?_dc=20210118153103:1)
at encodeObject (app.js?_dc=20210118153103:1)
encodeString @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
XMLHttpRequest.send (async)
start @ app.js?_dc=20210118153103:1
request @ app.js?_dc=20210118153103:1
dispatchRequest @ app.js?_dc=20210118153103:1
requestVersion @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
fire @ app.js?_dc=20210118153103:1
doFireEvent @ app.js?_dc=20210118153103:1
b.doFireEvent @ app.js?_dc=20210118153103:1
fireEventArgs @ app.js?_dc=20210118153103:1
fireEvent @ app.js?_dc=20210118153103:1
success @ app.js?_dc=20210118153103:1
callback @ app.js?_dc=20210118153103:1
onComplete @ app.js?_dc=20210118153103:1
onStateChange @ app.js?_dc=20210118153103:1
g @ app.js?_dc=20210118153103:1
XMLHttpRequest.send (async)
start @ app.js?_dc=20210118153103:1
request @ app.js?_dc=20210118153103:1
dispatchRequest @ app.js?_dc=20210118153103:1
requestAuth @ app.js?_dc=20210118153103:1
init @ app.js?_dc=20210118153103:1
launch @ app.js?_dc=20210118153103:1
onBeforeLaunch @ app.js?_dc=20210118153103:1
onBeforeLaunch @ app.js?_dc=20210118153103:1
onProfilesReady @ app.js?_dc=20210118153103:1
constructor @ app.js?_dc=20210118153103:1
constructor @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
invoke @ app.js?_dc=20210118153103:1
doInvokeAll @ app.js?_dc=20210118153103:1
invokeAll @ app.js?_dc=20210118153103:1
handleReady @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
setTimeout (async)
defer @ app.js?_dc=20210118153103:1
handleReadySoon @ app.js?_dc=20210118153103:1
fireReady @ app.js?_dc=20210118153103:1
doReadyEvent @ app.js?_dc=20210118153103:1
onReadyEvent @ app.js?_dc=20210118153103:1
load (async)
bind @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
(anonymous) @ app.js?_dc=20210118153103:1
Show 170 more frames
:5452/state?_dc=1610969692048:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
app.js?_dc=20210118153103:1 Uncaught RangeError: Maximum call stack size exceeded
at RegExp.exec (<anonymous>)
at RegExp.[Symbol.replace] (<anonymous>)
at String.replace (<anonymous>)
at Object.encodeString (app.js?_dc=20210118153103:1)
at Object.doEncode [as encodeValue] (app.js?_dc=20210118153103:1)
at encodeObject (app.js?_dc=20210118153103:1)
at Object.doEncode [as encodeValue] (app.js?_dc=20210118153103:1)
at encodeObject (app.js?_dc=20210118153103:1)
at Object.doEncode [as encodeValue] (app.js?_dc=20210118153103:1)
at encodeObject (app.js?_dc=20210118153103:1)
encodeString @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1
doEncode @ app.js?_dc=20210118153103:1
encodeObject @ app.js?_dc=20210118153103:1-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
I normally use a reverse proxy for my NAS, but that don't seem to work at all and the page doesn't even load. Now I opened a incognito browser tab and logged in locally by ip on port 5000, but that still doesn't work.
Re: DSM 7.0 Synology Package Center cannot be installed
That's just random ExtJS logging caused the 401 Unauthorized response. We'll want to look at the filebot-node.log on the server-side.
i.e. SSH into NAS and then run:
i.e. SSH into NAS and then run:
Code: Select all
sudo cat /var/packages/filebot-node/target/filebot-node.log-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
This is what i get. The authenticate.cgi is almost endless in the file
Code: Select all
ENVIRONMENT {
FILEBOT_CMD: 'filebot',
MAX_DB_CONNECTIONS: '10',
SYNOPKG_PKGVAR: '/volume1/@appdata/filebot-node',
SYNOPKG_USERNAME: '[REDACTED]',
OLDPWD: '/',
SYNOPKG_PKGNAME: 'filebot-node',
SYNOPKG_DSM_VERSION_MAJOR: '7',
JAVA_OPTS: '',
FILEBOT_CMD_GID: '106247',
SYNOPKG_PKGHOME: '/volume1/@apphome/filebot-node',
USER: 'FileBot',
SYNOPKG_DSM_VERSION_MINOR: '0',
SYNOPKG_PKGTMP: '/volume1/@apptemp/filebot-node',
SYNOPKG_DSM_VERSION_BUILD: '41222',
SELF: 'filebot-node',
PWD: '/var/packages/filebot-node/target',
SYNOPKG_TEMP_REPLACE_FOLDER: '/volume1/@tmp/synopkg.tmp/filebot-node',
SYNOPKG_PKGVER: '0.3.2',
FILEBOT_NODE_DATA: '/var/packages/filebot-node/var',
SYNOPKG_DSM_LANGUAGE: 'enu',
SYNOPKG_DSM_ARCH: 'apollolake',
SYNOPKG_PKG_PROGRESS_PATH: '/tmp/install_progress_filebot-node',
FILEBOT_NODE_HTTP: 'YES',
FILEBOT_NODE_AUTH: 'SYNO',
FILEBOT_NODE_CLIENT: 'client',
SYNOPKG_PKGDEST_VOL: '/volume1',
FILEBOT_TASK_CMD: 'filebot-node-task',
SHLVL: '3',
CPU_COUNT: '10',
FILEBOT_CMD_CWD: '/volume1',
SYNOPKG_PKG_STATUS: 'INSTALL',
PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
FILEBOT_NODE_HOST: '0.0.0.0',
FILEBOT_NODE_HTTP_PORT: '5452',
FILEBOT_CMD_UID: '106247',
SYNOPKG_TEMP_LOGFILE: '/tmp/synopkgmgr.log-filebot-node',
SYNOPKG_PKGDEST: '/volume1/@appstore/filebot-node',
_: '/usr/local/bin/node'
}
USER { UID: 106247, GID: 106247 }
filebot-node listening at http://0.0.0.0:5452/
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=HInshTKABUO6NjT0ewwk6CqaqkoON7eAFyxR8zZ64zIcQOykUXk1LJYsK6AImRvfCJ2bPiPDJIn2Yo2rfz_a8A; _ga=GA1.1.115015009.1600765903; organizrLanguage=en; _CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; stay_login=0; did=c08hkIzBG6N9vH-fv1QBDzgFjQAAlO9NW8cYcyAzbUNekLEOqTfIDGy1AQtSOkNJ_PHPyH_qFMYIGb5Om_oMbw; compact_display_state=true',
REMOTE_ADDR: '192.168.69.7'
}
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=HInshTKABUO6NjT0ewwk6CqaqkoON7eAFyxR8zZ64zIcQOykUXk1LJYsK6AImRvfCJ2bPiPDJIn2Yo2rfz_a8A; _ga=GA1.1.115015009.1600765903; organizrLanguage=en; _CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; stay_login=0; did=c08hkIzBG6N9vH-fv1QBDzgFjQAAlO9NW8cYcyAzbUNekLEOqTfIDGy1AQtSOkNJ_PHPyH_qFMYIGb5Om_oMbw; compact_display_state=true',
REMOTE_ADDR: '192.168.69.7'
}
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=HInshTKABUO6NjT0ewwk6CqaqkoON7eAFyxR8zZ64zIcQOykUXk1LJYsK6AImRvfCJ2bPiPDJIn2Yo2rfz_a8A; _ga=GA1.1.115015009.1600765903; organizrLanguage=en; _CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; stay_login=0; did=c08hkIzBG6N9vH-fv1QBDzgFjQAAlO9NW8cYcyAzbUNekLEOqTfIDGy1AQtSOkNJ_PHPyH_qFMYIGb5Om_oMbw; compact_display_state=true',
REMOTE_ADDR: '192.168.69.7'
}
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=HInshTKABUO6NjT0ewwk6CqaqkoON7eAFyxR8zZ64zIcQOykUXk1LJYsK6AImRvfCJ2bPiPDJIn2Yo2rfz_a8A; _ga=GA1.1.115015009.1600765903; organizrLanguage=en; _CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; stay_login=0; did=c08hkIzBG6N9vH-fv1QBDzgFjQAAlO9NW8cYcyAzbUNekLEOqTfIDGy1AQtSOkNJ_PHPyH_qFMYIGb5Om_oMbw; compact_display_state=true',
REMOTE_ADDR: '192.168.69.7'
}
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=HInshTKABUO6NjT0ewwk6CqaqkoON7eAFyxR8zZ64zIcQOykUXk1LJYsK6AImRvfCJ2bPiPDJIn2Yo2rfz_a8A; _ga=GA1.1.115015009.1600765903; organizrLanguage=en; _CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; stay_login=0; did=c08hkIzBG6N9vH-fv1QBDzgFjQAAlO9NW8cYcyAzbUNekLEOqTfIDGy1AQtSOkNJ_PHPyH_qFMYIGb5Om_oMbw; compact_display_state=true',
REMOTE_ADDR: '192.168.69.7'
}
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=HInshTKABUO6NjT0ewwk6CqaqkoON7eAFyxR8zZ64zIcQOykUXk1LJYsK6AImRvfCJ2bPiPDJIn2Yo2rfz_a8A; _ga=GA1.1.115015009.1600765903; organizrLanguage=en; _CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; stay_login=0; did=c08hkIzBG6N9vH-fv1QBDzgFjQAAlO9NW8cYcyAzbUNekLEOqTfIDGy1AQtSOkNJ_PHPyH_qFMYIGb5Om_oMbw; compact_display_state=true',
REMOTE_ADDR: '192.168.69.7'
}Re: DSM 7.0 Synology Package Center cannot be installed
It says multiple timesrednoah wrote: 18 Jan 2021, 11:42 That's just random ExtJS logging caused the 401 Unauthorized response. We'll want to look at the filebot-node.log on the server-side.
i.e. SSH into NAS and then run:Code: Select all
sudo cat /var/packages/filebot-node/target/filebot-node.log
Code: Select all
fxgxWyPVM; io=AAPduyISLS-uXQHEAAAB',
REMOTE_ADDR: '192.168.1.15'
}
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: 'smid=9z3mz2DVafzJRUjQFWJoCZY8u9qQKzmSkewSVpGINdT8NZUkzo_wCwIo6OGGohk1mfWHe9lajkizxAdMtMP6Ww; _CrPoSt=aHR0cDovLzE5Mi4xNjguMS4xMDo1MDAwLw%3D%3D; did=sr7NOx-2xs4V36sEzNpxeT89f9c_esV1EAVp-4SWL6EVAjbQYu4CFDbZ_KWkeImUQv6CNbUdwwfHrFZNfnac3w; _SSID=AK_aOphJITd0skNvjSGAcHjVnuOy08NeQ9J2SRNMFSw; stay_login=0; id=KCX3N3fhtKJMP0NwddL47R0jqxZuG8S6Yk-pE5moGbU7VGp_OxKmu7S8d_OB0hUJ2vugJvlYtb2esfxgxWyPVM; io=AAPduyISLS-uXQHEAAAB',
REMOTE_ADDR: '192.168.1.15'Re: DSM 7.0 Synology Package Center cannot be installed
Strange. The HTTP_COOKIE should be all it needs.
Please open this in your browser to see if your DSM 7 still uses SynoToken for CSRF mitigation:
Please open this in your browser to see if your DSM 7 still uses SynoToken for CSRF mitigation:
Code: Select all
http://<IP>:5000/webman/login.cgi-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
This is the response
This is the latest log in filebot node
Code: Select all
{ "SynoToken" : "[REDACTED]", "result" : "success", "success" : true }Code: Select all
/usr/syno/synoman/webman/modules/authenticate.cgi
{
HTTP_COOKIE: '_CrPoSt=aHR0cDovLzE5Mi4xNjguNjkuMzo1MDAwLw%3D%3D; _SSID=IFRLXrNOxCUEvgcH1oGXxwQoOiDLn159Ykp7uMYhdnw; did=wQ7oYN0itytTmd5_6Ecu3YaixDvpkFvAnmwKCwRrTjEeopbaWhF5Z90OqdubUBe5cHWQX6cTDzz1Sg8lw94-nQ; id=g3tuYjxa6rISvlRd-m1GCBdxAFasIhxh9XUKeJHVQiIm8mvrE4Lrc_7-FGjhj_P2NUWgmr0fbYZ24ty0kjUvzc; io=74NtEKPZzz254uRWAAAF',
REMOTE_ADDR: '192.168.69.7'
}
Last edited by peppershade on 18 Jan 2021, 12:02, edited 1 time in total.
Re: DSM 7.0 Synology Package Center cannot be installed
That might explain things. Try disabling Improve protection against cross-site request forgery attacks in the Security settings to see if that makes a difference. (NOTE: might require restart and relogin)peppershade wrote: 18 Jan 2021, 11:56 This is the response
Code: Select all
{ "SynoToken" : "lnv2GsnftC5mY", "result" : "success", "success" : true }
-
peppershade
- Posts: 7
- Joined: 16 Jan 2021, 18:39
Re: DSM 7.0 Synology Package Center cannot be installed
It seems to work!
I'm going to test it now
Edit: Confirmed working! Thank you very much for the support
Edit: Confirmed working! Thank you very much for the support
Re: DSM 7.0 Synology Package Center cannot be installed
Yes needs to logoff and login again after disabling the security feature and work at my place toorednoah wrote: 18 Jan 2021, 12:00
That might explain things. Try disabling Improve protection against cross-site request forgery attacks in the Security settings to see if that makes a difference. (NOTE: might require restart and relogin)
thanks a lot for that work, truly appreciated, will do an additional donation.
For the diverse tools I am using on my synology, you are the first one with a functional software on DSM 7 !!
Re: DSM 7.0 Synology Package Center cannot be installed
@RedNoah
Argh, no it is not picking anything there is a "Permission denied" issue
I am using my account with full admin rights to enter.
I use the same account to map that [Dawnloads_raw] to my pc for example
I tried in SSH to delete a file with that same account without any issue
found the solution !!
right click on the shared folder where the file are present / where filebot is looking at (in my case it is a shared forlder called /volume2/Downloads_raw) -->Tab Permission
Filebot was not there, so -->Create -> User or group select Filebot, Type -> Allow , Apply to ->All
then below select read and write permissions, click done and then save (filebot is now on the list for who got the permission)
do it again for where the files are going to be moved and stored (in my case it is a shared folder called /volume2/Video)
for the record and google search engine the error looked like that:
Argh, no it is not picking anything there is a "Permission denied" issue
I am using my account with full admin rights to enter.
I use the same account to map that [Dawnloads_raw] to my pc for example
I tried in SSH to delete a file with that same account without any issue
found the solution !!
right click on the shared folder where the file are present / where filebot is looking at (in my case it is a shared forlder called /volume2/Downloads_raw) -->Tab Permission
Filebot was not there, so -->Create -> User or group select Filebot, Type -> Allow , Apply to ->All
then below select read and write permissions, click done and then save (filebot is now on the list for who got the permission)
do it again for where the files are going to be moved and stored (in my case it is a shared folder called /volume2/Video)
for the record and google search engine the error looked like that:
Code: Select all
filebot -script 'fn:amc' /volume2/Downloads_raw --output /volume2/Video --action move -non-strict --order Airdate --conflict auto --lang en --def 'music=y' 'unsorted=y' 'clean=y' 'deleteAfterExtract=y' 'seriesFormat=Series/{ny}/{episode.special ? '\''Special'\'' : '\''Season '\''+s}/{n}-({y})-{episode.special ? '\''S00E'\''+special.pad(2) : s00e00}-{t}-Audio {audio.language}' 'animeFormat=Anime/{n}.{y}.{order.airdate.s00e00}.#{absolute}.{t}.[{airdate}]' 'movieFormat=Movies/{collection+'\''/'\''}{n.sortName('\''$2, $1'\'')}.{y}.{vf}.{vc}.{ac}.[{bitdepth}] bit.{audio.language}' 'musicFormat=Music/{n}/{album+'\''/'\''}{artist} - {album} - CD{media.PartPosition} - {pi.pad(2)} - {t}' --apply refresh --log all --log-file '/var/packages/filebot-node/var/filebot.log'
------------------------------------------
Run script [fn:amc] at [Mon Jan 18 14:49:37 CET 2021]
Parameter: music = y
Parameter: unsorted = y
Parameter: clean = y
Parameter: deleteAfterExtract = y
Parameter: seriesFormat = Series/{ny}/{episode.special ? 'Special' : 'Season '+s}/{n}-({y})-{episode.special ? 'S00E'+special.pad(2) : s00e00}-{t}-Audio {audio.language}
Parameter: animeFormat = Anime/{n}.{y}.{order.airdate.s00e00}.#{absolute}.{t}.[{airdate}]
Parameter: movieFormat = Movies/{collection+'/'}{n.sortName('$2, $1')}.{y}.{vf}.{vc}.{ac}.[{bitdepth}] bit.{audio.language}
Parameter: musicFormat = Music/{n}/{album+'/'}{artist} - {album} - CD{media.PartPosition} - {pi.pad(2)} - {t}
Argument[0]: /volume2/Downloads_raw
Permission denied: /volume2/Downloads_raw
Permission denied: /volume2/Downloads_raw
No files selected for processing
Done ¯\_(ツ)_/¯
------------------------------------------
[Process completed]