Daan I never got it to work.
Ron Gage On Mon, 2025-10-06 at 10:45 +0000, Daan wrote: > Any luck with your nginX configuration Ron? It would make a nice > “best practices” story if you do.. > > On 2025/09/02 19:03:22 Ron Gage wrote: > > Hello again from Detroit! > > > > With my luck, this isn't going to be workable, but I would like to > > run > > this through you all here before I give up on the approach. > > > > I have nginX Proxy Manager sitting in front of my Cloudstack > > system. > > Except for one thing, it appears to be working. The one thing: > > bringing > > up a console of a running instance disconnects immediately. The > > noVNC > > objects all draw on the screen as expected - including the pull-out > > on > > the left. Once everything draws on the web browser, I immediately > > get a > > "disconnected" bar across the top of the screen. I am really > > hoping to > > get this working as it's my last major hurdle here. > > > > I have the requisite defined name for the console proxy defined in > > CS > > and it is coming up in the browser properly. In NPM, while I have > > a > > Let's Encrypt cert defined/created, I am not forcing SSL. I have > > NPM > > forwarding traffic to the CS Console Proxy as http and that is > > working > > as expected. I also have a stream defined for port 8080 traffic to > > allow the data stream to come through unmolested. I also have the > > firewall on the NPM set to allow tcp ports 80, 443 and 8080. > > > > I have nmapped the console proxy internally and it shows only tcp > > ports > > 80 and 8080 open. > > > > I am testing from both my day-job as well as from my cell phone > > with > > Wifi turned off. Same result either way. The console works just > > fine > > from within my network. > > > > Anyone have any ideas on what I could be doing wrong here? > > > > Ron Gage > > > > > > -- Ron Gage Westland, MI
