Jump to content

Can't connect to the internet due to a 503 error in the proxy, hel


Breener
 Share

Recommended Posts

Hey, I can't connect to the internet on Steam, Chrome and I even tried Internet Explorer in case and can't connect with that either. When I clicked on the "More information" button on Chrome, it said:

"Error 102 (net::ERR_CONNECTION_REFUSED): Unknown error."

Then, when I go to Steam, it says that it's a 503 Proxy Error. The strangest thing? It's only on 1 profile on my laptop (mine, not my brother's) and nothing else is affected.

Any help is appreciated, thanks!

Link to comment
Share on other sites

102 is normally an information code: 102 Processing (WebDAV) (RFC 2518)

As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet.[3] This prevents the client from timing out and assuming the request was lost.

From http://en.wikipedia.org/wiki/List_of_HTTP_status_codes

503 Error: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a

server must use it when becoming overloaded. Some servers may wish

to simply refuse the connection.

From http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Link to comment
Share on other sites

102 is normally an information code: 102 Processing (WebDAV) (RFC 2518)

As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet.[3] This prevents the client from timing out and assuming the request was lost.

From http://en.wikipedia.org/wiki/List_of_HTTP_status_codes

503 Error: The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a

server must use it when becoming overloaded. Some servers may wish

to simply refuse the connection.

From http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

I'm sorry, but that didn't really help my problem :/ I'd just like to know why this happened and if I can fix it.

Thanks.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy