protonscr

Steam does not start when loopback is not allowed

steamclosed
ValveSoftware/steam-for-linux#11920 · opened 2025-04-20 by mackerel225 · updated 2025-04-20 · 1 comments · github
Mmackerel225 2025-04-20 github

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

Steps for reproducing this issue:

  1. have iptables with outgoing and incoming packets for loopback to deny
  2. start steam
  3. steam crashes with "Steam encountered an unexpected error during startup (0x3000)".

nftables config

table inet filter {
  chain input {
    type filter hook input priority 0
    policy drop

    ct state invalid drop comment "early drop of invalid connections"
    ct state {established, related} accept comment "allow tracked connections"

    counter
  }

  chain forward {
    type filter hook forward priority 0
    policy drop

    counter
  }

  chain output {
    type filter hook output priority 0
    policy drop

    tcp dport {80, 443} accept comment "Allow 80 and 443"

    counter
  }
}

The issue is resolved if you allow outgoing and incoming loopback, but that shouldn't be necessary.

This might be related - https://github.com/ValveSoftware/steam-for-linux/issues/5082

Kkisak-valve maintainer 2025-04-20 github

Hello @mackerel225, Steam needs to be able to talk to its web component. This issue is already being tracked at #3135. Closing as a duplicate.