502 Error with "Custom" Port

[Shaneee]

I have Swag setup with my domain and it's working perfect for everything so far. However I have an app that shared a port so I've changed it.
For example it wanted to use port 84 but it's in use so I changed it to 85. I can access it locally but when I edit the proxy-conf file and alter the port I just get a 502 Bad Gateway error.

Setup was the same as everything else. I have my root hosted in www and it works. Other apps with subdomains all routed to my domain with Swag/Cloudflare just this one app that doesn't use the "expected" port number...

[Shaneee]

Fixed by using the Unraid local IP in the conf rather than the container name.

[drizuid]

I have Swag setup with my domain and it's working perfect for everything so far. However I have an app that shared a port so I've changed it.
For example it wanted to use port 84 but it's in use so I changed it to 85. I can access it locally but when I edit the proxy-conf file and alter the port I just get a 502 Bad Gateway error.

for others who come here, the accepted solution is the solution the OP chose, it is not the generally recommended solution for others.

you should not be changing the port in the proxy conf at all; internally it's still whatever it originally was (84) as long as swag and the app share a custom bridge.

your work around solution is causing triple nat and is very inefficient.

proper solution: pc -> unraid -> nat to swag -> app on port 84
your solution: pc -> unraid -> nat to swag -> nat to unraid -> nat to app on port 85