Business Community > Routers > Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
< Routers

Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
2023-10-18 14:33:23 - last edited 2023-10-19 10:46:46
Tags: #NAT #Controller Related
Model: ER605 (TL-R605)   SG2210P  
Hardware Version: V3
Firmware Version: 3.20.9

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

 

  1. Router ER-605
  2. Switches TL-SG2210P v3.20
  3. 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? 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy-Solution
2023-10-19 09:56:53 - last edited 2023-10-19 10:46:46

  @liosali 

 

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.

"SY" is a 22-year old boy presenting to the tp-link community with brain empty. Take care of yourself, and be well. Loycechan030
Recommended Solution
  0  
  0  
#6
Options
13 Reply
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 02:38:40

  @liosali 

 

Screenshots of your topology and port forwarding rules pls?

"SY" is a 22-year old boy presenting to the tp-link community with brain empty. Take care of yourself, and be well. Loycechan030
  0  
  0  
#2
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 03:12:55

  @Loycelover- 

 

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

 

  0  
  0  
#3
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 07:38:16

  @liosali 

 

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?

"SY" is a 22-year old boy presenting to the tp-link community with brain empty. Take care of yourself, and be well. Loycechan030
  0  
  0  
#4
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 08:29:45

  @Loycelover- 

 

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

 

  0  
  0  
#5
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy-Solution
2023-10-19 09:56:53 - last edited 2023-10-19 10:46:46

  @liosali 

 

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.

"SY" is a 22-year old boy presenting to the tp-link community with brain empty. Take care of yourself, and be well. Loycechan030
Recommended Solution
  0  
  0  
#6
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 10:06:17
Is there no way around this? If not, then I will be forced to change the architecture again .... :(
  0  
  0  
#7
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 10:07:56

  @liosali 

 

No idea for now but maybe they will fix it later if you just send emails and give direct feedback?

"SY" is a 22-year old boy presenting to the tp-link community with brain empty. Take care of yourself, and be well. Loycechan030
  0  
  0  
#8
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 10:11:11

  @Loycelover- 

 

How can we send them an emial for this fix? 

 

I am not aware of the channel, can you please guide me?

  0  
  0  
#9
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 10:13:29

  @liosali 

 

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.

"SY" is a 22-year old boy presenting to the tp-link community with brain empty. Take care of yourself, and be well. Loycechan030
  0  
  0  
#10
Options
Re:Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2023-10-19 10:46:19

  @Loycelover- 

 

Thank you will definately do!!!!

 

Appriciate all your help !!!!! 

  0  
  0  
#11
Options
12

Information

Helpful: 0

Views: 2068

Replies: 13

Tags

NAT Controller Related
Related Articles
 Omada software controller 4.1.5 - Port 80 and port 443 are already in use
3406 0
 Unable to route port 80/443 through NAT/DMZ
474 0
 ER605 Port Forwarding will not work under Omada Software Controller
1057 0
After upgrade of Omada Software Controller V5.7 to V5.8.4 Windows no data is shown (using port 443)
1598 0
Port Forwarding 443 Forwards to the WebUI of the Router Instead of the Internal Server
1938 0
Change the port to 443 in OpenVPN
495 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.