Hi folks,
I need to do a lot of catching up from other discussions, but first I need to finish an issue with my overal Node-RED setup...
I need to setup a (Tailscale) reverse proxy that exposes Node-RED at some path "my_root". So when I navigate to http(s)://my_host_name/my_root
, the Node-RED flow editor should be displayed.
Since I am by far a specialist about this kind of thing, I would really appreciate if somebody could enlighten me!
First attempt - without httpAdminRoot
So the flow editor runned originally at the base path. Which means I configured my reverse proxy like this:
http://my_host_name/my_root --> http://localhost:1880
When I navigate to http://my_host_name/my_root
the Node-RED html page is being fetched from the base path (http://localhost:1880) without problems:
However none of the other files can be found, because those requests go to the base path of my proxy (http://my_host_name/red/...
), while my proxy is listening only to requests to my_root (http://my_host_name/my_root/red/...
):
So the proxy has no idea what to do with those requests.
Second attempt - with httpAdminRoot
Since Node-RED should get all these files from my_root to solve this, I thought I should adjust the httpAdminRoot in my settings.js file:
When I navigate now to http://my_host_name/my_root
the Node-RED html page cannot be fetched anymore, since that is now being served at my_root:
So I thought that I could solve this by changing my reverse proxy, so that I get redirected to my_root (where the html is being served):
http://my_host_name/my_root --> http://localhost:1880/my_root
And then indeed I can fetch the Node-RED html page from my_root, but the other files still cannot be fetched:
For some reason those files are NOT being fetched from http://my_host_name/my_root/red/...
but from the base path ( http://my_host_name/red/...
). I thought that all files would be served under httpAdminRoot?
Thanks for reading!!
Bart