Odd one here. Specific website no longer accessible while INSIDE my network.

[cvman_16]

I host my own website within my house, as of 2 days ago, I can no longer reach my domain, it times out, but the moment I'm outside my network, it's fully functional.

Affects ALL devices in the network, 2 computers on wifi, 2 computers via ethernet, phones, and tablets.

from WITHIN the Network, I can successfully PING the domain, NSLOOKUP also seems to work as expected.

I can only speculate the block is related to my Blue Curve modem, otherwise, not all devices would be affected. 

I have bounced around through MULTIPLE Shaw Support reps with no resolution.

This has been functional for almost 2 decades, and now it's off.

Thoughts???

[rstra]

@cvman_16 

This worked with XB6 in the past and then stopped? Can you access the website by using the local IP address?

[cvman_16]

yes, I have learned this morning that my local LAN IP loads, naturally, this will not see my cookie set on the domain. This has always worked, just not now.

[rstra]

@cvman_16 

I wonder if there was an update the blocked NAT loop back? 

[cvman_16]

IMO it has to be something like that, but support isn't aware

[ksihota]

Trying to figure out if this is related to my issue. Are you using 2 IPs and have your modem in Bridge mode?
In my situation I have my modem in bridge mode and my local server using one ip address while my home system uses the 2nd ip address. For some time, I was unable to access my server from within my home unless I used a VPN. It had not been an issue when I was using my older Hitron modem. After upgrading to the newer modem (forcing me to use bridge mode) the problem began. I tried everything I could think of and tried everything I was told by support but couldn't figure it out. Then, about a year ago it seemed to work properly. I have no idea what changed and can't find my original posts here about it.  Just recently the issue is back so I am looking through posts to see if I can figure out what changed.

[ksihota]

Just a small addition to this...
I say that I can't access it locally without using a VPN, this is not quite true. I t appears that there actually is a connection but it is so slow that it just ends up timing out. In some cases there may be a slight response but a page would only load a very limited amount of data.

I did find my old post and the date it started working was around March of last year but I couldn't find any reason why.

[mdk]

@ksihota -- from a computer connected to your first router, run a "trace-route" to the IP-address assigned to the WAN port on your second router. Fast? Slow? 

From a computer connected to your second router, run a "trace-route" to the IP-address assigned to the WAN port on your first router. Fast? Slow? 

[mdk]

@cvman_16 -- from WITHIN the Network, I can successfully PING the domain, NSLOOKUP also seems to work as expected

So, PING packets to the private IP-address of your web-server reach that computer, and "response" packets get routed back. But, PING packets may just "talk" directly to the network-adapter inside your web-server, and those packets do NOT get handled by any application running on your computer. In contrast, TCP/IP packets from your computer to the web-server must reach your web-server, so that the web-server application can respond. 

NSLOOKUP just looks at routing information -- it does not actually send any packets to any "target" computer, unlike PING or TRACERT or HTTP/secure-HTTP. So, NSLOOKUP will work, even when the web-site's computer is powered-off.

[ksihota]

From my server (wired) the traceroute was <0.1ms

From my laptop (wifi on the home side) I get this. The home side is using a bitdefender box as its WIFI router.

1 1 ms <1 ms <1 ms S0106e8447e03f0e8.gv.shawcable.net

Thought I would check the route from my laptop to the server and this is what I got.

Tracing route to S0106a4badb14c311.gv.shawcable.net [24.108.193.xxx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms box.local [10.10.10.1]
2 11 ms 10 ms 119 ms 24.108.192.1
3 22 ms 22 ms 24 ms S0106a4badb14c311.gv.shawcable.net

When I tried the server domain name instead of IP address I kept getting time outs but noticed that the IP address for the server was wrong. I checked back later and then it went through properly and the IP address for the server was correct. Obviously a DNS updating issue there. Times were about the same.

Even though the DNS appears to be updating the connection is still not working properly although it does appear to connect at random times (albeit very slowly)

Maybe its a DNS issue but I can't see why the direct IP address connection wouldn't work or why I can access from outside my home or by using a VPN. From what I can see, it appears as if the modem is the issue, however, this is way above my pay grade.