Jump to content

Issues Connecting to linustechtips.com

ZesIO
By ZesIO
in Forum Bugs and Issues
 Share
Posted

As stated in another post, I have issues connecting to linustechtips.com through my normal ISP. Loading up floatplane.com works just fine, but the SSO through linustechtips.com fails as well. All HTTP(S) requests seem to be timing out. @colonel_mortis

 

My ISP is: RWTH Aachen University (AS47610)

Connecting IP Range (for my student dorm): 137.226.236.0/23 

 

I have inquired via ticket to find out, if our universities firewall is causing issues: but they're telling me that everything should be fine. Not sure if there's any additional information that would help... our router is a Cisco Catalyst 4500X, but since it's only routing traffic through to our univiersities data center and their firewall is supposedly fine, it shouldn't cause any issues.

 

Maybe worth a note: We currently only have a IPv4 subnet, but considering that IPv6's adoption is taking a while, this probably shouldn't cause issues either.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Do either of http://104.27.164.153 (expecting a Cloudflare error direct IP access not allowed) or https://linustechtips.com/cdn-cgi/trace work for you?

In the other topic, you said ping was working correctly - is the IP that it's using one of 104.27.164.153 or 104.27.165.153 (linux ping tells you, not sure about Windows)?

HTTP/2 203

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
2 minutes ago, colonel_mortis said:

is the IP that it's using one of 104.27.164.153 or 104.27.165.153 (linux ping tells you, not sure about Windows)?

Windows does tell it too.

^^^^ That's my post ^^^^
<-- This is me --- That's your scrollbar -->
vvvv Who's there? vvvv

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
53 minutes ago, colonel_mortis said:

Do either of http://104.27.164.153 (expecting a Cloudflare error direct IP access not allowed) or https://linustechtips.com/cdn-cgi/trace work for you?

In the other topic, you said ping was working correctly - is the IP that it's using one of 104.27.164.153 or 104.27.165.153 (linux ping tells you, not sure about Windows)?

Neither work for me, just getting an "ERR_CONNECTION_TIMEOUT" in Chrome or whatever equivalent in other browsers.

 

When pinging linustechtips.com I get ICMP responses from 104.27.164.153.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
10 minutes ago, ZesIO said:

Neither work for me, just getting an "ERR_CONNECTION_TIMEOUT" in Chrome or whatever equivalent in other browsers.

 

When pinging linustechtips.com I get ICMP responses from 104.27.164.153.

Are you running linux/macos, or do you have the linux subsystem installed? If so, in a linux-style command prompt, can you run 

traceroute -T -p 80 linustechtips.com

(you may need to use sudo), and also 

traceroute -I linustechtips.com

Then post both outputs either here or in PM. The first will see where packets are being dropped when making a HTTP request, and the second effectively uses ping to see what route they should have taken.

HTTP/2 203

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
There you go!
root@nikh ~ # traceroute -T -p 80 linustechtips.com                                                                                                         
traceroute to linustechtips.com (104.27.165.153), 30 hops max, 52 byte packets
 1  137.226.236.1 (137.226.236.1)  4.218 ms  4.362 ms  4.593 ms
 2  n7k-sw23-1-wohnheime-vl1019.noc.rwth-aachen.de (137.226.34.161)  0.673 ms  0.956 ms  1.292 ms
 3  n7k-lssnord-1-et4-14.noc.rwth-aachen.de (137.226.139.37)  0.670 ms n7k-ww10-1-et4-14.noc.rwth-aachen.de (137.226.139.33)  0.669 ms  0.864 ms
 4  fw-xwin-2-vl158.noc.rwth-aachen.de (134.130.3.253)  0.388 ms  0.285 ms  0.231 ms
 5  n7k-ww10-1-xwin-vl106.noc.rwth-aachen.de (134.130.3.227)  1.132 ms  1.348 ms  1.627 ms
 6  n7k-lssnord-1-xwin-po101-1.noc.rwth-aachen.de (134.130.9.130)  0.940 ms  1.211 ms  0.934 ms
 7  cr-fra2-be8-3006.x-win.dfn.de (188.1.242.109)  4.435 ms  4.551 ms  4.600 ms
 8  de-cix-frankfurt.as13335.net (80.81.194.180)  5.815 ms  5.722 ms  5.709 ms
 9  104.27.165.153 (104.27.165.153)  4.230 ms  4.296 ms  4.654 ms
root@nikh ~ # traceroute -I linustechtips.com                                                                                                                 
traceroute to linustechtips.com (104.27.165.153), 30 hops max, 60 byte packets
 1  137.226.236.1 (137.226.236.1)  1.201 ms  1.349 ms  1.588 ms
 2  n7k-sw23-1-wohnheime-vl1019.noc.rwth-aachen.de (137.226.34.161)  0.721 ms  1.007 ms  1.299 ms
 3  n7k-ww10-1-et4-14.noc.rwth-aachen.de (137.226.139.33)  0.614 ms  0.827 ms  1.050 ms
 4  fw-xwin-2.noc.rwth-aachen.de (134.130.3.253)  0.395 ms  0.436 ms  0.441 ms
 5  n7k-ww10-1-xwin-vl106.noc.rwth-aachen.de (134.130.3.227)  1.093 ms  1.682 ms  1.779 ms
 6  n7k-lssnord-1-xwin-po101-1.noc.rwth-aachen.de (134.130.9.130)  1.078 ms  1.282 ms  1.330 ms
 7  cr-fra2-be8-3006.x-win.dfn.de (188.1.242.109)  4.377 ms  4.333 ms  4.748 ms
 8  de-cix-frankfurt.as13335.net (80.81.194.180)  6.875 ms  6.751 ms  6.702 ms
 9  104.27.165.153 (104.27.165.153)  4.693 ms  4.790 ms  4.335 ms

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
3 minutes ago, ZesIO said: 

There you go!

root@nikh ~ # traceroute -T -p 80 linustechtips.com                                                                                                         
traceroute to linustechtips.com (104.27.165.153), 30 hops max, 52 byte packets
 1  137.226.236.1 (137.226.236.1)  4.218 ms  4.362 ms  4.593 ms
 2  n7k-sw23-1-wohnheime-vl1019.noc.rwth-aachen.de (137.226.34.161)  0.673 ms  0.956 ms  1.292 ms
 3  n7k-lssnord-1-et4-14.noc.rwth-aachen.de (137.226.139.37)  0.670 ms n7k-ww10-1-et4-14.noc.rwth-aachen.de (137.226.139.33)  0.669 ms  0.864 ms
 4  fw-xwin-2-vl158.noc.rwth-aachen.de (134.130.3.253)  0.388 ms  0.285 ms  0.231 ms
 5  n7k-ww10-1-xwin-vl106.noc.rwth-aachen.de (134.130.3.227)  1.132 ms  1.348 ms  1.627 ms
 6  n7k-lssnord-1-xwin-po101-1.noc.rwth-aachen.de (134.130.9.130)  0.940 ms  1.211 ms  0.934 ms
 7  cr-fra2-be8-3006.x-win.dfn.de (188.1.242.109)  4.435 ms  4.551 ms  4.600 ms
 8  de-cix-frankfurt.as13335.net (80.81.194.180)  5.815 ms  5.722 ms  5.709 ms
 9  104.27.165.153 (104.27.165.153)  4.230 ms  4.296 ms  4.654 ms

root@nikh ~ # traceroute -I linustechtips.com                                                                                                                 
traceroute to linustechtips.com (104.27.165.153), 30 hops max, 60 byte packets
 1  137.226.236.1 (137.226.236.1)  1.201 ms  1.349 ms  1.588 ms
 2  n7k-sw23-1-wohnheime-vl1019.noc.rwth-aachen.de (137.226.34.161)  0.721 ms  1.007 ms  1.299 ms
 3  n7k-ww10-1-et4-14.noc.rwth-aachen.de (137.226.139.33)  0.614 ms  0.827 ms  1.050 ms
 4  fw-xwin-2.noc.rwth-aachen.de (134.130.3.253)  0.395 ms  0.436 ms  0.441 ms
 5  n7k-ww10-1-xwin-vl106.noc.rwth-aachen.de (134.130.3.227)  1.093 ms  1.682 ms  1.779 ms
 6  n7k-lssnord-1-xwin-po101-1.noc.rwth-aachen.de (134.130.9.130)  1.078 ms  1.282 ms  1.330 ms
 7  cr-fra2-be8-3006.x-win.dfn.de (188.1.242.109)  4.377 ms  4.333 ms  4.748 ms
 8  de-cix-frankfurt.as13335.net (80.81.194.180)  6.875 ms  6.751 ms  6.702 ms
 9  104.27.165.153 (104.27.165.153)  4.693 ms  4.790 ms  4.335 ms

 

That is weird, I was really expecting the packets to get dropped somewhere in the middle. What about 

traceroute -T -p 443 linustechtips.com

(which tests it for HTTPS traffic)?

HTTP/2 203

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Looks like in this case packets go missing after hop 3 of the above traceroutes. 

root@nikh ~ # traceroute -T -p 443 linustechtips.com
traceroute to linustechtips.com (104.27.164.153), 30 hops max, 52 byte packets
 1  137.226.236.1 (137.226.236.1)  0.730 ms  0.859 ms  1.110 ms
 2  n7k-sw23-1-wohnheime-vl1019.noc.rwth-aachen.de (137.226.34.161)  0.686 ms  0.964 ms  1.245 ms
 3  n7k-lssnord-1-et4-14.noc.rwth-aachen.de (137.226.139.37)  0.594 ms  0.797 ms n7k-ww10-1-et4-14.noc.rwth-aachen.de (137.226.139.33)  0.574 ms
 4  * * *

I guess I'll have to send another ticket and see what's up, since this should indicate an issue on my uni's end. Interesting that this only affects HTTPS traffic.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
1 minute ago, ZesIO said:

Looks like in this case packets go missing after hop 3 of the above traceroutes. 


root@nikh ~ # traceroute -T -p 443 linustechtips.com
traceroute to linustechtips.com (104.27.164.153), 30 hops max, 52 byte packets
 1  137.226.236.1 (137.226.236.1)  0.730 ms  0.859 ms  1.110 ms
 2  n7k-sw23-1-wohnheime-vl1019.noc.rwth-aachen.de (137.226.34.161)  0.686 ms  0.964 ms  1.245 ms
 3  n7k-lssnord-1-et4-14.noc.rwth-aachen.de (137.226.139.37)  0.594 ms  0.797 ms n7k-ww10-1-et4-14.noc.rwth-aachen.de (137.226.139.33)  0.574 ms
 4  * * *

I guess I'll have to send another ticket and see what's up, since this should indicate an issue on my uni's end. Interesting that this only affects HTTPS traffic.

That is odd, especially if it only affects some sites. Hopefully they're able to resolve it.

HTTP/2 203

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Yeah, I hope so too. Thanks for your help though! :)

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Forum Bugs and Issues

×