-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dashboard 2.0 behind reverse proxy (nginx) #1612
Comments
Hello @WoMec I have this (I have just migrated to 2.0 this week) in my nginx.conf file (using docker-compose) and I have it working (in future I want to leave location at '/'). (see at bottom) But THIRD PARTY NODES are NOT working. I get this errores in browser console
@bartbutenaers do uou know if this is a "problem" of all third party nodes or a general "problem" of Dashboard 2.0?
|
This may be the same problem #1024 |
In my humble opinion, I think nowadays working with docker and nignx is a must. What do you think? Does it have a easy solution? |
@ortegafernando how are you installing your third-party nodes? Via the palette manager? or as global installs? |
@joepavitt By pallete manager. If you need any log or something from me, please ask me |
@ortegafernando if you have a look at #1615 I think I have found the problem. If you setup httpAdminRoot to 'nr' and then proxy /nr to http://nodered:1880/nr/ then I think that may provide a workaround. That is if I understand the nginx config correctly. |
Hi,
I am trying to set up a reverse proxy with Nginx for the new Node-RED Dashboard 2.0. Previously, with Dashboard 1.0, I was able to access the dashboard easily by configuring Nginx to route requests based on the device's IP address or FQDN.
I would like to achieve the same setup for Dashboard 2.0, but I am facing issues with WebSocket connections. It seems that my Nginx configuration is not handling WebSockets correctly, and the dashboard does not work as expected.
Could you provide guidance on the correct Nginx configuration to ensure WebSocket support for Dashboard 2.0?
Thanks!
The text was updated successfully, but these errors were encountered: