You are not logged in.

#1 2021-11-25 18:12:10

boredhero
Member
Registered: 2020-10-14
Posts: 14

Issues with various apps talking to servers (Steam, Discord, Paradox)

I'll be the first to admit that I am not particularly familiar with networking.
I am currently experiencing an assortment of issues with apps but they do not occur in Firefox. Steam works fine in browser, but I want to play games that use the steam friends network to handle multiplayer. Discord works fine in browser as well, but the application tries and fails to connect to servers to check for updates and otherwise connect to servers at all. I play Stellaris a lot, and if I launch it directly, the Paradox Launcher is unable to connect to its servers to let me log in. All of these things work just fine in Firefox, but outside of Firefox they seem to have an issue.

Things Ive Tried:
Steam: Steam beta client, steam native runtime, ensuring I have the 32-bit dependencies installed as is indicated on the wiki page for steam troubleshooting, cache clearing for web browser and download in steam, clean install of steam, reboots
Discord: Multiple clean installs of discord, discord-canary, and discord-dev. Same sort of issues with not being able to reach servers.
Paradox Launcher: Can launch this directly from the desktop icon or by searching for it, but it's useless as Paradox can't connect to it's servers to log me in nor can it connect to the steam Friend Network. Tried clean installing stellaris

I believe this may be some sort of DNS issue based on some other old reddit posts and forum posts I've found from a few years ago, but haven't had any luck. I've tried enabling nscd.service and restarting. I've tried enabling systemd-resolved and restarting. Nothing seems to work and I'm at a loss. I don't really understand DNS beyond the very top level.

My system is up to date and otherwise free of issues.

Here is my /etc/hosts

# Static table lookup for hostnames.
# See hosts(5) for details.
127.0.0.1      localhost
::1            localhost
127.0.1.1      noaharchgaminglaptop.localdomain noaharchgaminglaptop

Last edited by boredhero (2021-11-25 18:13:32)

Online

#2 2021-11-30 17:16:30

SilverStraw
Member
Registered: 2021-11-25
Posts: 1

Re: Issues with various apps talking to servers (Steam, Discord, Paradox)

You can try replacing the contents of /etc/hosts with this:

127.0.0.1      localhost
127.0.1.1      noaharchgaminglaptop.localdomain noaharchgaminglaptop
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

I was having connectivity issues with Uplay (Ubisoft Connect) and this helped.

Offline

#3 2021-12-01 21:51:21

boredhero
Member
Registered: 2020-10-14
Posts: 14

Re: Issues with various apps talking to servers (Steam, Discord, Paradox)

SilverStraw wrote:

You can try replacing the contents of /etc/hosts with this:

127.0.0.1      localhost
127.0.1.1      noaharchgaminglaptop.localdomain noaharchgaminglaptop
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

I was having connectivity issues with Uplay (Ubisoft Connect) and this helped.

Unfortunately this did not solve the problem even after a reboot sad
I think I'm gonna just have to clean install at this point...

Online

#4 2021-12-02 08:28:45

seth
Member
Registered: 2012-09-03
Posts: 25,086

Re: Issues with various apps talking to servers (Steam, Discord, Paradox)

boredhero wrote:

I think I'm gonna just have to clean install at this point...

Bullshit. Also you'll likely just end up in the same situation again.

The DNS estimation is sound, FF will likely use its internal resolution mechanism.

So let's see. Outputs of

ip a; ip r
ping -c1 8.8.8.8 google.com
ping -c1 google.com
drill  @8.8.8.8 google.com
drill google.com
nslookup google.com
stat /etc/resolv.conf
cat /etc/resolv.conf
cat /etc/nsswitch.conf
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Offline

#5 Today 21:56:36

boredhero
Member
Registered: 2020-10-14
Posts: 14

Re: Issues with various apps talking to servers (Steam, Discord, Paradox)

seth wrote:
boredhero wrote:

I think I'm gonna just have to clean install at this point...

Bullshit. Also you'll likely just end up in the same situation again.

The DNS estimation is sound, FF will likely use its internal resolution mechanism.

So let's see. Outputs of

ip a; ip r
ping -c1 8.8.8.8 google.com
ping -c1 google.com
drill  @8.8.8.8 google.com
drill google.com
nslookup google.com
stat /etc/resolv.conf
cat /etc/resolv.conf
cat /etc/nsswitch.conf
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Outputs as requested, in order. Sorry for late reply.

❱ ip a; ip r
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 
       valid_lft forever preferred_lft forever
2: enp59s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 54:bf:64:14:a4:6c brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:b8:6d:58:37:d4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.227/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 86367sec preferred_lft 86367sec
    inet6 fe80::cc8d:c0a6:6ec0:1717/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 
192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.227 metric 600 
❱ ping -c1 8.8.8.8 google.com 
PING google.com (172.217.12.238) 56(124) bytes of data.

--- google.com ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
❱ ping -c1 google.com
PING google.com (172.217.12.238) 56(84) bytes of data.
64 bytes from iad30s15-in-f14.1e100.net (172.217.12.238): icmp_seq=1 ttl=59 time=10.8 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 10.839/10.839/10.839/0.000 ms
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 25982
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.	IN	A

;; ANSWER SECTION:
google.com.	214	IN	A	142.251.45.14

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 15 msec
;; SERVER: 8.8.8.8
;; WHEN: Mon Dec  6 16:53:33 2021
;; MSG SIZE  rcvd: 44
❱ drill google.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 47557
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.	IN	A

;; ANSWER SECTION:
google.com.	253	IN	A	172.217.2.110

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 14 msec
;; SERVER: 192.168.1.1
;; WHEN: Mon Dec  6 16:53:57 2021
;; MSG SIZE  rcvd: 44
❱ nslookup google.com
Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
Name:	google.com
Address: 142.250.73.238
Name:	google.com
Address: 2607:f8b0:4004:807::200e
❱ stat /etc/resolv.conf
  File: /etc/resolv.conf
  Size: 72        	Blocks: 8          IO Block: 4096   regular file
Device: 8,18	Inode: 3409810     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-12-06 16:48:56.739923817 -0500
Modify: 2021-12-06 16:48:55.119923822 -0500
Change: 2021-12-06 16:48:55.119923822 -0500
 Birth: 2021-12-06 16:48:55.119923822 -0500
❱ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 1.1.1.1
nameserver 192.168.1.1
❱ cat /etc/nsswitch.conf 
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files

publickey: files

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files
❱ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
ckb-next-daemon.service                  | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nscd.service                             | multi-user.target.wants
optimus-manager.service                  | graphical.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved.service                 | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

Online

#6 Today 23:08:33

seth
Member
Registered: 2012-09-03
Posts: 25,086

Re: Issues with various apps talking to servers (Steam, Discord, Paradox)

So systemd-resolved is active, but operates as a client of /etc/resolv.conf where networkmanager has configured 1.1.1.1 (cloudflare) as main DNS and 192.168.1.1 as secondary.
You actually can resolve (and ping) google.com through various mechanisms.

What might be at play is ambiguity between nscd and resolved, can you

resolvectl query discord.com # ideally use the domain that discord actually fails to resolve

And what if you disable both, systemd-resolved and nscd?

---

seth wrote:

ping -c1 8.8.8.8 google.com

ftr, copy-and-fail, should have been "ping -c1 8.8.8.8" but it doesn't matter since you can even ping the domain.

Offline

Board footer

Powered by FluxBB