October 1, 20196 yr 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 October 1, 20196 yr by pengrus Add TMM description
Archived
This topic is now archived and is closed to further replies.