Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
I am writing on this forum for the first time in hope that someone will be able to help me with my problem.
I am using a Omada Software Controller where my
- Router ER-605
- Switches TL-SG2210P v3.20
- Access EAP245
are all managed by the Omada Software Controller connected to one of the switches as in point 02.
I am trying to deploy Nginix Reverse Proxy via npm and when i try to expose port 80 and 443 on the Router, the traffic lands on the router's login page instead of the portfording rule that I have defined under Settings > Transmission > NAT > Portforwarding rules.
These rules to route the traffic to a dedicated system inmy network are not working at all and the traffic lands an the login page of the router with the message in the red at the bottom saying "This Gateway is managed by Omada Controller <IP address>
Can any one help me fis this issue?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Well, when you use controller, the 80 and 443 port will be forwarded automatically for the gateway, and this rule has the highest priority, that's why you cannot forward them again for your own server. You can try to forward other ports for your server, or just use gateway in standalone mode.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Following is the topology
and following are the rules
I have disabled the rules for the port 80 and port 443 since it was not working, following are the details of the rules
and
- Copy Link
- Report Inappropriate Content
The configurartions should be OK, but it seems you have set the https port forwarding rules' destination as 192.169.x.x, is it 192.168.x.x?
- Copy Link
- Report Inappropriate Content
Yes, that is the plan,
I exposed both the 80 and the 443 port in the same manor.
Well initially i tried to route all traffic to my NPM (reverse proxy) so i placed in the internal ip address of 192.168.X1.Y1, as was trying to get the HTTPS certificate form LetsEncrypt it kept failing.
Then I routed the ports of my LMS server via the NAT (as you saw the screenshot in the previous message). Tried to get the certificate for the LetsEncrypt and it failed again. Upon investigations I found that the LetsEncrypt was trying to reach my server via port 80 but it was not able to verify the header.
So I simply typed in my external IP from another network in a browser and i landed on the login page of my router ER605, below is the screen shot
I am getting this for both http (port 80) and https (port 443) when i type in my public ip address.
So not sure what I am doing wrong
- Copy Link
- Report Inappropriate Content
Well, when you use controller, the 80 and 443 port will be forwarded automatically for the gateway, and this rule has the highest priority, that's why you cannot forward them again for your own server. You can try to forward other ports for your server, or just use gateway in standalone mode.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
No idea for now but maybe they will fix it later if you just send emails and give direct feedback?
- Copy Link
- Report Inappropriate Content
How can we send them an emial for this fix?
I am not aware of the channel, can you please guide me?
- Copy Link
- Report Inappropriate Content
Don't know which country are you from but you should be able to find an official support email on the official website, click contact us or Support or something like this.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2041
Replies: 13
Voters 0
No one has voted for it yet.