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.

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.
404 from controller when accessing via port forwarding
404 from controller when accessing via port forwarding
2022-10-11 03:23:35 - last edited 2022-10-12 08:56:35
Model: OC200  
Hardware Version: V1
Firmware Version: 5.5.7

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

  0      
  0      
#1
Options
1 Accepted Solution
Re:404 from controller when accessing via port forwarding-Solution
2022-10-11 20:43:02 - last edited 2022-10-13 09:57:40

EDIT: post removed

Recommended Solution
  2  
  2  
#4
Options
4 Reply
Re:404 from controller when accessing via port forwarding
2022-10-11 17:13:25

  @SethP 

 

Hey

 

Never tried it that way, but another option for you would be to use a VPN.   Setup OpenVPN on the controller, therefore when you connect to the VPN you are inside your network and can access the controller locally.

 

Personally I just use the cloud access for remote control (or the app).  

  0  
  0  
#2
Options
Re:404 from controller when accessing via port forwarding
2022-10-11 18:08:53

  @Philbert Thank you - that's a great suggestion for manual access, but it won't work for my software that uses the API, as it runs as a service on a computer where a vpn can't be left on.

 

There's got a to be a way to port forward to the controller...

 

Seth

  0  
  0  
#3
Options
Re:404 from controller when accessing via port forwarding-Solution
2022-10-11 20:43:02 - last edited 2022-10-13 09:57:40

EDIT: post removed

Recommended Solution
  2  
  2  
#4
Options
Re:404 from controller when accessing via port forwarding
2022-10-11 22:08:38

  @btx Awesome, thank you!  That worked great.

 

Seth

  0  
  0  
#5
Options