can't open filebot node in web ui

[leeeunchang]

my filebot node opens normally on synology dsm

but when i try open it in chrome

like this https://xxx.synology.me:5452

it shows nothing..

and when i connect reverse proxy
through the web
it only shows "Not Found" .

what should i do ?

[rednoah]

Are you using the FileBot Node package?
https://www.filebot.net/linux/syno.html


Are you using the FileBot Node docker container?
https://www.filebot.net/linux/docker.html


Are you trying to access your Synology DSM from outside the local network?


Does https://xxx.synology.me:5452 work from inside the local network?




Note that the FileBot Node package for Synology does not run on a separate port, and is served by DSM itself, which makes it remotely accessible just like DSM:

Code: Select all

http://<IP>:5000/webman/3rdparty/filebot-node/index.html

If an iframe works in DSM, then you can use Right-Click ➔ View Frame Source to check the standalone URL.




Making your DSM remotely accessible from the internet is probably not a good idea security-wise. I would VPN into your local network, and then everything will work as if you were physically there.

[leeeunchang]

Are you using the FileBot Node package?
https://www.filebot.net/linux/syno.html

yes. I am using filebot node package

Are you using the FileBot Node docker container?
https://www.filebot.net/linux/docker.html

nope i am using filebot node synology package

Are you trying to access your Synology DSM from outside the local network?

yes i am trying to open dsm remotely.

Does https://xxx.synology.me:5452 work from inside the local network?

not tried it inside. i am in the office. i will try it after work and tell you later.

thank you for your reply.

[rednoah]

If you're using the Synology package, then you can only use FileBot Node via the Synology DSM WebUI. You can of course open the iframe directly in a new tab of course if you want it as a separate fullscreen window, there's technically no difference really, akin to "Open Image in New Tab", but that only works if you already have valid login cookies, i.e. logged into the Synology DSM WebUI already with persistent login cookies stored and sent by your browser with each request.


The FileBot Node server-side service is indeed running on 127.0.0.1:5452 but that's just an internal implementation detail, and the internal node service is notably only accessible from the DSM host itself, and exposed to the network only via the Synology DSM WebUI akin to how a reverse proxy works.

[leeeunchang]

https://xxx.synology.me:5452 and 192.168.0.5:5452 do not work from inside the local network.
http://<IP>:5000/webman/3rdparty/filebot-node/index.html <--- this works from inside and outside.
inside https://192.168.0.5:5001/webman/3rdpart ... index.html
outside https://xxx.synology.me:5001/webman/3rd ... index.html

thank you so much~

but i don't know how to open iframe in a new tab.
and is there any simple way to open filebot node in shorter address with reverse proxy like "https://filebot.xxx.synology.me" ?
Please let me know rednoah. thank you~

If you're using the Synology package, then you can only use FileBot Node via the Synology DSM WebUI. You can of course open the iframe directly in a new tab of course if you want it as a separate fullscreen window, there's technically no difference really, akin to "Open Image in New Tab", but that only works if you already have valid login cookies, i.e. logged into the Synology DSM WebUI already with persistent login cookies stored and sent by your browser with each request.


The FileBot Node server-side service is indeed running on 127.0.0.1:5452 but that's just an internal implementation detail, and the internal node service is notably only accessible from the DSM host itself, and exposed to the network only via the Synology DSM WebUI akin to how a reverse proxy works.

[rednoah]

is there any simple way to open filebot node in shorter address with reverse proxy like "https://filebot.xxx.synology.me" ?

No simple way for sure. You'd have to ask Synology Support engineers if DSM even allows for that. Maybe if you run a custom FileBot Node in a docker container, with custom authentication, custom HTTPS certs, custom reverse proxy or DNS entries, etc.


I would imagine that Synology DSM login cookies are limited to the exact domain (but did not check to confirm; ask Synology) so Synology FileBot Node almost certainly wouldn't work because your browser wouldn't be sending login cookies along to subdomain requests:
https://stackoverflow.com/questions/184 ... and-domain