Interactive troubleshooting
Fix Progress
Try the steps in order. Open each step, follow the instructions, then mark the step that solved the problem.
Exit Steam completely instead of closing only its window. Right-click the Steam icon in the Windows notification area, select Exit, wait 20 seconds, and reopen Steam. Open both the Store and Community tabs.
Verification:
The Store and Community pages should load without the “Unable to connect to server” message. If Error Code 105 returns, continue to the next step.
Open Steam, select Steam > Settings > In Game, locate Delete Web Browser Data, and select Delete. Close Steam completely and reopen it. This removes cached web files and cookies used by the client’s Store, Community, profile, and market pages. It does not remove installed games or local save files.
Verification:
Open the Steam Store, then open a Community page. If both display normally, damaged or stale browser data caused the error.
Turn off the modem and router, disconnect their power for 30 seconds, reconnect them, and wait until the internet connection returns. Test Steam again. If the error remains, connect the computer temporarily to a phone hotspot.
Verification:
If Steam works through the hotspot but not through the normal connection, the problem is linked to the router, internet provider, DNS resolver, or a network-level filter.
Open Start, type Command Prompt, select Run as administrator, and run:
ipconfig /flushdns
Close Steam before running the command, then reopen it after Windows reports that the DNS resolver cache was cleared.
Verification:
Run “nslookup store.steampowered.com” in Command Prompt. The result should return one or more addresses rather than a timeout or name-resolution failure.
Open Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings. Right-click the active Wi-Fi or Ethernet adapter, select Properties, open Internet Protocol Version 4 (TCP/IPv4), and choose Use the following DNS server addresses. Enter 8.8.8.8 as the preferred server and 8.8.4.4 as the alternate server. Save the changes, flush the DNS cache again, and restart Steam.
Verification:
Confirm that store.steampowered.com opens in both a normal browser and the Steam client. If it does, the previous DNS resolver was unavailable, slow, filtered, or returning stale records.
Disconnect any VPN, gaming tunnel, proxy application, secure DNS filter, traffic optimizer, or network-level ad blocker. In Windows, open Settings > Network & internet > Proxy and disable Use a proxy server unless the network administrator requires it. Restart Steam after changing the setting.
Verification:
If Steam loads with the VPN or proxy disabled, reconnect the service and select another server or exclude Steam from its filtering rules.
Open Windows Security > Firewall & network protection > Allow an app through firewall. Select Change settings and confirm that Steam is allowed on the active network profile. If the existing entry appears damaged, remove it, reopen Steam, and approve the new network-access prompt. Do not leave the firewall disabled after testing.
Verification:
Open the Steam Store, Community, Friends, and Downloads pages. Normal operation across all four areas indicates that the application rule was blocking part of Steam’s traffic.
Open Command Prompt as administrator and run these commands one at a time:
netsh winsock reset
netsh int ip reset
Restart Windows after both commands finish. This step may be needed when a VPN, security suite, network utility, or damaged socket catalog has altered Windows networking.
Verification:
After the restart, run “Test-NetConnection store.steampowered.com -Port 443” in PowerShell. The TcpTestSucceeded field should display True.
What worked for other readers
Steam Error Code 105 appears when the client cannot load a Steam web service and displays a message such as “Unable to connect to server” or “Server may be offline or you may not be connected to the internet.” The computer may still appear online because ordinary web browsing, game downloads, Friends, or an active game session can use different connections from the embedded Store and Community pages.
Quick Fix
- Exit Steam fully from the notification area and reopen it.
- Go to Steam > Settings > In Game > Delete Web Browser Data.
- Restart the router and compare the normal connection with a phone hotspot.
- Run
ipconfig /flushdnsin an administrator Command Prompt. - Temporarily disconnect VPN, proxy, filtering software, and network-level ad blocking.
- Test a public DNS resolver such as
8.8.8.8and8.8.4.4.
What Steam Error Code 105 Means
Steam Error Code 105, sometimes displayed as Error Code -105, is a web-service connection failure. It commonly appears when Steam cannot resolve a hostname through DNS, cannot establish an HTTPS connection, or cannot pass traffic through a proxy, VPN, firewall, router, content filter, or internet provider.
Find the Relevant Test
How Error Code 105 Usually Appears
The error is often limited to pages rendered inside the Steam client. A user may remain signed in and continue downloading or launching games while the Store displays a blank page, a connection warning, or an error page.
Store And Community Pages Fail
The Library works, but Store, Community, profiles, inventory, market, news, or workshop pages do not load. This pattern points toward Steam’s embedded web data, DNS, HTTPS filtering, or a blocked web process.
Steam Shows No Connection
Friends, downloads, account sign-in, and Store access all fail. This broader pattern is more consistent with a router problem, firewall rule, VPN conflict, internet-provider issue, or temporary Steam service interruption.
The Error Affects One Network
Steam works through a phone hotspot but fails through home Wi-Fi or Ethernet. The computer and Steam installation are probably functional. Focus on the router, DNS resolver, parental controls, filtered DNS, or internet provider.
The Error Affects One Computer
Other devices can reach Steam through the same router. Inspect the affected computer’s Steam browser data, Windows DNS cache, proxy settings, security software, hosts file, network adapter, and firewall permissions.
Why Steam Cannot Reach The Server
Valve’s network troubleshooting material lists routers, firewalls, background applications, wireless interference, internet providers, and network configuration among the areas that can interrupt Steam connectivity. Valve also recommends comparing wireless performance with a direct wired connection when possible. [✅Source-1]
DNS Resolution Failure
DNS converts a hostname such as store.steampowered.com into an IP address. Steam cannot start the web connection when the configured resolver times out, returns an invalid answer, blocks a Steam domain, or keeps an outdated record in cache.
This explains a common Error 105 pattern: websites that are already cached or use unrelated domains continue working, while selected Steam pages fail. The internet connection exists, but the required hostname is not resolving correctly.
Damaged Steam Web Browser Data
The modern Steam interface uses web-rendered content for several sections. Cached scripts, cookies, local storage, or other browser data can become stale after a client update, interrupted shutdown, sign-in change, or failed page load.
Deleting Steam web browser data is more relevant to Error 105 than clearing the download cache when the problem affects only Store or Community pages. The download cache primarily relates to game content delivery and updates.
VPN, Proxy, Or Filtered Traffic
A VPN or proxy changes the route between Steam and its destination. A failing VPN endpoint, unsupported proxy authentication, split-tunneling rule, DNS leak protection feature, or HTTPS inspection module can allow ordinary browsing while blocking the Steam client.
Network-wide ad blockers and filtered DNS services can create a similar symptom when a Steam content, authentication, image, or script hostname is placed on a blocklist. Temporarily disabling the filter is a diagnostic step, not a request to leave protection disabled.
Firewall Or Security Software Rules
A firewall can permit one Steam executable while denying another component used to render web pages. Rules may also become outdated after Steam updates an executable or changes its installation files.
Valve advises granting Steam executables permission for TCP and UDP traffic when prompted and restarting the computer after firewall changes. [✅Source-2]
Router Or Internet Provider Problems
A router can retain failed DNS sessions, exhausted connection states, incorrect filtering rules, or unstable wireless links. An internet provider can also experience a routing or DNS failure that affects selected services rather than the entire internet.
A phone-hotspot comparison separates these possibilities quickly. If the same computer and Steam installation work immediately on another network, reinstalling Steam is unlikely to address the actual cause.
Temporary Steam Service Interruption
The message itself allows for an unavailable server. A widespread service event is more likely when several devices and unrelated networks fail at the same time. Local repair steps cannot restore a remote service, so test the official Store and Support sites in a normal browser before changing advanced Windows settings.
Identify The Failing Layer Before Changing Settings
| Test Result | Most Likely Area | Next Action |
|---|---|---|
| Steam Store fails, but the Store opens in Chrome, Edge, or Firefox | Steam web data, application firewall rule, client-specific proxy, or Steam process | Delete Steam web browser data, exit Steam fully, and review firewall permissions |
| Steam Store fails in both Steam and every browser | DNS, router, provider routing, hosts file, or remote service | Run an DNS lookup, restart network hardware, and test a hotspot |
| Steam works through a hotspot | Home router, home DNS resolver, network filter, or internet provider | Change DNS, review router filtering, and contact the provider if needed |
| Other computers work on the same network | Local Windows or Steam configuration | Flush DNS, remove proxy settings, repair firewall rules, and reset Winsock |
| Store fails, but downloads and Friends work | Embedded web service path rather than the full Steam connection | Delete web browser data and inspect DNS or HTTPS filtering |
| Every Steam feature fails on several devices | Remote outage, router failure, or provider problem | Test another network and avoid reinstalling until the network state is known |
Test The Steam Hostname
Open Command Prompt and run:
nslookup store.steampowered.comA successful lookup normally returns one or more addresses. A timeout, server failed response, or message stating that the domain cannot be found points toward DNS. Repeat the test against the Community hostname:
nslookup steamcommunity.comIf both lookups fail while other domains resolve, check filtered DNS, parental controls, the hosts file, and the selected resolver.
Test HTTPS Port 443
Open PowerShell and run:
Test-NetConnection store.steampowered.com -Port 443TcpTestSucceeded : True means Windows established a TCP connection to the HTTPS port. A failed result does not identify the cause by itself, but it narrows the investigation to name resolution, routing, firewall rules, proxy behavior, or the remote endpoint.
Compare Wi-Fi, Ethernet, And A Hotspot
A network comparison is more useful than repeating the same repair on one connection. Test in this order:
- Current Wi-Fi or Ethernet connection.
- Ethernet instead of Wi-Fi, where available.
- A phone hotspot or another trusted internet connection.
Valve notes that wireless and powerline connections can experience intermittent failures caused by interference. A direct wired test helps distinguish local radio conditions from Steam or Windows faults.
Repair Steps In Practical Order
1. Exit Every Steam Process
Closing the main window may leave Steam running in the background. Right-click the Steam notification-area icon and select Exit. Open Task Manager and confirm that Steam and its related web processes have closed before relaunching the client.
A full process restart clears a frozen renderer, stalled network request, or temporary client state without changing account or network settings.
2. Delete Steam Web Browser Data
Use the current client path:
- Open Steam.
- Select Steam > Settings.
- Open In Game.
- Find Delete Web Browser Data.
- Select Delete.
- Exit Steam fully and reopen it.
This action may sign web pages out or remove locally stored page preferences. It does not uninstall games, remove the Library, or erase game saves.
Use the correct cache control: Steam’s Clear Download Cache command is documented under Settings > Downloads and targets download-related data. Use it when downloads or updates also fail, rather than treating it as the first repair for a Store-only Error 105. [✅Source-3]
3. Restart The Modem And Router Correctly
Disconnect power from both devices rather than pressing Wi-Fi buttons or restarting only the computer. Leave them unplugged for about 30 seconds, restore power to the modem first, and then restore the router when the modem reconnects.
A factory reset is not needed at this stage. It can erase the Wi-Fi name, password, provider credentials, port rules, and parental-control settings.
4. Flush DNS And Renew The Network Lease
Start with the least disruptive command:
ipconfig /flushdnsIf the connection also shows address or gateway problems, run the following commands in an administrator Command Prompt:
ipconfig /release
ipconfig /renew
ipconfig /flushdnsMicrosoft includes these commands among its Windows connection-repair steps. Releasing and renewing an address briefly disconnects the adapter, so avoid running them during an active download, call, or remote session. [✅Source-4]
5. Change The DNS Resolver
Changing DNS is useful when the hotspot test works, nslookup times out, or the provider’s resolver returns inconsistent results.
Windows Control Panel Method
- Open Control Panel > Network and Internet > Network and Sharing Center.
- Select Change adapter settings.
- Right-click the active adapter and select Properties.
- Open Internet Protocol Version 4 (TCP/IPv4).
- Select Use the following DNS server addresses.
- Enter
8.8.8.8and8.8.4.4. - Save the change and run
ipconfig /flushdns.
Google documents 8.8.8.8 and 8.8.4.4 as its IPv4 public DNS addresses. The same documentation lists 2001:4860:4860::8888 and 2001:4860:4860::8844 for IPv6. [✅Source-5]
Keep a record of the previous setting. Managed work, school, hotel, or filtered family networks may require their assigned DNS service.
6. Disable VPN And Proxy Connections For Testing
Disconnect the VPN from its application, then inspect Windows proxy settings:
- Open Settings > Network & internet > Proxy.
- Leave Automatically detect settings enabled unless it causes a known issue.
- Disable Use a proxy server when no administrator requires one.
- Exit and restart Steam.
Also inspect browser-security applications, antivirus web shields, family filters, DNS filtering clients, traffic monitors, and gaming route tools. Test one change at a time so the responsible component can be identified.
7. Repair Firewall Access Without Disabling Protection
Open Windows Security > Firewall & network protection > Allow an app through firewall. Confirm that Steam is allowed for the currently active profile.
When testing third-party security software, use its application-control page to allow the authentic Steam executable from the installed Steam directory. Do not download a replacement executable from another site.
Do not leave the firewall or antivirus disabled. A brief controlled test can identify interference, but the safer repair is to correct the application rule, update the security product, or remove a broken network-filter component.
8. Check Steam’s Required Network Ports
Most home routers allow outbound connections automatically, so manual port forwarding is rarely the first repair for Error 105. Restricted workplace, campus, hotel, or security-managed networks may block the traffic Steam expects.
| Purpose | Protocol And Remote Port |
|---|---|
| Web traffic | TCP 80 and TCP 443 |
| Steam client traffic | UDP 27015–27050 |
| Steam client traffic | TCP 27015–27050 |
The range from 27015 through 27050 contains 36 numbered ports. Valve lists this range together with TCP ports 80 and 443 in its Steam port reference. Games and optional Steam functions can require additional ports. [✅Source-6]
On a normal private network, prefer allowing the Steam application instead of creating broad unsolicited inbound rules. Ask the network administrator before changing a managed router or institutional firewall.
9. Inspect The Windows Hosts File
The hosts file can override DNS and force a domain to the wrong address. Open Notepad as administrator, then open:
C:\Windows\System32\drivers\etc\hostsLook for lines containing steampowered.com, steamcommunity.com, steamstatic.com, or other Steam-related domains. Remove only entries that were added by a filter, old troubleshooting attempt, or unwanted network utility.
Do not delete the entire file or remove organization-managed entries. Save a backup before editing it, then run ipconfig /flushdns.
10. Reset Winsock And TCP IP
Use this repair after ordinary DNS, router, browser-data, proxy, and firewall checks fail:
netsh winsock reset
netsh int ip resetRestart Windows. Winsock reset rebuilds the Windows socket catalog, while the TCP/IP reset restores networking parameters. VPN clients, security filters, virtual adapters, static addressing, or specialized network software may need reconfiguration afterward.
11. Use Windows Network Reset Only As A Later Step
Windows Network Reset removes and reinstalls network adapters and returns many network components to their default state. On Windows 11, open Settings > Network & internet > Advanced network settings > Network reset.
This can remove saved adapter configuration, virtual switches, VPN adapters, and custom network settings. Record anything important first. Microsoft places Network Reset among the later Wi-Fi repair options rather than the opening step. [✅Source-7]
Advanced Checks When Error 105 Remains
Check Whether Steam Web Processes Are Being Blocked
Open Task Manager while Steam is running and inspect its related processes. If security software repeatedly terminates, quarantines, or blocks a Steam web-rendering component, repair the security rule rather than repeatedly reopening Steam.
Review Windows Security under Virus & threat protection > Protection history. Restore a file only when its location, publisher, and relation to the installed Steam client have been verified.
Test A Clean Windows Startup
A clean startup can identify a background conflict involving VPN software, network optimizers, traffic filters, overlay programs, parental-control tools, or third-party security suites.
Disable non-Microsoft startup services temporarily, restart Windows, and test Steam. Re-enable items in small groups until the error returns. Keep essential hardware, authentication, accessibility, and security services enabled unless their vendor provides different instructions.
Check Adapter And Router Time Settings
An incorrect system date, time, or time zone can break secure HTTPS validation. Enable automatic time under Settings > Time & language > Date & time, synchronize the clock, and restart Steam.
Also verify that the router’s date and time are correct when it performs HTTPS inspection, access scheduling, certificate validation, or parental filtering.
Compare IPv4 And IPv6 Behavior
A network may advertise IPv6 while providing an incomplete route or failing DNS service. Run both commands:
ping -4 store.steampowered.com
ping -6 store.steampowered.comSome Steam hosts may decline ping requests, so packet loss alone does not prove that the service is unavailable. The useful result is whether each command resolves the hostname to the expected address family.
Do not permanently disable IPv6 as an opening repair. Test it only when the network clearly shows broken IPv6 resolution or routing, then repair the router or provider configuration.
Collect A Network Report For Steam Support
Record the exact error text, date and time, affected Steam pages, connection type, hotspot result, DNS lookup output, and whether port 443 succeeds. Avoid publishing account credentials, authentication cookies, private IP configuration, or identifying log content.
Steam provides a network diagnostic process and explains what information can help when reporting connection problems. [✅Source-8]
Steam Error 105 On macOS And Linux
macOS DNS Cache Repair
Quit Steam, open Terminal, and run:
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponderEnter the administrator password when prompted, restart Steam, and test the Store. Also inspect System Settings > Network > VPN & Filters for content filters, VPN profiles, or security extensions that may intercept Steam traffic.
Linux DNS And Packaging Checks
On Linux systems using systemd-resolved, close Steam and run:
sudo resolvectl flush-cachesThen test resolution:
resolvectl query store.steampowered.comIf Steam was installed through Flatpak, compare it with the distribution package or Valve’s supported installer when permitted by the operating system. A sandbox networking fault can affect Steam’s web pages even when the host browser works.
Also inspect firewall rules, DNS services, VPN interfaces, custom /etc/hosts entries, and the resolver configuration shown in /etc/resolv.conf. Do not replace resolver files blindly because many Linux distributions generate them automatically.
Repairs That Commonly Waste Time
- Reinstalling games: Error 105 concerns access to Steam web or network services, not an individual game’s content files.
- Deleting the Steam library: Installed game data does not repair DNS, proxy, router, or firewall failures.
- Factory-resetting the router immediately: A power cycle and hotspot test provide safer diagnostic information first.
- Disabling all security protection permanently: Correct the blocked application or filtering rule instead.
- Opening every router port: Normal outbound access usually does not require broad inbound port forwarding.
- Running random registry files: DNS and connection repairs do not require an unverified registry download.
- Changing several settings at once: One change followed by one test makes the cause easier to identify.
Reducing Repeat Connection Failures
Keep Steam, Windows, network-adapter drivers, router firmware, VPN software, and security tools updated. Old network filter drivers can remain active even after their main application appears closed.
Use one DNS filtering layer rather than stacking a browser filter, Windows DNS client, VPN filter, router blocklist, and provider-level family service. Multiple layers make a failed lookup harder to trace.
Keep a record of custom DNS addresses, static IP settings, proxy details, VPN adapters, and router rules. This allows a controlled rollback after Windows Network Reset or router maintenance.
When Error 105 returns, begin with three comparisons: Steam versus a normal browser, home internet versus a hotspot, and the affected computer versus another device. Those tests usually reveal whether the fault belongs to Steam’s local web data, the computer, the network, or a remote service.
Common Questions About Steam Error Code 105
Is Steam Error Code 105 A Server Outage?
It can be, but the message does not prove that Steam is offline. If Steam fails on several devices and separate internet connections at the same time, a remote service problem becomes more likely. If a phone hotspot fixes the error, the normal network is the stronger suspect.
Why Does Steam Show Error 105 When My Internet Works?
An active internet connection does not guarantee that every hostname or port is reachable. DNS may fail only for Steam domains, a firewall may block the Steam application, or a VPN may route Steam differently from the browser.
Does Error Code 105 Mean My Steam Account Is Banned?
No. Error 105 is a connection or page-loading failure. Account restrictions, incorrect passwords, Steam Guard requests, and access limitations normally produce different messages.
Will Deleting Steam Web Browser Data Remove My Games?
No. It removes cached web content, cookies, and local page data used by Steam’s web-rendered sections. Installed games and their local files remain in the Library folders.
Should I Clear The Steam Download Cache?
Clear it when downloads, installations, or updates are also failing. For a Store-only or Community-only Error 105, deleting web browser data, testing DNS, and checking filters are more directly related to the symptom.
Which DNS Addresses Can I Test?
Google Public DNS uses 8.8.8.8 and 8.8.4.4 for IPv4. Record the current configuration before changing it, especially on work, school, hotel, or managed family networks.
Why Does Steam Work On A Phone Hotspot?
The hotspot gives Steam a different router, DNS resolver, public route, and internet provider. Success through that connection indicates that the Steam installation can communicate and that the normal network path needs inspection.
Should I Reinstall Steam To Fix Error 105?
Reinstallation belongs near the end of the process. It cannot repair a failing DNS resolver, blocked router, internet-provider route, or external VPN filter. Back up the Steam library configuration before uninstalling if every network and Windows repair has already failed.
Can An Ad Blocker Cause Steam Error 105?
A network-level blocker can cause it when it blocks a domain required by the Steam page. Browser-only extensions usually do not control the Steam client, but DNS filters, router blocklists, antivirus web shields, and system-wide filtering applications can.
What Should I Send To Steam Support?
Include the full error message, affected pages, time of failure, operating system, connection type, hotspot result, DNS lookup result, and whether HTTPS port 443 succeeds. Remove passwords, cookies, account recovery data, and other private information from diagnostic files.