Jump to content

Browser Based Launcher sessions disconnect unexpectedly when using a Nginx Reverse Proxy


support

Recommended Posts

A user has reported an issue with the browser based launcher, where after establishing either a RDP of SSH session, the tab that the session is in seems to close unexpectedly.  This happens at around the 2 minute mark into the session.

 

The customer came back to us for a fix for this, which I've quoted below.  Thanks to our customer who provided this feedback, if you are reading this:)

 

The issue with the remote session launcher closing after a few minutes of inactivity was reverse proxy related. We are using NGINX as a reverse proxy. Since your browser-based remote sessions use WSS, an upgrade instruction was needed to get the launcher working (proxy_set_header Upgrade $http_upgrade). After that, remote sessions worked, but they would close after a short period of inactivity. This timeout has been increased with the (proxy_read_timeout) instruction. These two config lines will be needed if users would like to use browser-based remote sessions with an NGINX reverse proxy successfully. Everything works great now.

 

Regards,

Support.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...