Are there issues with GitHub or is T-Mobile randomly blocking access to GitHub?
It's now taking me several attempts just to run the updater as most of the times it instantly fails at the start or during the update process with "no route to host" errors, 403 forbidden errors or SSL errors. The latter two errors are rare for some reason as almost all errors that come up are "no route to host". I've uploaded a few logs showing what the errors look like, both in the terminal and the journal.
My home internet is T-Mobile 5G Home Internet.
Are these issues with GitHub or is T-Mobile throttling and blocking access to GitHub?
54 Replies
Check if you don't have active their "safe web" protection shit, it block random sites for your "safety".
I checked that and it's not enabled. The issue only started happening around two days ago. Additionally I found out this behavior is happening on other services as well (Google, Duckduckgo, Protonmail, Steam, Discord, etc). Usually starts with an unspecified Secure DNS error in Firefox then goes to the usual "host unreachable" for around a minute. Sometimes I get "Connection Refused" errors instead.
maybe some random routing issues? Did you tried running
traceroute to affected sites?
also
did you try doing classical router restart?Sometimes the DNS settings that come with your ISP aren't that great. I usually get less issues iif I use 1.1.1.1 (Cloudflare DNS) or 8.8.8.8 (google's DNS) in my router settings.
yeah or this, it could be good old dns issue
I changed the DNS on my laptop to use Cloudflare's DNS, and in Firefox I use Cloudflare Secure DNS. I can't change the DNS settings in the router or in the app that T-Mobile requires you use to change basic settings.
If I connect to my phone hotspot (my phone also uses T-Mobile but isn't having these issues) the issues go away, but I only have a very small amount of hotspot data each month
you can change them directly in system settings
On the router itself? Or in the app? Because there is no DNS options in either of those
in bazzite
you don't have to change dns in router
Oh, I already did that in Bazzite
I did it over a year ago
try running
traceroute to affected sitesT-Mobile blocks traceroute sadly. Right now I can connect to ghcr but running a traceroute only shows this stuff. It returned after line 30 and never shows a destination.
it dont block it, this is normal output, some loops are hiden
Oh, OK.
I mean you need to run in when site is not working, otherwise it will be okay
plus
add this
traceroute -m 255
you can also try ping to affected sites if you see something like Time to Live Exceeded most of the time is will mean that there is a routing loopOh, OK. Yeah I'll run it when the issue comes up and see what it outputs. Right now the issue isn't occurring so I'll have to wait until it comes back.
I've also tried ping when the issue was occurring
Though pinging affected sites shows no issues when the issue is occurring
well you can wait, maybe it fill fix itself in couple of days if not, i would contact isp
Yeah I might try to contact them if it doesn't fix itself in a couple days
I originally thought it was github and fedora CDNs being overloaded due to Fedora 42 release
oh did you try reseting your router?
Yes I tried resetting the Android router T-Mobile gave us
No change in behavior
damn android router
For your diagnostics maybe try a wifi hotspot with your phone? Then you can see if the issue is the router or not at fault
I did, the issues stopped when connecting to the hotspot from my phone
Even though my phone is also on T-Mobile
Sounding a lot like the router is the problem then
Could it also be de-prioritization? As far as I know home internet service is the lowest priority on T-Mobile
Even lower than Hotspot apparently
Also apparently we have to use the router T-Mobile provides us. We can't use our own according to them
You could try a VPN, and see if it makes a difference
I did try a VPN when the issue was happening and it didn't help at all.
Infact it made it to where I couldn't connect to anything until the issue went away
One more thing to try, have you tried disabling the wifi powersaving mode? https://docs.bazzite.gg/General/issues_and_resolutions/#wi-fi-lag-spikes sometimes it can do weird things with your wifi
I'll try that
OK the wifi powersaving mode was on, so I'm going to disable that
Hopefully it helps a bit
It didn't work, instead it caused WiFi to stop working completely
Apparently it didn't like what was in the file that the guide had me create
"Failed to read configuration: /etc/NetworkManager/conf.d/wifi-powersave-off.conf: Key file contains line “wlp0s20f3” which is not a key-value pair, group, or comment"
Thats what was in the journal
unless I was not supposed to replace the [connection] part
yeah you paste the command as is
[connection] isn't a placeholder
OK yeah it worked now
Thought I had to target the wifi device itself
Hopefully it makes a difference 🙂
@Pryka @wolfyreload Sorry for the pings but the issue occurred again and I immediately ran a traceroute on the affected domain, and this was the result. It stopped at line 9 with '!X' next to all the timings. I'm guessing this is a router issue?
!X means that it was blocked deliberately. I would contact your ISP.
I'd imagine that your machine is 192.168.12.1 and that the router is 192.0.0.1. Looks like your problem is the router, so yeah ISP issue
Yeah, agree.
Keep that screen. If you manage to contact some technicians it can be helpful
I'll go and do that. Not sure why they would be randomly blocking Github and various other services. I also ran a traceroute while connected to my Hotspot (which is working and I can connect to that site through it) and it never actually shows a destination, just countless rows of '* * *'.
Maybe it's a hardware issue with the router.
Hard to tell.
OK I did research and it's normal for a successful traceroute on tmobile to get into a loop with three stars since they do block it on their home internet service
Stars are fine
The issue here is !X
Yeah I knew that when it came up as it never got past the router
didn't know it was being blocked but knew something was wrong
Yeah it dies in router
Looks like a hardware issue to me.
Could this also be caused by the router having hardware issues? Same issue was and is still happening randomly to DuckDuckGo and various other sites and services so I did a couple traceroutes to affected services to see if the behavior was the same. First one gets out to the actual internet but ends up back at the router, whereas the second one stops at a completely different IP address (10.160.107.34). During both traceroutes said sites were inaccessible with similar errors to what I was getting in ujust update.
I also contacted the ISP about the issue and they said they could not and would not tell me why the issue was occurring or what the actual cause was. They were able to tell me that the router hardware was not what was causing it though. Not sure why they're being sketchy about it.
I don't see why they would randomly block some sites for couple of seconds.
For me it looks like hardware(router) issue or internal ISP issues.
Yeah I'm thinking it might be something with the ISP or a bad update pushed to the router. It was updated at night automatically a few days ago.
Strange they won't give me anymore information though.
Tbh I always had to fight my ISP when it comes to connection fuckups. They always deflect to me, your issue, all is fine on our site.
It was always the same story.
The only tactic that did work, was persistence.
I remember when 2FA from Sony did not reach my Phone. Sony pointed me to T-mobile and T-mobile to Sony.
I was calling Sony almost daily... And proved to them that this is their issue. And I was right.
I had similar story with a local IPS years ago. No no, everything is fine, you are doing something wrong... I was bugging them daily untill they fucking send a technician who fix physical issue in building.
This is almost always a struggle...
OK I'll keep testing and contacting them. I did notice when testing additional devices and operating systems that devices running Windows, Android or iOS were being affected far less or not at all, whereas devices running Linux or other open-source operating systems were being affected by it more.
If they are all affected is definitely something wrong.
@TheMCNerd2018 also suggesting that if they won't help in any way you won't extend your contract helps 😛
Why pay for defective service?
Sadly because everything else is far more expensive in my area, also I have multiple other people on the plan that do not want to be disturbed or go through all the troubles of changing internet service.
Yeah yeah I know, but they don't - T-Mobile
I really want to change to a better service, specifically actual Fiber service since it's actually available in my area. Alas because the other people in my household are fine with the current service they don't want it changed.
Pain