Home Network Community > Wi-Fi Routers > cascading router, Nginx and port forwarding
< Wi-Fi Routers

cascading router, Nginx and port forwarding

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

cascading router, Nginx and port forwarding

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
cascading router, Nginx and port forwarding
cascading router, Nginx and port forwarding
2024-04-17 18:22:54 - last edited 2024-04-17 19:51:24
Tags: #Port Forwarding
Model: Archer AX55 Pro  
Hardware Version:
Firmware Version: latest, installed today

Hello,

this is the strange situation:

I have a primary modem/router connected to my ISP (ip 192.168.0.1/24) and an Archer AX55 connected to the first one (ip 192.168.1.1/24).

I have a NAS running Nginx in a Docker container. I forwarded port 443 and 80 from the main router to the Tp-Link and then from the Archer to the NAS.

The reverse proxy managed by Nginx doesn't work but, until yesterday, with another router in place of Archer, everything worked fine.

Any idea?

Port forwarding of course is working correctly.

 

Thanks

Max

  0      
 
  0      
 
#1
Options
5 Reply
Re:cascading router, Nginx and port forwarding
2024-04-18 02:35:55

  @maxmonz 

 

Have you considered to use your AX55 in AP mode (Case 1) to avoid the double NAT and also double port-forwarding.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  0  
  0  
#2
Options
Re:cascading router, Nginx and port forwarding
2024-04-18 06:48:13

  @maxmonz 

 

Yes, I considered that option but for some reason I used this one for years. Never had problems.

I can't imagine what's the reason. With the previous router and the same configuration everything was fine.

  0  
  0  
#3
Options
Re:cascading router, Nginx and port forwarding
2024-04-18 07:00:48

  @maxmonz 

 

Neither can I, that's why I suggested to set AX55 in AP mode.

What your exact router model AX55 Pro or AX55 and what's its FW release indeed ?

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  0  
  0  
#4
Options
Re:cascading router, Nginx and port forwarding
2024-04-18 07:08:09

  @maxmonz 

 

Firmware: 1.2.3 Build 20231103 rel.66045(4555)
Hardware: Archer AX55 Pro v1.0

  0  
  0  
#5
Options
Re:cascading router, Nginx and port forwarding
2024-04-18 08:12:11 - last edited 2024-04-18 08:15:10

  @maxmonz 

 

Indeed the latest FW release.

I found a similar problem in the Netgear community though.

Have a look and see how this was resolved.

If that doesn't work for you can try the AX55 Pro in AP mode.

Before making any re-configurations make a configuration backup.

Thus, it would be easier if you decide to go back, restoring the configuration.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue and mark the post as a "Recommended Solution".
  0  
  0  
#6
Options

Information

Helpful: 0

Views: 963

Replies: 5

Tags

Port Forwarding
Related Articles
Port Forwarding Not Actually Forwarding Port
328 0
Port forwarding
168 0
port forwarding interval port
1229 0
Why port forwarding feature is not working on my router?
461 0
Port forwarding not working
1426 0
Port Forwarding not Working
394 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.