reverse proxy/ Dockge agent fails across subnets

[mvnixon]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Hi,
I have Dockge running across several hosts in the same subnet. My 'primary' dockge connects to other dockge instances as agents without problem. I also have a nginx reverse proxy set up pointing to all dockge instances, which has worked flawlessly. These all run on a 192.168.1.0/24 subnet.

I've recently set up a new host on a different subnet (for security reasons) on 192.168.5.0/24 subnet, and installed dockge. I can access it fine directly via ip:5001, however when using either the 'primary' dockge instance to connect to the new host, it times out when connecting (I specify the ip:5001 address). Also, when I've set up my reverse proxy and try to access it via the reverse proxy, I get (110: Operation timed out) errors in the proxy logs. Accessing directly works fine.
In the container logs for the dockge instance I'm trying to connect to, the only think that is printed is Origin is not set, IP: ::ffff:192.168.1.11

Ive removed all config files, and started again several times. What is infuriating is that it actually seems to work and connect fine to start with, then stops working, without any rhyme or reason. The only common denominator I can see is that it only occurs when connecting via reverse proxy or another dockge instance from subnet 192.168.1.0/24 to the subnet in which the new dockge instance resides, 192.168.5.0/24.

Does anyone have any ideas on how I can further troubleshoot?

📝 Error Message(s) or Log

No response

🐻 Dockge Version

1.4.2

💻 Operating System and Arch

Ubuntu 24.04.1

🌐 Browser

Safari 18.0.1

🐋 Docker Version

27.3.1

🟩 NodeJS Version

No response