Let's all have a good laugh at my expense...
when I access my URL at nodered.foo.bar (no port), the router forwards port 1880 for me. but leaves websockets in the dust.
when I access my URL at nodered.foo.bar:1880, well all the debug shows up.
I suppose I can live with that workaround and the embarassment of overlooking it.
More laughing:
I totally forgot I was using caddy to handle my multiple subdomains and ports. This is what happens when my documentation guy is on vacation 100% of the time.
I simply added "websocket" to the correct domain's proxy line and debug info started showing up.
thank you for joining me on my journey. please remember where you parked.
2 Likes
On my setup. Pi4, Node-Red, viewing from Mac. Safari and Chrome no debug output. Firefox seems ok.
Hi, you really need to create a new thread if you want some help. This is a 2yo thread with an existing solution.
If there is a difference between browsers, use the console in your browser dev tools to see what errors are being produced. But please expand in a different thread if you want some help.