DSM 7.0 Synology Package Center cannot be installed

[Kopernikus]

@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.

[Kopernikus]

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.

[rednoah]

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?

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.

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.d

or perhaps somewhere else:

Code: Select all

find / -name '*.conf' &2>/dev/null

[Kopernikus]

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

Content of dsm.filebot-node.conf:

Code: Select all

location /webman/3rdparty/filebot-node/ {
	proxy_pass http://127.0.0.1:5452/;
	proxy_set_header X-Real-IP $remote_addr;
}

[rednoah]

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.log

Code: Select all

sudo cat /var/log/packages/filebot-node.log

[Kopernikus]

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.log

Code: Select all

sudo cat /var/log/packages/filebot-node.log

You where right it was a leftover from DSM6.
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]

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]

[rednoah]

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]

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.

[rednoah]

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]

@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.

[rednoah]

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]

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?

[rednoah]

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]

Ok, I'll keep you informed.

[Kopernikus]

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.

I got this answer from Synology:

"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?

[rednoah]

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

[Kopernikus]

Ok, thx.
Replied to them with the given info, I'll keep you informed.
Btw, happy holidays!

[Kopernikus]

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.

[rednoah]

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?

[keepwalking]

I think for the moment I will use Filebot as a command line tool, and run task through task manager I gues.

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?

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]

I think for the moment I will use Filebot as a command line tool, and run task through task manager I gues.

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?

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"

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.

[Kopernikus]

@rednoah

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?

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).
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]

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?

[rednoah]

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