404 from controller when accessing via port forwarding
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I need to access my oc200 controller directly, both for backups and I've written some software that uses the controller API. On the local network everything works correctly. I open Chrome and put in "https://192.168.3.2" and it redirects to https://192.168.3.2/eba0faca6954b514b6d833[edited]/login where I get the login screen (after Chrome tells me it's not secure, and I tell it to proceed).
With port forwarding, I have 8043 forwarded to the controller's 443, and when I put https://100.x.x.x:8043 into chrome, I get the redirect to https://100.x.x.x:8043/eba0faca6954b514b6d833[edited]/login, so I know it's connecting to the controller, but instead of the login form I get a 404. And I've tried source ports other than 8043 with the same result.
If I use 443 as the source port everything works fine, so it wouldn't appear to be a networking issue.
How I can use a source port other than 443 to remotely access the controller?
Thank you.
Seth
