Could not connect to Steam Network... error - Manjaro #8481
Comments
|
Looking through the connection log, this shows up. This is on Manjaro (see system info), as said in followup#3, running Win-client using Wine I can log on with no problems.
|
|
Same result here with an fresh Linux Mint install.... -- |
|
Tested on two other machines on same network.
|
|
At the end of an attempt there is a line stating that "Connectivity test: result=Connected, in progress=0". |
|
Your system information Wine version: wine-valve 3:7.0.1b-1 Tried running Windows steam-client in wine again, once again successful (though with black webrendering). @kisak-valve - seeing that I am able to login to steam using the windows client w/wine-valve, but not using the linux client points to the problem not being the network per se, am I correct? Doing also yields this in the connection_log in /.local/share/steam/logs: Which, correct me if I am wrong, looks like the linux client actually having some sort of connection to the servers? Below, screenshot of windows client running on above system:
|
|
Now Steam works here with "Linux Mint 20.3". All I did was updated to the latest mesa at kisak/kisak-mesa, and the latest amd radeon drivers at oibaf:graphic-drivers Last but not least updated the login manager to use "Mint-Y-Legacy-Dark-Teal" theme at desktop, and use the "Mint-Y-Dark-Teal" theme at the login manager settings with autologin, and now Steam updates and starts correctly. |
|
Hello @kimme, please do not use the kisak-mesa and oibaf PPAs at the same time. Pick one or the other and ppa-purge the one you don't feel like using. They both provide the same packages and mixing packages from both PPAs is not tested or supportable. |
|
I have removed the oibaf:graphic-drivers ppa with ppa-purge. |
And it still works with my settings.... |
|
Ok - not entirely sure (yet) what happened, but as of today my status is:
In between I have updated my Manjaro installation to latest release (but as late as last thursday still no fix). No changes in network etc, so whatever changed is software. |
|
Initial retest (second linux machine, wifi, Pop_OS 22.04) failed, both deb and flatpak installation gave same error as in initial report. Manjaro installation still running a-ok. But I have noticed very slow sync w/cloud for some games. Also client seemingly loosing connection to net and regaining it without any obvious reason. This I have seen before on and off. |
|
My suggestion is to enable the "Adwaita" in any "Mouse Cursor" settings to get the Steam installation rolling. I have enabled the "Adwaita" as "Mouse Cursor" in my "Login Window" settings on my "Linux Mint 20.3", and the Steam installation worked. My theme is "Mint-Y-Legacy-Dark-Teal", and Steam finally works here now. |
|
I started the initial installation from the "Gnome terminal" and it worked. Now when I start "steam" from the terminal, it gives this output... kimme@desktopp:~$ steam The Flathub "Steam" client still gives me the above mentioned error....... |
Same system as initial posting in other words. Also same network, with no changes. Still running but as commented in last post, there still seems to be some connection trouble (client seems to be disconnecting and connecting randomly). Sort of weird too, not that much of a problem when installing games, more so if using cloudsync. Tested again on same second machine which failed with latest Pop_OS, this time with same Manjaro version as above. Wifi connection to same network as working above, but getting the same "Could not connect..." error as before. To sum up - machine I reported about initially is now working (although still not sure why), and second w/identical os and network (though wifi) not working... |
|
...aaand back to square one... ;( Same machine as in last post, no changes since yesterday and on login attemp "Cannot connect..." error... Why?? [``` |
|
Meanwhile, still runs like a charm w/wine on same system. |
|
flatpak version on same machine also same error - "cannot connect to..". |
|
Retest after large stable update May 13. System info: First test: steam --reset, then starting steam in konsole. Same error as before, get to Updating info and immediately the "Could not connect..." error. No changes to hardware, network since post 11 days ago when steam suddenly worked again (and then didn't). Running windows steam client w/wine still works flawlessly. |
|
TLDR; fixed this issue by getting a new router. Long background story: For the past few months I've had this same problem that I've seen described here, and elsewhere, for various flavors of linux. I run a rolling Arch-linux, and this problem popped up out of nowhere after having worked for years. Naturally, I assumed it had something do to with the system being updated, though I wasn't paying too much attention when it happened, so I was not able to pinpoint exactly what triggered it. After having poked around, I noticed that I didn't have the problem when connecting to the internet using my phone as a hotspot. I assumed it was a problem with my ISP, and had several conversations with them about it. They did a few things to try and fix it, they were running a a firewall in front of my router, so they made it into a bridge instead, but that did nothing. Later, after having booted into windows (dual boot on the same system), I realized steam was working perfectly there, so the problem would have to be elsewhere. I went back to trouble shooting my Arch system. My router was an old Zyxel P8702N that was sent to me by my ISP (Telenor) at the time when I got ADSL installed. Originally the admin interface was accessible locally, but the ISP later made it so it was only accessible from the internet, and only from their network. They later discontinued service in my area, so I switched to the ISP I have now, but lost access to the admin interface for the router, so I could not check the logs or do any setup there. That was fine as long as it still worked with the new connection, but since I was able to get steam to work in Windows, I didn't suspect that it would be the source of the problem anyway. To run steam, I would switch to my phone hotspot, run steam, and then switch back to wifi, which sometimes would work, and sometimes not. I was able to play for the most part once I got into a game and got peer-to-peer connection to the other players, but steam would constantly go offline and online again for as long as I was on the wifi, it was unstable but somewhat doable. This whole time, I would google the problem every so often, check the forums, and try every suggestion imagineable, I would completely wipe steam and reinstall, I would reset steam, I tried all the different ways of setting up dns that Arch has to offer, I tried using a wired connection in place of wifi, and bunch of other things, but nothing fixed it. In the end, I got tired of trying everything and I was also having some weird issues with my wifi, so I went and got a new router. The first thing I tried after getting the new router was starting steam, and immediately it came up flawlessly. Changing the router completely fixed the issue, and it hasn't been a problem since. I have no idea what actually caused the problem in the first place, or why it would work in Windows and not linux, but there it is, the problem was with the router. If you haven't tried using a different connection, like with your phone, I would suggest you do, and if that works, take a hard look at your router. All the other things I tried had zero effect, getting a new router fixed it immediately, but I have no idea how I could have known that since all the indications pointed to something with the linux system. So, I figured I'd just tell my story, maybe it's not very interesting, but it solved my problem, maybe it will solve yours. If anyone is interested, I can reconnect my old router and post logs or anything else that would be of interest in perhaps diagnosing the problem more accurately. As far as I could tell, skimming through what other people have posted here, and elsewhere, from their logs and terminal outputs, mine looked the same, so I figured we might all have the same problem, YMMV. edit: corrected the name of old router |
|
System info: @kisak-valve - I stumbled upon a possible solution while looking for Manjaro networking reports where some apps work others don't. After an initial test that failed (like above posts), I followed a posting in Manjaro forums Networking, and added the Google nameservers 8.8.8.8 and 8.8.4.4. to /etc/resolvconf, and checked /etc/resolvconf.conf making sure this line was ok: resolv_conf:/etc/resolv.conf new test, same setup. Starts w/downloading new version, and when logging in updates user info without crashing to "cannot connect...". Updating of installed games works as it should, no intermittent missing network connections. Tested on second system, upgraded to same Manjaro/KDE versions as above, same Nvidia drivers, same Steam versions, and running beta. So only difference from first system is hardware specs (laptop not stationary), plus using Wifi not cabled. Worked perfectly also on this machine. Hope this solves it, but will wait a while before actually saying it solved it ;) |
|
@kisak-valve Still not 100% sure that the nameserver bit was what solved it, but I have been using Steam daily for over a week now and it runs rock solid. Both systems from last post same good performance. As an aside, whereas the little Friends window previously had problems connecting, that too seems to be solved. |
Your system information
Please describe your issue in as much detail as possible:
On and off since January I have had problems running Steam (up til then running flawlessly) increasingly often getting the "Could not connect to Steam Network..." error. Since Feb 24 I have not been able to start Steam at all. I have tried steam --reset, I have tried running with steam -tcp, both have worked earlier but now only present me with the "Could not connect to Steam Network..." error.
After starting I will get to login-window, and on to "Updating Steam information" and then immediately get the "Could not connect to Steam Network..." error.
I have tried every possible solution I could find, up to and including a fresh OS install. Same result. In addition to current kernel (5.16) I have also tried the LTS kernels 5.15 and 5.10 with same results.
I have also found several posts for Manjaro/Arch suggesting networking changes, none of these have had any effect.
Included files are from a fresh OS install (also fresh Steam install, purged version installed with OS, deleted folders, then reinstalled).
Steps for reproducing this issue:
bootstrap_log.txt
cef_log.txt
configstore_log.txt
connection_log.txt
FOLLOWUP #1: Installing flathub version on same system gives same error.
FOLLOWUP #2: Tried installing Fedora 35, latest Pop OS, latest OpenSuse Tumbleweed, same errors there.
FOLLOWUP #3 Installing the windows version using wine (Wine-valve 3.7.0.1b-1 from AUR) installs and runs just fine. Which is strange? Should at least rule out any IP related problems? Still same error with (non-wine) steam-runtime
FOLLOWUP #4 Downgraded Nvidia proprietary driver to 470 series on fresh Manjaro install. Still same error (see #3).
The text was updated successfully, but these errors were encountered: