Home Network Community > All Threads > Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)
< All Threads

Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)

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

Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)
Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)
2022-04-30 06:50:55 - last edited 2022-06-09 02:40:12
Tags: #Port Forwarding
Model: Archer AX3000  
Hardware Version: V1
Firmware Version: 1.0.11 Build 20210730 rel.54485(4555)

Hi, I'm trying to host a web server on a Raspberry Pi 4 but without luck on the following modem: Archer AX3000, 1.0.11 Build 20210730 rel.54485(4555)

I've changed the remote access port in the settings from 80->8080, 443->4443:

 

and then I've added a forwarding rule:



I've rebooted the modem. After that, it seems that the port 80 is still used by the modem's web, because it's still opens on port 80 on the local network:



Are there any ways to forward port 80 on this modem model? 

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)-Solution
2022-05-01 03:32:30 - last edited 2022-05-07 07:55:52

  @terziyski 

Actually, yes, but only now I can see - the problem was on the side of the ISP and the modem works fine.

When I opened PUBLIC url on WiFi of the ISP, the page opened (on the port 80).
Only when I changed the network from WiFi to Mobile (another ISP) the page and port 80 became unreachable.

After doing a tracerout, I figured out that by accessing the public ip and port 80 on WiFi, there was only 1 node - a router of the ISP (a loopback).
So, it seems like the port 80 is unaccessible behind the NAT of my ISP, but accessible while I'm there.

It means that my ISP blocks port 80 for pppoe WAN incoming connections, and port 80 forwarding works fine on the modem.

Recommended Solution
  1  
  1  
#3
Options
2 Reply
Re:Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)
2022-04-30 14:20:00 - last edited 2022-05-02 13:20:51

  @rigid_spoon 

 

Have you done this test from an external network (mobile or other ISP): http://<your_public_ip_address>

Also make sure that your Internet IP address matches your public IP address here:

 

 

If your Internet IP address is private then you're behind a double NAT and that's the issue.

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:Archer AX3000/AX50 Port 80 is Not Forwarded (Virtual Server)-Solution
2022-05-01 03:32:30 - last edited 2022-05-07 07:55:52

  @terziyski 

Actually, yes, but only now I can see - the problem was on the side of the ISP and the modem works fine.

When I opened PUBLIC url on WiFi of the ISP, the page opened (on the port 80).
Only when I changed the network from WiFi to Mobile (another ISP) the page and port 80 became unreachable.

After doing a tracerout, I figured out that by accessing the public ip and port 80 on WiFi, there was only 1 node - a router of the ISP (a loopback).
So, it seems like the port 80 is unaccessible behind the NAT of my ISP, but accessible while I'm there.

It means that my ISP blocks port 80 for pppoe WAN incoming connections, and port 80 forwarding works fine on the modem.

Recommended Solution
  1  
  1  
#3
Options

Information

Helpful: 0

Views: 1381

Replies: 2

Tags

Port Forwarding
Related Articles
Archer AX50 AX3000 wireless issue
10849 0
Archer AX3000|AX50 loosing internet speed
10516 1
how to forward port 80
373 0
Archer AX50 AX3000
5219 1
AX3000/AX50 keeps rebooting
6300 0
Archer [ax3000] [ax50] 5Ghz DL Speed too slow
1093 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.