Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I recall same thing happening to me, but it was always enough to rehost or relaunch the game
(Well, the idea was to see if the PC was the culprit by any means, but it killed multiple birds in one stone)
Even changed Steam download region just to see if it helped, but nope.
This is like you say, it happens from time to time (even loading with a black screen) but it's the first time that I see it during multiple days and it's very strange.
[Deleted the original post I did some days ago and reposting, after some tests with other games (specially 20XX, since that game goes through Epic Online Services for public games but for Steam friends goes through Steam...) public we have 0 luck, but via Steam it worked with no problems, so I'm around 99.9999999% that is Epic Online Services related, even when I got the laptop with another external IP but with the same ISP or when I downloaded the Epic Client to see if it solved everything...]
So, my router has their DHCP done by a Raspberry Pi Zero running Pi-Hole. It seems that after a reset caused when it started, something went wrong and both Google and OpenDNS had something against Epic Online Services.
When I tested the other day I changed from OpenDNS to Google's ones. Because (unknown to me at that point) Google's DNS didn't work too I assumed that everything on that part was perfect and wasn't the culprit.
Today after many days I decided to factory reset the router (why I didn't do it sooner? Because when I did a test with my smartphone as AP and another computer, that didn't work too, even my smartphone wasn't connected to the Wi-Fi and the other PC had that home Wi-Fi disabled, flushed DNS and released IP... I don't know what happened) I assumed that it was indeed my ISP, but not my home connection.
After a factory reset I tested with an arcade public run, I connected and was happy to finally see that it was fixed.
Asked on Discord to double check, it worked, went my merry way to re-enable DHCP through the Raspberry and not from the router, and second test went poof with the same problem. After another test and re-enabling various DNS resolvers and watching that both Google and OpenDNS didn't work but other ones like Cloudflare or Quad9 worked it was clear, something between these 2 DNS providers for the Pi was doing the error and not allowing me toconnect even when I checked the query log they weren't blocked or anything, so...
TL:DR: Pi-Hole and DNS went bananas and ♥♥♥♥♥♥ me for over four days.