You are not logged in.

#1 2025-06-28 01:32:38

upstartmass
Member
Registered: 2025-06-28
Posts: 10

[SOLVED] Steam cannot connect to internet(Error Code: -105)

Since yesterday, I have had an issue with Steam not properly connecting to the internet. However, my internet seems to be fine, as the I am currently accessing this website on the same computer and network. Also ping properly returns packets from terminal. Strangely, steam worked up until the point that I tried to setup a VPN yesterday. Because of that, I tried to reverse what ever I did yesterday, by completely deleting OpenVPN and ProtonVPN off of the system, but it didn't work. Next I tried to figure out if there was some kind of firewall issue (which hasn't been an issue before as this is my home network), but it doesn't say that my ports are blocked.

This is the current output of iptables (I am not really sure what this means).

 -> % sudo iptables -L -v                                        
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

When I run ip route I don't see any indication that I could still be connected to a VPN, as there is no tun0.

I also tried deleting the cache, reinstalling steam, installing the flatpak version, and none of them seem to work. Also strangely, I can see my friends list and see who is online, but cannot access anything else that requires internet, such as community posts and the store.

I believe it is likely related to the VPN installation, but I have exhausted my options as to trying to fix this myself and am not sure what else to try.

Last edited by upstartmass (2025-06-28 15:24:35)

Offline

#2 2025-06-28 06:36:47

-thc
Member
Registered: 2017-03-15
Posts: 936

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

Please post the output of

ip a
ip -4 r
ip -6 r
ls -l /etc/resolv.conf
cat /etc/resolv.conf
resolvectl status

Offline

#3 2025-06-28 06:52:11

seth
Member
Registered: 2012-09-03
Posts: 66,327

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

Relevant steam ports: https://help.steampowered.com/en/faqs/v … -DA21-31EB

Did you end up installing nftables for your VPN shenanigans?
https://wiki.archlinux.org/title/Nftabl … e_firewall - this is active by default and blocks any inbound but ssh.
Also check nft ruleset and tables.

Edit: apparently steam yells that error on DNS issues
Next to -thc's list

drill steampowered.com
nslookup steampowered.com

Last edited by seth (2025-06-28 06:54:15)

Offline

#4 2025-06-28 06:57:15

upstartmass
Member
Registered: 2025-06-28
Posts: 10

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

-thc wrote:

Please post the output of

ip a
ip -4 r
ip -6 r
ls -l /etc/resolv.conf
cat /etc/resolv.conf
resolvectl status

Here is the result:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp9s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 58:11:22:4c:18:8a brd ff:ff:ff:ff:ff:ff
    altname enx5811224c188a
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 2c:8d:b1:5c:a6:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.243/24 metric 600 brd 192.168.0.255 scope global dynamic wlan0
       valid_lft 143490sec preferred_lft 143490sec
    inet6 2600:8804:8780:270::a7ce/128 scope global dynamic noprefixroute 
       valid_lft 57092sec preferred_lft 57092sec
    inet6 2600:8804:8780:270:2e8d:b1ff:fe5c:a620/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 86387sec preferred_lft 86387sec
    inet6 fe80::2e8d:b1ff:fe5c:a620/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.243 metric 600 
68.105.28.12 via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.243 metric 600 
68.105.29.11 via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.243 metric 600 
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.243 metric 600 
192.168.0.1 dev wlan0 proto dhcp scope link src 192.168.0.243 metric 600 
2600:8804:8780:270::/64 dev wlan0 proto ra metric 600 expires 86386sec pref medium
fe80::/64 dev wlan0 proto kernel metric 256 pref medium
default nhid 1573764466 via fe80::8e76:3fff:fe2d:7bc1 dev wlan0 proto ra metric 600 expires 166sec pref medium
-rw-r--r-- 1 root root 47 Jun 25 17:50 /etc/resolv.conf
# Generated by resolvconf
nameserver 10.96.0.1
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
  Current DNS Server: 10.96.0.1
         DNS Servers: 10.96.0.1
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net
                      8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com
                      2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

Link 2 (enp9s0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

Link 4 (wlan0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 68.105.29.11
       DNS Servers: 68.105.29.11 68.105.28.12
     Default Route: yes

Offline

#5 2025-06-28 07:00:38

upstartmass
Member
Registered: 2025-06-28
Posts: 10

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

seth wrote:

Relevant steam ports: https://help.steampowered.com/en/faqs/v … -DA21-31EB

Did you end up installing nftables for your VPN shenanigans?
https://wiki.archlinux.org/title/Nftabl … e_firewall - this is active by default and blocks any inbound but ssh.
Also check nft ruleset and tables.

Edit: apparently steam yells that error on DNS issues
Next to -thc's list

drill steampowered.com
nslookup steampowered.com

I actually did find that page with the relevant steam ports during my research, and tried to run some commands to ensure that they were forced open, but it didn't seem to have an effect. Potentially because I am not super familiar with networking.

And as far as I can remember, I don't think I downloaded nftables. I was mostly just working with OpenVPN and ProtonVPN.

Offline

#6 2025-06-28 07:04:02

seth
Member
Registered: 2012-09-03
Posts: 66,327

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

nft list rulesetnft list ruleset

Did you btw meatime reboot (as this will flush everything netfilter that wireguard/any vpn will have added)

Offline

#7 2025-06-28 07:18:33

upstartmass
Member
Registered: 2025-06-28
Posts: 10

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

seth wrote:
nft list rulesetnft list ruleset

Did you btw meatime reboot (as this will flush everything netfilter that wireguard/any vpn will have added)

I think that command is throwing an error:

Error: syntax error, unexpected string
list rulesetnft list ruleset
     ^^^^^^^^^^

Also, by reboot do you mean restarting the PC? Because I did try that a few times and it didn't work, so some of setting must have been changed somehow.

Offline

#8 2025-06-28 07:20:42

seth
Member
Registered: 2012-09-03
Posts: 66,327

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

LOL, ctrl+p bounced.

nft list ruleset

but you /have/ https://archlinux.org/packages/extra/x86_64/nftables/ installed… so in doubt it's its firewall.
Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Offline

#9 2025-06-28 07:25:35

upstartmass
Member
Registered: 2025-06-28
Posts: 10

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

seth wrote:

LOL, ctrl+p bounced.

nft list ruleset

but you /have/ https://archlinux.org/packages/extra/x86_64/nftables/ installed… so in doubt it's its firewall.
Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

lol, even funnier is the fact that I didn't even notice that it was the same command twice. It just looked like a typical command tongue

But here is the output (the typo command didn't return anything):

-> % find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
iwd.service                              | multi-user.target.wants
jellyfin.service                         | multi-user.target.wants
nvidia-hibernate.service                 | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-suspend.service.wants
nvidia-resume.service                    | systemd-suspend-then-hibernate.service.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-network-generator.service        | sysinit.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Offline

#10 2025-06-28 07:43:19

seth
Member
Registered: 2012-09-03
Posts: 66,327

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

The nftables.service isn't enabled - did you check drill and nslookup for steampowered.com ?

There's a disparity: some resolvconf got you the PNR 10.96.0.1 (which isn't your current segment) while the wifi connection is on 68.105.29.11 (your ISP)
Probably just fix the resolv.conf and re-establish the stub resolver symlink, https://wiki.archlinux.org/title/Systemd-resolved#DNS

Offline

#11 2025-06-28 15:24:06

upstartmass
Member
Registered: 2025-06-28
Posts: 10

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

seth wrote:

The nftables.service isn't enabled - did you check drill and nslookup for steampowered.com ?

There's a disparity: some resolvconf got you the PNR 10.96.0.1 (which isn't your current segment) while the wifi connection is on 68.105.29.11 (your ISP)
Probably just fix the resolv.conf and re-establish the stub resolver symlink, https://wiki.archlinux.org/title/Systemd-resolved#DNS

Solved! I'm don't entirely understand what went wrong, but just in case someone in the future ever as the same problem, the following command fixed my issue with resolv.conf.

ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

Thank you so much for your help.

Offline

#12 2025-06-28 15:33:22

seth
Member
Registered: 2012-09-03
Posts: 66,327

Re: [SOLVED] Steam cannot connect to internet(Error Code: -105)

When setting up the VPN something or someone replaced the resolv.conf symlink to the stub resolver w/ a real file with contents suitable for the VPN (but the DNS won't work w/o)
This condition never gets "automatically" undone.

In your defense: depending the resolved behavior on the filetype and a symlink to a different, incompatible config file sure sounded like a brilliant idea in someones head at some point, but in reality it's the dumb, convoluted, fragile shit that makes systemd so annoying.

Offline

Board footer

Powered by FluxBB