Exposing my port 80 and 443 via the Omada OC200 Hardware Controller for hosting Nginx reverse proxy
Exposing my port 80 and 443 via the Omada OC200 Hardware Controller for hosting Nginx reverse proxy
I need a way to forward 443 and 80 to my server!
From what I am reading on the forum the router (er605) automatically forwards 443 and 80 to the controller if not used in standalone mode.
Is this true? This seems like a supersilly implementation! Why did I spend 100$ on a piece of HW only to not be able to host anything using https and hostname.
DNS only resolves to an ip and I cant tell everyone to type in mydoman:specialPort.
Is the way to use the software controller instead and place it downstream from a reverse proxy?
That way all the 443 and 80 trafic would get redirected to a machine that has both the reverse proxy and the controller.
Any Ideas for workarounds of this stupid implementation?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Im glad you resolved your issue (its usually something simple like a typo!)
I am curious about something, you were saying that if you were redirecting 443 it always resulted in forwarding to your controller? I dont see how this can be if you dont have a port forward specifically for that. By default, nothing is forwarded anywhere and you are free to forward any port to any IP that you want.
Do you have any remote sites that your OC200 is also controlling?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1374
Replies: 12
Voters 0
No one has voted for it yet.