All users, going over the boundless expanses of the global network, encountered errors in the work of sites. For us, they are presented in the form of error pages, which indicate the code of the problem.
Site errors are a frequent occurrence.They can occur both on the side of users and on the server. Each problem has its own special code, where you can find out the reason and ways to fix the error. The most common site malfunctions are the following codes: 404, 522, 503, 400.
Error 522 does not carry a serious problem, it is quite easy to fix. The essence of the problem is that the server can not respond to the client's request, thus causing a connection failure.
The client has a limited amount of time forTo wait for a response from the server to your request. The problem happens on the client side when the data transfer rate is low and the ping level (delay) is high.
Error 522 has several causes:
Because of too strong an influx of customqueries the server, which is not designed to process large amounts of data, is out of order. This is not a critical issue in the site, but it takes a little time for administrators to return the functionality to the server and filter out the user's thread. Frequently with similar problems users of the site "Fikbuk" are faced. Error 522 in this case occurs when many users try to open the same page.
Users can also request a negativecharacter. Often an abnormal amount of actions in relation to the server indicates an attack by intruders. In this case, the site can suffer serious losses, because there is a lot of time to restore after the attack, and all the actions are quite laborious and costly. Several times this scenario was also encountered on the entire well-known site called "Fichebuk". Error 522 occurred to users for several days. Then the administration acknowledged that the site was subject to hacker attack. Soon the problem was eliminated, and now the resource is working stably, failures sometimes happen, but the workability is quickly restored by the developers.
In order to fix the problem on the server side, you should limit the number of requests and the speed that is used to process them.
From the user's side, a number of actions should be taken: