protonscr

Friends list will not load. Steam attempts to connect to incorrect URL.

steamclosed Web
ValveSoftware/steam-for-linux#7310 · opened 2020-08-09 by navennn · updated 2020-10-01 · 7 comments · github
Nnavennn 2020-08-09 github

Your system information

  • Steam client version (build number or date): 1596762082
  • Distribution (e.g. Ubuntu): Uubntu
  • Opted into Steam client beta?: [Yes/No] tried both
  • Have you checked for system updates?: [Yes/No] yes/updated

Please describe your issue in as much detail as possible:

I am having an issue with friends list. Very frequently it doesn't load.
I checked /home/username/.steam/error.log. And this is what it says:

[0809/091813.005034:ERROR:ssl_client_socket_impl.cc(935)] handshake failed; returned -1, SSL error code 1, net_error -200
[0809/091813.069017:ERROR:ssl_client_socket_impl.cc(935)] handshake failed; returned -1, SSL error code 1, net_error -200

I traced the website that steam is attempting to connect to with tcpdump (when clicking to retry to connect with friends list):

11:32:52.184813 IP naven-GV72-8RC.33126 > a104-103-89-82.deploy.static.akamaitechnologies.com.https: Flags [S], seq 4285047090, win 64240, options [mss 1460,sackOK,TS val 304211364 ecr 0,nop,wscale 7], length 0
11:32:52.211759 IP a104-103-89-82.deploy.static.akamaitechnologies.com.https > naven-GV72-8RC.33126: Flags [S.], seq 3964677010, ack 4285047091, win 28960, options [mss 1460,sackOK,TS val 719006465 ecr 304211364,nop,wscale 7], length 0
11:32:52.211785 IP naven-GV72-8RC.33126 > a104-103-89-82.deploy.static.akamaitechnologies.com.https: Flags [.], ack 1, win 502, options [nop,nop,TS val 304211391 ecr 719006465], length 0
11:32:52.211957 IP naven-GV72-8RC.33126 > a104-103-89-82.deploy.static.akamaitechnologies.com.https: Flags [P.], seq 1:518, ack 1, win 502, options [nop,nop,TS val 304211392 ecr 719006465], length 517
11:32:52.241104 IP a104-103-89-82.deploy.static.akamaitechnologies.com.https > naven-GV72-8RC.33126: Flags [.], ack 518, win 235, options [nop,nop,TS val 719006495 ecr 304211392], length 0
11:32:52.242895 IP a104-103-89-82.deploy.static.akamaitechnologies.com.https > naven-GV72-8RC.33126: Flags [.], seq 1:1449, ack 518, win 235, options [nop,nop,TS val 719006495 ecr 304211392], length 1448
11:32:52.242906 IP naven-GV72-8RC.33126 > a104-103-89-82.deploy.static.akamaitechnologies.com.https: Flags [.], ack 1449, win 501, options [nop,nop,TS val 304211423 ecr 719006495], length 0
11:32:52.243578 IP a104-103-89-82.deploy.static.akamaitechnologies.com.https > naven-GV72-8RC.33126: Flags [.], seq 1449:2897, ack 518, win 235, options [nop,nop,TS val 719006495 ecr 304211392], length 1448
11:32:52.243584 IP naven-GV72-8RC.33126 > a104-103-89-82.deploy.static.akamaitechnologies.com.https: Flags [.], ack 2897, win 501, options [nop,nop,TS val 304211423 ecr 719006495], length 0
11:32:52.243781 IP a104-103-89-82.deploy.static.akamaitechnologies.com.https > naven-GV72-8RC.33126: Flags [P.], seq 2897:4097, ack 518, win 235, options [nop,nop,TS val 719006495 ecr 304211392], length 1200
11:32:52.243785 IP naven-GV72-8RC.33126 > a104-103-89-82.deploy.static.akamaitechnologies.com.https: Flags [.], ack 4097, win 501, options [nop,nop,TS val 304211423 ecr 719006495], length 0
11:32:52.245377 IP a104-103-89-82.deploy.static.akamaitechnologies.com.https > naven-GV72-8RC.33126: Flags [P.], seq 4097:5269, ack 518, win 235, options [nop,nop,TS val 719006496 ecr 304211392], length 1172

a104-103-89-82.deploy.static.akamaitechnologies.com translates to 104.103.89.82

;; ANSWER SECTION:
a104-103-89-82.deploy.static.akamaitechnologies.com. 1325 IN A 104.103.89.82

When I go to this website, certificate's common name is controlleddisbursements.cnb.com, which is definitely incorrect. That is probably the reason for SSL fault seen in error.log.
Please, investigate this.

Skärmbild från 2020-08-09 09-26-47

Steps for reproducing this issue:

Sometimes it works, sometimes it doesn't. Seems to be related to loadbalancing (I sometimes get a proper URL, sometimes not)

I had opened a ticket to support, who redirected me here; Ticket: HT-2RRK-MB97-83Y8

Thanks
Adam

Tthoughton 2020-08-09 github

Same issue as the OP's topic here.
Interestingly, game updates do still download.

ZZackyist 2020-08-13 github

Having the same issue with the error message "FRIENDS NETWORK UNREACHABLE" showing all the time. It was working a month ago and I was using the latest beta version available to me. I opted out of beta today but that didn't help and neither did clearing Steam caches or setting TZ variables (found as old solutions on the web).

I haven't been able to connect to the Friends network for a week now, despite smashing the Retry button continuously. Everything else seems to work but this is kind of breaking for me, not being able to play with friends.

EDIT: Added my system info in case it helps:
Your system information

  • Steam client version (build number or date): 1596217132
  • Distribution (e.g. Ubuntu): elementary OS 5.1.7 Hera
  • Opted into Steam client beta?: [Yes/No] No, but also had the same issue with the beta before opting out today
  • Have you checked for system updates?: [Yes/No] Yes, just updated every package available today
TTriMoon 2020-08-16 github

@navennn

When I go to this website, certificate's common name is controlleddisbursements.cnb.com, which is definitely incorrect. That is probably the reason for SSL fault seen in error.log.
Please, investigate this.

Looking at that CN you provided it contains the word disbursement which indicates a problem with payments from the side of the ones using that server-name (eg. Valve) :wink:
Because IIRC akamai is a CDN...
Maybe a traceroute could help identify which server they didn't pay :rofl:

Nnavennn 2020-08-17 github

It should be a trivial fix from Valve side.
P.S. I realized that tcpdump was wrong, I updated my post with a fresh one.

ZZackyist 2020-08-30 github

Just updating that for me, the new Steam version seems to have fixed this problem even though I didn't notice any fix in the changelog. The working version is 1598665466 from August 29th.

Nnavennn 2020-08-31 github

I guess it is resolved. Last time I had this issue was on August 21st, judging by routers' logs at least.

Nnavennn 2020-10-01 github

The issue has not reoccurred for over a month now.

Nothing extracted yet.