SorceForge - Will Not Load

Recently I have noticed sourceforge.net will not load into a web browser. Have tried Firefox, Brave and Chrome on my T440 and T550 running Endevouros. Will not load on my wife’s iPad or Chromebook. Have tried thru my NETGEAR range extender as well as direct from my thinkpads wifi to weak nearby source. Have tried Endevouros installed on my Thinkpads, as well as “Live” boots of Endevouros and MxLinux on my Thinkpads.

One exception to above is that I can access SourceForge normally using “TOR Browser”.
Obously this is causing me problems accessing certain packages using AUR helpers, I.E., Yayourt, Yay, Pamac.

Has anyone a suggestion as to what the cause is and any possible remedy?

Have been using Endevouros c/w XFCE DE for several months, love it, love it, love it!

Thanks so much,

Wayne

Sounds like it is being blocked by something in your network or by your ISP.

Are you running any network-wide blocking/filtering? Is it possible whoever is providing your internet is proxying or filtering your traffic?

Try running

 traceroute sourceforge.net 
1 Like

Just in case traceroute not found,

yay -S traceroute

.:wink:

1 Like

Loads instantly! Firefox :fox_face:

1 Like

Thanks so much all!

I don’t understand what traceroute is revealing ??

traceroute sourceforge.net
traceroute to sourceforge.net (204.68.111.105), 30 hops max, 60 byte packets
1 _gateway (10.254.250.1) 5.665 ms 6.078 ms 6.066 ms
2 10.5.0.1 (10.5.0.1) 11.337 ms 12.612 ms 12.596 ms
3 100.127.41.238 (100.127.41.238) 14.795 ms 15.885 ms 12.561 ms
4 100.120.124.42 (100.120.124.42) 12.547 ms 16.109 ms 14.934 ms
5 ashbbprj02-ae2.0.rd.as.cox.net (68.1.4.139) 22.230 ms 19.998 ms 22.206 ms
6 173.245.63.44 (173.245.63.44) 22.195 ms 19.637 ms 18.960 ms
7 172.70.36.4 (172.70.36.4) 19.380 ms 173.245.63.239 (173.245.63.239) 16.706 ms 173.245.63.243 (173.245.63.243) 38.647 ms
8 172.70.133.6 (172.70.133.6) 41.013 ms 172.70.33.106 (172.70.33.106) 41.491 ms 172.70.133.182 (172.70.133.182) 40.345 ms
9 172.70.133.77 (172.70.133.77) 39.140 ms 172.70.33.174 (172.70.33.174) 39.905 ms 172.70.133.186 (172.70.133.186) 37.540 ms
10 172.70.41.89 (172.70.41.89) 42.357 ms 172.70.173.35 (172.70.173.35) 41.859 ms 162.158.77.62 (162.158.77.62) 44.045 ms
11 * * *
12 204.68.111.105 (204.68.111.105) 98.594 ms 98.346 ms 78.734 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

My internet comes from the “LandLord”, can not imagine why he would block SourceForge, can not really rule it out!.

Perhaps I should try it from my local Starbucks???

Wayne

Loads like this! :fox_face:

simplescreenrecorder-2021-11-26_10.46.29.mkv (1.4 MB)

It is revealing that your traffic just isn’t getting there. How long has this been going on? If it is very recent, it might fix itself. If not, someone would need to contact your ISP to work with them to understand what is happening.
EDIT: It looks like Rick is getting the same result so that isn’t useful here.

I ran traceroute on it also. It pops right up in the browser.

[ricklinux@eos-kde ~]$ traceroute sourceforge.net
traceroute to sourceforge.net (204.68.111.105), 30 hops max, 60 byte packets
 1  _gateway (192.168.2.1)  0.646 ms  0.763 ms  0.967 ms
 2  10.11.5.9 (10.11.5.9)  6.684 ms  6.678 ms  6.732 ms
 3  * * *
 4  64.230.52.186 (64.230.52.186)  28.568 ms  28.615 ms  28.907 ms
 5  tcore4-chicagocp_hundredgige0-4-0-0.net.bell.ca (64.230.79.157)  26.923 ms  26.912 ms  27.022 ms
 6  bx6-chicagodt_0-7-0-0.net.bell.ca (64.230.79.87)  24.652 ms  31.085 ms  31.383 ms
 7  141.101.73.14 (141.101.73.14)  29.099 ms  21.039 ms  21.077 ms
 8  172.70.124.2 (172.70.124.2)  35.722 ms 172.70.176.2 (172.70.176.2)  37.202 ms 141.101.73.18 (141.101.73.18)  28.722 ms
 9  172.70.125.30 (172.70.125.30)  24.837 ms 172.70.125.39 (172.70.125.39)  24.493 ms 172.70.129.32 (172.70.129.32)  20.538 ms
10  108.162.217.24 (108.162.217.24)  23.666 ms 172.70.129.123 (172.70.129.123)  20.333 ms 172.70.129.45 (172.70.129.45)  21.460 ms
11  172.70.177.86 (172.70.177.86)  18.974 ms 108.162.217.15 (108.162.217.15)  20.024 ms 172.70.177.98 (172.70.177.98)  20.100 ms
12  * * *
13  204.68.111.105 (204.68.111.105)  69.389 ms  69.444 ms  68.365 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
[ricklinux@eos-kde ~]$ 
1 Like

Ehh…in that case traceroute might not be useful. I guess that icmp traffic might not be able to get there.

I would suggest about two weeks, previously it loaded without issue. I agree, it can only be my provider!

Is there any way I can get pamac to use “TOR Browser” to connect ?

Wayne

A ping of sourceforge.net works …

[wayne@wayne-20cjs1mw00 ~]$ ping sourceforge.net
PING sourceforge.net (204.68.111.105) 56(84) bytes of data.
64 bytes from 204.68.111.105 (204.68.111.105): icmp_seq=1 ttl=53 time=94.7 ms
64 bytes from 204.68.111.105 (204.68.111.105): icmp_seq=2 ttl=53 time=77.3 ms
64 bytes from 204.68.111.105 (204.68.111.105): icmp_seq=3 ttl=53 time=79.3 ms
64 bytes from 204.68.111.105 (204.68.111.105): icmp_seq=4 ttl=53 time=77.8 ms
^C
sourceforge.net ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 77.285/82.276/94.739/7.233 ms
[wayne@wayne-20cjs1mw00 ~]$

???
Wayne

If you can ping it, but can’t hit it in a web browser, it seems likely that something is blocking your http/https traffic.

Thanks so very much to one and all!

I will, in time take my machine to an alternate access location to see if I have success there, that may not fix the problem but it may help sooth curiosity! Thanks again everybody!

Wayne

1 Like

Is it a DNS problem? Are you pinging the web address or the IP address?

Rick,

Interesting!, the command I gave was >ping sourceforge.net< . I am, shall we say, just a simple ordinary citizen, there would be no point of anyone blocking “ME”! Unless someone else on this wifi network is doing something unusual. Interesting, suspenseful. ha!

Wayne