Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mauro.mascarenhas]

Hello,

I'm having a issue with port forwarding, specifically the 80 one.
The problem is: I am testing a webserver with my local computer (an WordPress installation), so I need the PORT 80 to make my site available to everyone.
Then, I have followed this guide (I know it is outdated, but the concept remains the same), but unfortunately it does not work. With any other port it works like a charm, so I have something like this: myserver.dlinkddns.com:8080, but I do not want this ":8080" in the end of the URL, once it is quite "ugly" and the convention is that HTTP servers must be on PORT 80, so it can be ommited in the URL bacoming something like myserver.dlinkddns.com.
In the beginning I though it was due to the configuration interface, but it is only lfor local use(192.168.0.1) [LAN]. Does anybody know what can be causing this issue?

Since now, thanks a lot.

Yours faithfuly,
Mauro Mascarenhas.

[FurryNutz]

Link>Welcome!

• What Hardware version is your router? Look at sticker under the router case.
• Link>What Firmware version is currently loaded? Found on the routers web page under status.
• What region are you located?

I presume it maybe due to the issue of D-Link routers don't support loopback.
List of NAT Loopback Supporting Routers

[mauro.mascarenhas]

Hi, thank you for answering to my question.

Well, here is the data:

Router :	DIR-615 T1
FW :	20.06
Region :	South America (Brazil)

After looking at the list, I have not noticed this device present there. Nevertheless, the port 8080 does work after configuring it in "Advanced->Virtual Server" and entering the following data:

Service name	WEB
Protocol :	TCP
WAN PORT :	8080
Open LAN PORT :	80
LAN IP address :	192.168.0.101

192.168.0.101 is a attached to MAC address to avoid conflicts (static).
Then, if I access the 8080 port outside my house it works fine, but if I use 80 port nothing happens.
Furthermore, I have another router (DIR-600 C1) which is in the list you have just sent, but it does not work too.

Since now, thank you a lot.

[FurryNutz]

I presume Virtual Server will help for remote access.

[mauro.mascarenhas]

I presume Virtual Server will help for remote access.

Sorry? I could not see your point.

--- EDIT ---

I have just upgraded the FW to v20.11 but the problem still persists.

I have also used this tool (http://canyouseeme.org/) and as expected, the port 8080 worked, but the 80 gets connection timed out. Any suggestion?
As I have just said before, when using my DIR-600 I get the same problem.

[FurryNutz]

That are your firewall settings set for?

[mauro.mascarenhas]

That are your firewall settings set for?

Yes, those are the settings for my server ("Advanced->Virtual Server" for DIR-615 and in "Advanced->Port forwarding" in DIR-600 ):

Service name	WEB (HTTP in DIR-600)
Protocol :	TCP
WAN PORT :	8080 (8080~8080 in DIR-600)
Open LAN PORT :	80 (80~80 in DIR-600)
LAN IP address :	192.168.0.101

and:

Service name	WEB (HTTP in DIR-600)
Protocol :	TCP
WAN PORT :	80 (80~80 in DIR-600)
Open LAN PORT :	80 (80~80 in DIR-600)
LAN IP address :	192.168.0.101

However just the first configuration is working. In addition to that, my system does not have any blockage (it is a linux server - BITNAMI Stack).

[FurryNutz]

so all is accessible from the wan side now not from the LAN side right?

[Hard Harry]

Who is the ISP? Most block incoming port 80 to stop people from running web servers if it is against their Terms of Service(ToS). It sounds like your does too, which means they probably don't want you having a website long term on your service. Before figuring out how to fix the problem, you might want to ask them what they allow first.

[mauro.mascarenhas]

so all is accessible from the wan side now not from the LAN side right?

Not actually, on the LAN side it is working fine (tested from mobiles and other computers connected to the home network - http://192.168.0.1/ - did not need to include the port because is already in the conventional one (80) at the server), but it is not working on WAN side (it only redirects from PUBLIC_IP:8080 to 192.168.0.101:80, but not from PUBLIC_IP:80 to 192.168.0.101:80).

Who is the ISP? Most block incoming port 80 to stop people from running web servers if it is against their Terms of Service(ToS). It sounds like your does too, which means they probably don't want you having a website long term on your service. Before figuring out how to fix the problem, you might want to ask them what they allow first.

Thanks for the suggestion, but after checking it fortunately I found that my ISP (NET Virtua) does not block port 80, but I have also found lots of people with the same ISP complaining about it. I'm going to check it and then return here.

--- EDIT ---

Well, unfortunately Hard Harry is right. after run a test at https://www.grc.com/x/ne.dll?rh1dkyd2 it showed me that standardized ports are blocked here (which is illegal in Brazil). Thank you for the suggestion and sorry for the incovenience. Now I am going to claim them to make those ports available to me.

[FurryNutz]

Good Luck.

[mauro.mascarenhas]

Good Luck.

Well, thank you.
You can already mark this topic as resolved. Thank you a lot for the given support.

[FurryNutz]

Good Luck.