Websockets through Reverse Proxy


Recommended Posts

Hi,

 

I have 6.7.2 running multiple dockers and VMs which have various browser-based services running behind a reverse proxy hosted in one of those VMs.  This proxy is actually kind of two-way, it handles external requests, but also internal requests on my local domain.  Problem is, I cannot access several service features, including the sockets unraid uses for logs, docker updates, the terminal, etc, unless I access those domains locally.

 

Example:

 

sonarr.example.com proxied to 192.168.1.xxx, works fine.

tower.example.com proxied to 192.168.1.yyy works, but not any of the sockets/windows

192.168.1.yyy works fine.

tinymediamanager.example.com proxied to 192.168.1.zzz doesn't work at all (in case you're unfamiliar, it's written entirely in Java, displayed through what I think is similar to noVNC/etc on ip:5800)

 

Behavior is the same whether they are publicly accessible or not.

 

It seems as if whatever those pages are trying to pass just isn't making it through the journey from public IP to https server to proxied asset (and back).

 

Any ideas?

 

Thanks!

 

-P

Edited by pengrus
Add TMM description
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.