dolivas27

I have updated to the latest and still have the errors anything else I can check?

@Djoss Thanks for the update very much appreciated. All seems to be work well now..... Thanks Again, Dean

Ok I figured it out I needed to change the server name in the letsencrypt proxy-config file. Everything is now working the way it was. I am still getting this error when I log in to the controller through the proxy, I am sure it’s not the container. If anyone could lead me in the right direct to solve the problem, I would appreciate it. This is the error that always pops up on the controller while I connected remotely. WebSocket connection error This is what the console in chrome shows for the error, but I am not sure on what to look at? WebSocket connection to 'wss://***.*****.com/wss/s/default/events' failed: Error during WebSocket handshake: Unexpected response code: 400 O.open @ components.v5.10.17.1.js:167 I blocked out the address it does not show ***.*****.com but the correct address. Thanks for the help, Dean

First thanks for the update much appreciated. I noticed that port 10001 is set to TCP should it not be UDP? Also, I have this error when trying to connect the controller from my external host name? It was working be for and if I stop the new controller and fire up the old controller it connects just fine any ideas where to look? 502 Bad Gateway nginx/1.14.2 Thanks, Dean

+1