Web site 503 (503 Service temporarily unavailablethe requested) service temporarily unavailable solution summary _win server

503 is an HTTP status code, is a return state of the server error, due to temporary server maintenance or overload, the server is currently unable to process the request. This condition is temporary and will be restored after a period of time. So what should we do when we encounter 503 services that are temporarily unavailable?

If you are a webmaster

First, check to see if you have closed the application pool. Each Web site corresponds to an application pool (IIS server is so), of course they may be the same application pool, can also be different, to see if the 503 error site corresponding to the program pool open.

If you do not close the application pool, it is necessary to see if the application pool queue is full when the request arrives. Each site has its maximum load, and when the access request reaches this value, there will be a 503 error, the solution can increase the request queue, the default value is 1000.

It is also possible that the application pool identity does not use a predefined account: A network service that has its own identity configured, but the configured user does not belong to the IIS_WPG group, in which case the application pool path of the Web site can be changed and changed to an application pool belonging to the IIS_WPG group.

CPU usage is too high, and the application pool has CPU monitoring enabled, the CPU utilization is set to close the application pool, and the service-side page (. asp,.aspx) written by the developer is inefficient, causing the CPU to occupy for a long time, eventually reaching the set percentage, Which causes the application pool to shut down. You can restart the application pool when you encounter this situation.
If you are a visitor

First try to refresh, access again, if the site is not closed, most likely because the site has been overloaded, this state may disappear immediately, so more than a few times may be able to visit the refresh.

If the refresh does not solve the problem, try to clear the cache, restart the browser, or switch directly to a different kernel browser, some of which may not be compatible with some browsers. (Some people on the internet said that this can be solved, small series on the list, the correctness of its evaluation)

Contact Webmaster, if the above methods can not be resolved, you want to visit the site, you can contact the site administrator to ask him to solve the problem, because this situation is likely to be the site administrator is the site maintenance caused, at this time you only wait for maintenance after the visit.

Click here to enter the method or step

Attention matters

Increase the request queue must pay attention to your server load, so as not to aggravate the server burden caused serious consequences.

When an application pool consumes a large amount of CPU, it is essential to check that the executable in the Web site (php,asp, etc.) is inefficient, which is the fundamental way to solve the problem.

If the site administrator to shut down the application pool to facilitate maintenance, you can only wait to open after maintenance.

The use of Alexa rankings can be queried to the webmaster's mailbox, convenient contact webmaster inquiries.