What does a server error mean? How to cope with the situation for an ordinary user

One of the most common problems in the operation of Internet resources is error 500. In accordance with accepted specifications, it is generated by the server when there is some problem in the system. It can be caused by the site itself or the hosting. You need to start looking for it on the service. Once it has finally become clear that the error is generated by the site itself, you need to understand it. Most often, its appearance is caused by incorrect information inside the .htaccess component, which contains important parameters environment. Here you need to study its contents in detail and try to find out the reason for the appearance of such a message as “Error 500”.

Identifying the cause

Each time such a message appears, it is added Additional Information about the error. Depending on the provider, it is recorded in the Error file with the .log extension or in the corresponding hosting section. Opening specified file or by going to this section, you can find out why the HTTP 500 error appears on the monitor screen when a visitor tries to access your resource on the World Wide Web ( Internal Server Error). It needs to be eliminated as quickly as possible, since it leads to downtime of your page and, as a result, you lose visitors and profit.

Server

A fairly wide range of problems can cause this message to appear. Among them are:

In the first case, you either need to change the tariff plan to one with more memory, or disable the script itself if it is possible to work without it. It is also worth downloading the site to your local PC and checking it with an antivirus. Maybe this is due to his malicious activities. In the second case, the solution is similar. You may need to reinstall a broken component. Before installing any module on the site, you need to make sure that it is compatible with previously installed ones. This is best done at the development stage. Well, in the latter case, the rights to access folders and files are set incorrectly. For the former, they should be 755, and for the latter, this parameter should be either 644 or 444. If all this is done, and error 500 still appears when trying to access the page, then go to next steps, which are associated with the resource itself.

The site itself

The most common reason for this message to appear is incorrect parameters inside .htaccess. It is not allowed to have parameters such as

php_value, php_admin_flag or php_flag. All of them must be turned into comments using the “#” icon, which is placed in front of them. Next, you need to find a directive such as Options +FollowSymLinks and replace it with the following: Options +SymLinksIfOwnerMatch. You can also remove the +ExecCGI parameter and then check that there is no message such as “Error 500”. Internal Server Error should not appear either. If this does not help, then you can delete MultiViews in the same file. After this, you need to try to access the page again and check the functionality of the resource.

Summary

If after the manipulations the result is still the same, error 500 continues to appear, then it makes sense to contact the provider’s support service for help. With their help this issue must be resolved.

Most Internet users are familiar with errors that sometimes arise when working with a website or searching for certain information in search engines. If you are the owner of a website that suddenly started producing such errors, it is important for you to understand what they mean, the reason for their occurrence and how to eliminate them.

Often on various forums on the Internet you can see discussions on the topic of eliminating errors on the site. Sometimes the problems that arise are minor and can be solved by the user independently, without turning to specialists.

In order to know what to do in an unexpected situation, it is worth reading the description of the most common errors, as well as reading the guide to eliminating them.

Types of errors

HTTP protocol errors occur when the web server, for some reason, cannot successfully send the requested document to the user. In this case, the server will inform the user in the HTTP header of the error code that occurred.

Error codes can be positive or negative or successful or unsuccessful.

There are 4 types of codes (xx is a combination of any numbers):

• 2xx - request completed successfully;
• 3xx - the request was successfully redirected (also a positive code);
• 4xx - error - the document was not sent to the user because a critical error occurred. The 4xx code class is intended to indicate errors on the client side;
• 5xx - server error - critical error on the server. Codes 5xx are allocated for cases of unsuccessful operation due to the fault of the server.

Of greatest interest to the site owner are codes indicating errors on the client or server side. The causes and methods for eliminating these errors are presented below.

Error 400

Bad Request

When you go to a website, your browser may display a “400 Bad Request.” This means that the server has detected syntax error in the query entered by the user. However, such an error can appear not only when you enter the site address, but also, for example, when logging into the control panel of your site. There may be several reasons for this:

• blocking the browser by antivirus;
• blocking Windows firewall by browser;
• a large number of cookies and data in cache;
• Internet interruptions.

In order to determine which of the listed options applies to your situation, you must test each of them until the problem is completely resolved. Let's start with the first possible reason.

Browser blocking

• Review your antivirus settings in the section called “Application Rules” or something similar.
• Check if your browser is on the list and what level of trust it has.
• Increase your browser's trust level if it is low.
• Save the new settings and try logging into the control panel again.

If the error persists, proceed to checking the next cause.

Windows Firewall Blocking

• Try disabling the firewall temporarily: Start menu - Control Panel - System and Security - Windows Firewall - Turn it on or off.
• Clear cache and cookies.
• Please refresh the error pages.
• If the problem is resolved, then to finish, add allowed programs to the firewall: Start - Control Panel - System and Security - Firewall - Allow programs to run through the firewall.

If the problem persists, continue checking.

Cache and cookies

• Delete cookies and clear cache: press Shift + Ctrl + Delete while the browser is open.
• Remove unnecessary files.
• Check your browser functionality.

Internet interruptions

• Contact your internet provider and see if they have any work going on.
• Find out how long the work will take.

Error 403

Forbidden

Error 403 means that the server cannot fulfill the request because access to the requested files or pages is denied. This error can occur for a number of reasons. Let's look at the most common ones:

• The index file index.html is not loaded in the public_html directory of your site or is incorrect. To resolve this error, create a file called index.html or rename an existing file. Possible options for the file name are index.html, index.htm, or index.php.
• The directory in which the requested file is located has such permissions that the Apache web server could not read the file on the server disk. To resolve this error, try changing the access rights in the section responsible for setting rights.
• The site files were uploaded to the wrong directory. To resolve this error, check whether the site files are located in the site/public_html directory, where site is the name of your site.

Error 404

Not Found

Error 404 means that the server cannot find the data requested by the user.
Reasons for this error:

• Invalid URL entered into the browser address field. To resolve this error, check whether the link is specified correctly.
• The file requested by URL is not present on the server. To resolve this error, you need to check the presence of the requested file in the public_html directory of your site.

Error 500

Internal Server Error

Error 500 means that the server has Internal error. This problem can occur for two reasons:

• The script cannot be run. Most likely, the access rights for folders and files are incorrect. If PHP script files hosted on your hosting have access rights of 777, then the execution of these scripts may be blocked by the server. This happens because permissions 777 allow anyone to make any changes to this file, which significantly affects the security and integrity of your site. To resolve this error, you should check the access rights to the site folders and files. It is recommended to set access rights to 755 for folders, 600 for executable scripts, and 644 for all other files.
• Incorrect instructions in the .htaccess file or the presence of unsupported directives in it. You may have misspelled the name of the required directive or its parameters. This error can be resolved by enabling the error log error.log. The web server will tell you which specific directive it considered erroneous - it will need to be corrected.

Error 502

Bad Gateway

This error- the result of a request that resulted in an invalid response from the server. There may be several reasons for the problem:

• Problems with the proxy server. To resolve this error, try typing in address bar browser link to some other site. This way you can check whether there is Internet access at all. If you find that you have Internet access, but your access to a specific site still gives a 502 error, try deleting cookies in the browser.
• Insufficient server resources. This may mean that the load on the server exceeds the resources available on the selected hosting plan. Check with your hosting provider for information about plans with more resources and, if necessary, increase the RAM or available disk space.

Error 503

Service Temporarily Unavailable

Each account on the hosting server has a certain number of work processes allocated in accordance with the selected tariff plan. Requests are processed on a first-come, first-served basis; they arrive at the server, where light requests are processed instantly, while heavy requests are processed slowly. Every queue is limited by a certain number of requests. If a new request is outside this boundary, it will not be accepted, and instead of the result, the browser will display the “Service is temporarily unavailable” notification.

To fix this error you need to know the reasons why it may appear:

1. Scripts freeze when transferring large static files via PHP. Scripts run for a certain period of time, not all the time. When the script runs out of time, the file transfer is interrupted; accordingly, the file will not be transferred completely, and the request will leave the web server process still running long time. You can resolve the error using the following steps:

• Check all the components and plugins of your CMS, disabling them one by one, and find the heaviest or damaged ones, which slow down the loading of the site. If possible, discard such components or look for a faster analogue.
• Check for slow queries - a mysql-slow.log file is created in the logs folder of your account. The information in this file is updated once a day and contains only the most problematic SQL queries.
• If PHP scripts use Include functions that load parts of the engine located on the same account, make sure that they use a local path and not a URL like “http://...”. The presence of a URL forces the server to make an additional HTTP request - this takes extra time and greatly slows down the loading of the site.

2. A large number of requests to the server. There are several reasons for such requests:

• The downloaded resource is split/contains links to too many files (pictures, style sheets, JS scripts), which are loaded through separate requests. In this case, you should combine the resources into a single file where possible.
• DDoS attacks, floods, and comment spams can also cause a large number of requests. In the event of a DDoS attack, it is necessary to determine its type and, according to its level, take corrective action. You can read more about DDoS attacks in the article "

Sometimes in Google Play Market there is some kind of glitch due to which the user cannot log into his account, download the application or update it. What is the cause of the server error, and how to fix it; how to prevent? Let's try to understand the main problems and find their solution!

Why there may be a problem with the Play Market

Google Play Market is a voluminous application that integrates almost all programs installed on an Android device. The main function of the Market is the timely updating of these programs. Thus, the user does not need to waste time visiting developer sites to get the “latest” version of their product. You just need to set up automatic updates.

Google Play Market application

Of course, this level of integration requires an account to store data about installed applications. Since the Play Market belongs to Google, the account is linked to it, and accordingly, Google. And if any problems arise with it, then they are transferred to the “Market”, and therefore to the installed applications. Conversely, malfunctions in the Market can lead to errors in the entire account. However, don't panic right away. Perhaps in your case everything can be solved “in two clicks”.

What could be the reasons for Google Play Market not working properly? Below is a list of the most common ones.

Operating system error;

Large amount of residual data, cache;

Error Play settings Market;

Disabling the "Download Manager";

Google account error;

Incompatible applications;

Incorrect date and time on the device.

This list lists problems in order of decreasing likelihood of occurrence. Before we jump straight into solutions, let's look at what types of errors may appear.

Types of errors

Play Market server error

There may be several Play Market errors. Although each is technically different in nature, the reasons are usually similar for all. This article is intended to help solve only those errors that are listed below.

Error code 491/481. Applications are not downloaded and/or updated.

919. The program is downloaded, but it cannot be launched.

403/413/504. Applications are not installed or updated.

923. Your Google account is not syncing or your cache is full.

921/. Applications are not downloaded.

492. Cache problem.

911/919. Applications are not downloaded.

//. Receiving information from the server is impossible.

Invalid batch file. There is a file or cache problem.

The occurrence of any of the presented errors is the result of failures of the Google account or the entire system. Some of them may appear when installing applications, others when updating them. Whenever they arise, a set of actions must be carried out to solve them. Cannot be selected specific way solutions to this or that error, since they all manifest themselves in different cases and for various reasons.

So, if you receive a message about any of the presented errors, check out the solutions to solve them.

How to fix server errors in the Play Store

As already indicated, the root cause of a particular error is difficult, almost impossible, to identify. Therefore, to solve any problem you need to take several mutually exclusive steps. They are presented below in order of execution.

Checking some parameters

Before you begin the following steps, make sure that:

The date and time on the device are correct;

There is an Internet connection;

Google accounts included.

Despite the ridiculous banality, it is often the restoration of these simple factors that helps restore normal work Play Market. If everything is in order here, go to “Step 1”.

As simple as it may sound, sometimes a simple reboot really helps. The fact is that when you turn off the device, part of the cache is automatically deleted. So, by rebooting your phone or tablet, you can get rid of erroneous files or data.

To reboot, hold down the device unlock key. In the window that appears, select “Restart”. If you don’t have it, click “Turn off power”, and then turn on the device manually by holding down the same key.

Reboot your device

Reset settings and clear cache files

Go to the “Settings” of the device;

Find the “Program Manager” or “Applications” menu item;

In the list that appears, find Google Play Market;

Open it and press the “Erase data” and “Clear cache” buttons in turn.

Erase residual data and clear the cache

In most cases, these actions are quite sufficient. If they didn't help, move on to the next step.

Uninstalling all Play Market updates

Play Market updates can sometimes bring disruption to the system, especially if you have relatively new model devices. Removing them can help deal with the problem of errors. However, please note that in this case, the settings of the Play Market itself will be reset to their original settings.

To remove updates, go to settings Google apps Play Market, as we did in “Step 2”. Now click the “Uninstall updates” button.

Uninstalling Play Market updates

Clearing data from Google Play Services

This application is responsible for the correct operation of the main functions of the Play Market, such as updating or installing programs. Sometimes clearing the cache and contents of “Services...” helps to fix the mentioned errors. To carry out “Step 4”, find “ Google Services Play" in the list of programs installed on the device (as we did with the Play Market). Then click “Erase data” and “Clear cache” in sequence.

Cleaning up Google Play Services

Activating the Download Manager program

The Download Manager application is responsible for the device’s hardware ability to download programs from the network and install them. Sometimes the “Manager...” functions may be disabled. To enable them, do the following:

Find the Download Manager app among installed programs(as in steps 2 and 4).

Go into it and click on the “Enable” button.

Reboot your device (see “Step 1”).

If the “Download Manager” was indeed disabled, you must enable it, even if this did not help fix the errors. Otherwise, you will not be able to download programs at all.

Enable the “Download Manager” functions

Deleting your entire Google account

Often errors occur due to problems synchronizing your Google account with the Play Market. To fix this problem, you will have to delete your account.

Deleting your account without first synchronizing will result in the loss of personal data. To avoid this, you must use the data backup function.

Backup is carried out as follows. Go to the “Settings” of the device and find the “Accounts” item. Then select your Google account by clicking on it.

Find "Accounts" in "Settings"

Click on the name of your mailbox to enter the synchronization (backup) menu.

Click on your Google account name

In the menu that opens, you will see several items and sliders next to them. When the slider is on, it means that backup the corresponding data will be executed. We recommend leaving all sliders turned on. Now press the hard Options key on your phone or tablet (usually the touch button to the left of the Home button). In the window that appears, click “Synchronize”.

Click "Sync"

After synchronization is complete, you can delete your Google account with peace of mind. The delete button, as you probably noticed, is located in the same place as the “Synchronize” button.

Reboot your device and sign in to your Google account again (just go to Play Market or Gmail). The device will prompt you to restore your account data from the Google server. Now all applications from the Play Market installed on your device are normalized and synchronized. But if this step did not help you, move on.

Removing incompatible programs

If you have previously installed any programs not from the Play Market, there is a high probability that they are harming your account. It is especially worth highlighting applications for working with the functions of the Market itself. For example, those used for free receipt paid bonuses from games.

Job malicious applications breaks data synchronization across the entire device and can lead to serious problems. Often such programs are equated to viruses. Therefore, they must be removed immediately. If you did not install them yourself, we recommend using an antivirus, for example, “Dr. Web". Install it and scan and then clean the device.

Install antivirus "Dr. Web"

Reset Android OS settings

This step is, of course, quite radical. Resetting the OS settings will result in loss of application data and will also restore the phone (tablet) to factory settings. However, quite often this method allows you to get rid of all potential problems. Perhaps even from those you didn’t even know existed. You can also do a factory reset if you don't want to go through the steps above.

Eliminating errors through software intervention

This method can be very effective, however, it requires minimal knowledge of the Android OS, as well as some IT skills.

We do not recommend that you attempt the following unless you are confident in your abilities. Responsibility for implementing the proposed actions will remain with you, because, as a result, the device may completely break down.

So, first, download a file manager for Android devices. A good example in in this case is "Root Explorer". After downloading, follow these steps:

Open the Root Explorer program.

Go to: /data/data/com.android.vending/.

Delete all data from the specified folder.

Without closing the program, go to “Options” -> “Permissions” and check the boxes exactly as shown in the screenshot.

Using "Root Explorer"

Now you just need to restart your device and try to go to the Play Market.

Correct Google work Play Market essentially means normal work the entire operating system. Therefore, even if you do not need to download or install applications from the Market in the near future, but any of specified errors occurs, it needs to be corrected urgently. This will help nip potential problems in the bud, and therefore save both your personal data and the device itself.

HTTP status code(English) HTTP status code) - part of the first line of the server response for requests via the HTTP protocol. It represents an integer of three decimal digits. The first digit indicates condition class . The response code is usually followed by an explanatory phrase in English separated by a space, which explains to the person the reason for this particular response. Examples:

• 201 Created.
• 401 Unauthorized.
• 507 Insufficient Storage.

The client learns from the response code about the results of its request and determines what actions to take next. The set of status codes is a standard and they are described in the corresponding RFCs. New codes should only be introduced after agreement with the IETF. However, there are two codes known to be used that are not mentioned in the RFC: 449 Retry With. Also mentioned is the explanatory phrase “Reply With” in the specification for WebDAV V Microsoft Developer Network, introduced Microsoft and 509 Bandwidth Limit Exceeded, introduced in cPanel.

The client may not know all status codes, but it must respond according to the class of the code. There are currently five classes of status codes.

Web server Internet Information Services In its log files, in addition to standard status codes, it uses subcodes, writing them with a dot after the main one. At the same time, this subcode is not placed in responses from the server - the server administrator needs it so that he can more accurately determine the sources of problems.

Review list

Below is an overview list of all response codes described in this article:

Diagram of web server decision making based on headers
Statistics on response codes generated by the log analyzer Webalizer

• 1xx: Informational:
  • 100 Continue (“continue”);
  • 101 Switching Protocols;
  • 102 Processing (“processing in progress”).
• 2xx: Success (successfully):
  • 200 OK (“good”);
  • 201 Created (“created”);
  • 202 Accepted (“accepted”);
  • 203 Non-Authoritative Information (“information is not authoritative”);
  • 204 No Content;
  • 205 Reset Content;
  • 206 Partial Content;
  • 207 Multi-Status;
  • 226 IM Used
• 3xx: Redirection:
  • 300 Multiple Choices;
  • 301 Moved Permanently;
  • 302 Moved Temporarily;
  • 302 Found (“found”);
  • 303 See Other (“see other”);
  • 304 Not Modified (“not changed”);
  • 305 Use Proxy (“use proxy”);
  • 306 - reserved(code used only in early specifications);
  • 307 Temporary Redirect
• 4xx: Client Error:
  • 400 Bad Request (“bad, incorrect request”);
  • 401 Unauthorized (“not authorized”);
  • 402 Payment Required;
  • 403 Forbidden;
  • 404 Not Found (“not found”);
  • 405 Method Not Allowed;
  • 406 Not Acceptable;
  • 407 Proxy Authentication Required (“proxy authentication required”);
  • 408 Request Timeout (“timed out”);
  • 409 Conflict;
  • 410 Gone (“deleted”);
  • 411 Length Required;
  • 412 Precondition Failed (“condition is false”);
  • 413 Payload Too Large
  • 414 URI Too Long (“URI is too long”);
  • 415 Unsupported Media Type
  • 416 Range Not Satisfiable
  • 417 Expectation Failed
  • 418 I’m a teapot (“I am a teapot”)
  • 422 Unprocessable Entity
  • 423 Locked;
  • 424 Failed Dependency;
  • 425 Unordered Collection;
  • 426 Upgrade Required;
  • 428 Precondition Required;
  • 429 Too Many Requests;
  • 431 Request Header Fields Too Large
  • 444 Closes the connection without sending a response header. Non-standard code;
  • 449 Retry With;
  • 451 Unavailable For Legal Reasons
• 5xx: Server Error:
  • 500 Internal Server Error;
  • 501 Not Implemented;
  • 502 Bad Gateway (“bad, erroneous gateway”);
  • 503 Service Unavailable (“service unavailable”);
  • 504 Gateway Timeout(“gateway is not responding”);
  • 505 HTTP Version Not Supported (“HTTP version is not supported”);
  • 506 Variant Also Negotiates (“variant also negotiates”);
  • 507 Insufficient Storage (“storage overflow”);
  • 508 Loop Detected (“infinite redirection detected”);
  • 509 Bandwidth Limit Exceeded (“channel bandwidth has been exhausted”);
  • 510 Not Extended (“not extended”);
  • 511 Network Authentication Required
  • 520 Unknown Error
  • 521 Web Server Is Down (“the web server is not working”);
  • 522 Connection Timed Out("connection not responding");
  • 523 Origin Is Unavailable;
  • 524 A Timeout Occurred (“revival time has expired”);
  • 525 SSL Handshake Failed
  • 526 Invalid SSL Certificate

Description of codes

Information

This class contains codes that inform about the transfer process. When working through protocol version 1.0, messages with such codes should be ignored. In version 1.1, the client must be prepared to accept this class of messages as a normal response, but the server does not have to send anything. The messages themselves from the server contain only the start line of the response and, if required, a few response-specific header fields. Proxy servers must send such messages further from the server to the client.

• 100 Continue - the server is satisfied with the initial information about the request, the client can continue sending headers. Introduced in HTTP/1.1.
• 101 Switching Protocols - the server offers to switch to a protocol more suitable for the specified resource; The server must indicate the list of proposed protocols in the Upgrade header field. If the client is interested in this, then he sends a new request indicating a different protocol. Introduced in HTTP/1.1.
• 102 Processing - the request has been accepted, but it will take a long time to process. Used by the server to prevent the client from dropping the connection due to a timeout. Upon receiving such a response, the client must reset the timer and wait for the next command in normal mode. Appeared in WebDAV.

Success

Messages of this class inform about cases of successful acceptance and processing of a client request. Depending on the status, the server may also transmit the headers and body of the message.

• 200 OK - successful request. If the client requested any data, it is found in the header and/or body of the message. Introduced in HTTP/1.0.
• 201 Created - as a result successful implementation request, a new resource was created. The server can specify the addresses (there may be several) of the created resource in the body of the response, with the preferred address indicated in the Location header. The server is recommended to indicate in the response body the characteristics of the created resource and its address; the format of the response body is determined by the Content-Type header. When processing a request, a new resource must be created before sending a response to the client, otherwise a response with code 202 should be used. Introduced in HTTP/1.0.
• 202 Accepted - the request was accepted for processing, but it was not completed. The client does not have to wait for the final transmission of the message, as a very long process can begin. Introduced in HTTP/1.0.
• 203 Non-Authoritative Information - similar to answer 200, but in this case transmitted information was not taken from the primary source (backup, another server, etc.) and therefore may not be current. Introduced in HTTP/1.1.
• 204 No Content - the server successfully processed the request, but the response contained only headers without the message body. The client does not have to update the content of the document, but can apply the received metadata to it. Introduced in HTTP/1.0.
• 205 Reset Content - the server obliges the client to reset the user-entered data. The server does not transmit the body of the message and it is not necessary to update the document. Introduced in HTTP/1.1.
• 206 Partial Content - the server successfully completed a partial GET request, returning only part of the message. In the Content-Range header, the server specifies the byte ranges of the content. When working with such responses, special attention should be paid to caching. Introduced in HTTP/1.1. ( more details...)
• 207 Multi-Status - the server transmits the results of several independent operations at once. They are placed in the message body itself as an XML document with a multistatus object. It is not recommended to place statuses from the 1xx series in this object due to meaninglessness and redundancy. Appeared in WebDAV.
• 226 IM Used - the A-IM header from the client was successfully received and the server returns the content taking into account the specified parameters. Introduced in RFC 3229 to extend the HTTP protocol with delta encoding support.

Redirection

Codes in this class tell the client that in order for the operation to succeed, another request must be made, usually to a different URI. Of this class, five codes 301, 302, 303, 305 and 307 relate directly to redirects. The address to which the client should make the request is indicated by the server in the Location header. However, it is possible to use fragments in the target URI.

According to the latest standards, a client can redirect without a user request only if the second resource is requested using the GET or HEAD method. Previous specifications stated that to avoid round trips, the user should be asked after the 5th consecutive redirect. For all redirects, if the request method was not HEAD, then a short hypertext message with the target address should be included in the response body so that in case of an error the user can make the transition himself.

HTTP developers note that many clients mistakenly use 301 and 302 redirects. GET method to the second resource, despite the fact that the request to the first was with a different method (most often PUT). To avoid misunderstandings, codes 303 and 307 were introduced in version HTTP/1.1 and it is recommended to use them instead of 302. You need to change the method only if the server responded with 303. In other cases, make the next request with the original method.

The behavior of clients with various redirections is described in the table:

Response Status Caching If the method is not GET or HEAD

• 300 Multiple Choices - for the specified URI, there are several options for providing the resource by MIME type, by language, or by other characteristics. The server sends a list of alternatives with the message, allowing the client or user to make a choice automatically. Introduced in HTTP/1.0.
• 301 Moved Permanently - The requested document has been permanently moved to the new URI specified in the Location field of the header. Some clients behave incorrectly when processing this code. Introduced in HTTP/1.0.
• 302 Found, 302 Moved Temporarily - the requested document is temporarily available at another URI specified in the header in the Location field. This code can be used, for example, in server-driven content negotiation. Some[ which?] clients behave incorrectly when processing this code. Introduced in HTTP/1.0.
• 303 See Other - a document at the requested URI must be requested to the address in the Location field of the header using the GET method, even though the first one was requested using a different method. This code was introduced along with the 307 to avoid ambiguity, so that the server could be sure that the next resource will be requested using the GET method. For example, a web page has a text input field for quick transition and search. After entering the data, the browser makes a request using the POST method, including the entered text in the message body. If a document with the entered name is detected, the server responds with code 303, indicating its permanent address in the Location header. Then the browser is guaranteed to request it using the GET method to obtain the content. Otherwise, the server will simply return the search results page to the client. Introduced in HTTP/1.1.
• 304 Not Modified - the server returns this code if the client requested a document using the GET method, used the If-Modified-Since or If-None-Match header and the document has not changed since the specified moment. In this case, the server message should not contain a body. Introduced in HTTP/1.0.
• 305 Use Proxy - a request to the requested resource must be made through a proxy server, the URI of which is specified in the Location field of the header. This response code can only be used by origin HTTP servers (not proxies). Introduced in HTTP/1.1.
• 306 (reserved) - the previously used response code is currently reserved. Mentioned in RFC 2616 (HTTP/1.1 update).
• 307 Temporary Redirect - the requested resource is available for a short time at another URI specified in the Location field of the header. The request method (GET/POST) is not allowed to be changed. For example, POST request must be sent to the new URI using the same POST method. This code was introduced along with 303 instead of 302 to avoid ambiguity. Introduced in RFC 2616 (HTTP/1.1 update).

Client error

The 4xx code class is intended to indicate errors on the client side. When using all methods except HEAD, the server must return a hypertext explanation to the user in the body of the message.

• 400 Bad Request - the server detected a syntax error in the client's request. Introduced in HTTP/1.0.
• 401 Unauthorized - authentication is required to access the requested resource. The response header must contain the WWW-Authenticate field with a list of authentication conditions. The client can repeat the request by including the Authorization field in the message header with the data required for authentication.
• 402 Payment Required - intended to be used in the future. Currently not in use. This code is intended for paid user services and not for hosting companies. This means that this error will not be issued by the hosting provider in case of overdue payment for its services. Reserved since HTTP/1.1.

The server returned a 403 error when trying to view the “cgi-bin” directory, access to which was denied.

• 403 Forbidden - the server understood the request, but it refuses to fulfill it due to restrictions on the client's access to the specified resource. If HTTP authentication is required to access a resource, the server will return a 401 response, or a 407 response when using a proxy. Otherwise, the restrictions were set by the server administrator or web application developer and can be anything depending on the capabilities of the software used. In any case, the client should be informed of the reasons for refusing to process the request. Most probable reasons restrictions may result from attempting to access web server system resources (for example, .htaccess or .htpasswd files) or files to which access was denied using configuration files, a requirement for non-HTTP authentication, for example, to access a content management system or a section for registered users, or the server is not satisfied with the client’s IP address, for example, when blocking. Introduced in HTTP/1.0.
• 404 Not Found is the most common error when using the Internet, the main reason is an error in spelling the address of the Web page. The server understood the request, but did not find a corresponding resource at the specified URL. If the server knows that there was a document at this address, then it is advisable for it to use the code 410. The response 404 can be used instead of 403 if it is necessary to carefully hide certain resources from prying eyes. Introduced in HTTP/1.0.
• 405 Method Not Allowed - the method specified by the client cannot be applied to the current resource. In the response, the server must indicate available methods in the Allow header, separated by a comma. The server must return this error if the method is known to it, but it is not applicable specifically to the resource specified in the request; if the specified method is not applicable on the entire server, then the client must return code 501 (Not Implemented). Introduced in HTTP/1.1.
• 406 Not Acceptable - The requested URI cannot satisfy the characteristics passed in the header. If the method was not HEAD, then the server must return a list of acceptable characteristics for this resource. Introduced in HTTP/1.1.
• 407 Proxy Authentication Required - The response is similar to the 401 code, except that authentication is performed against a proxy server. The mechanism is similar to identification on the original server. Introduced in HTTP/1.1.
• 408 Request Timeout - the server’s waiting time for transmission from the client has expired. The client can repeat a similar previous request at any time. For example, this situation may arise when uploading a large file to the server using the POST or PUT method. At some point during the transfer, the data source stopped responding, for example, due to damage to the CD or loss of communication with another computer on the local network. While the client does not transmit anything, waiting for a response from it, the connection with the server is maintained. After some time, the server may close the connection on its end to allow other clients to make a request. This response is not returned when the client forcibly stops transmission at the user's command or the connection is interrupted for some other reason, since the response can no longer be sent. Introduced in HTTP/1.1.
• 409 Conflict - the request cannot be completed due to a conflicting access to the resource. This is possible, for example, when two clients try to change a resource using the PUT method. Introduced in HTTP/1.1.
• 410 Gone - the server sends this response if the resource used to be at the specified URL, but was deleted and is now unavailable. In this case, the server does not know the location of the alternative document (for example, a copy). If the server has a suspicion that the document may be restored in the near future, then it is better to send the code 404 to the client. Introduced in HTTP/1.1.
• 411 Length Required - For the specified resource, the client must specify Content-Length in the request header. Without specifying this field, you should not retry the request to the server using this URI. This response is natural for POST and PUT requests. For example, if files are downloaded at the specified URI, and the server has a limit on their size. Then it would be more reasonable to check the Content-Length header at the very beginning and immediately refuse the download, rather than provoke a meaningless load by breaking the connection when the client actually sends a message that is too large. Introduced in HTTP/1.1.
• 412 Precondition Failed - returned if none of the conditional header fields (If-Match, etc., see RFC 7232) of the request were fulfilled. Introduced in HTTP/1.1.
• 413 Payload Too Large - returned if the server refuses to process the request due to too much big size request body. The server may close the connection to stop further transmission of the request. If the problem is temporary, it is recommended to include a Retry-After header in the server response indicating the time after which a similar request can be repeated. Introduced in HTTP/1.1. Previously called "Request Entity Too Large".
• 414 URI Too Long - the server cannot process the request because the specified URI is too long. This error can be triggered, for example, when the client tries to pass long parameters via the GET method rather than the POST method. Introduced in HTTP/1.1. Previously called "Request-URI Too Long".
• 415 Unsupported Media Type - for some reason the server refuses to work with the specified data type using this method. Introduced in HTTP/1.1.
• 416 Range Not Satisfiable - a range outside the resource was specified in the Range field of the request header and the If-Range field was missing. If the client passed a byte range, then the server can return actual size in the Content-Range field of the header. This answer should not be used when passing multipart/byteranges[ source not specified 1964 days]. Introduced in RFC 2616 (HTTP/1.1 update). Previously called "Requested Range Not Satisfiable".
• 417 Expectation Failed - for some reason the server cannot satisfy the value of the Expect field in the request header. Introduced in RFC 2616 (HTTP/1.1 update).
• 418 I'm a teapot - This code was introduced in 1998 as one of the traditional IETF April Fool's jokes in RFC 2324, Hyper Text Coffee Pot Control Protocol. This code is not expected to be supported by real servers.
• 422 Unprocessable Entity - the server successfully accepted the request, can work with the specified type of data (for example, the body of the request contains an XML document with the correct syntax), but there is some kind of logical error due to which it is impossible to perform an operation on the resource. Introduced in WebDAV.
• 423 Locked - the target resource from the request is blocked from applying the specified method to it. Entered into WebDAV.
• 424 Failed Dependency - The implementation of the current request may depend on the success of another operation. If it is not completed and because of this the current request cannot be completed, then the server will return this code. Introduced in WebDAV.
• 425 Unordered Collection - used in the extension WebDAV Advanced Collections Protocol. Sent if the client specified the number of an element in an unordered list, or requested multiple elements in an order different from the server's.
• 426 Upgrade Required - the server indicates to the client the need to update the protocol. The response header must contain properly formed Upgrade and Connection fields. Introduced in RFC 2817 to allow transition to TLS over HTTP.
• 428 Precondition Required - the server indicates to the client the need to use condition headers in the request, like If-Match. Introduced in draft RFC 6585.
• 429 Too Many Requests - the client attempted to send too many requests in a short time, which could indicate, for example, an attempted DDoS attack. May be accompanied by a Retry-After header indicating after what time the request can be repeated. Introduced in draft RFC 6585.
• 431 Request Header Fields Too Large - The permissible length of headers has been exceeded. The server is not required to respond with this code; instead, it can simply reset the connection. Introduced in draft RFC 6585.
• 434 Requested host unavailable - The requested address is not available[ source not specified 1401 days].
• 449 Retry With - returned by the server if insufficient information was received from the client to process the request. In this case, the Ms-Echo-Request field is placed in the response header. Introduced by the corporation Microsoft For WebDAV. Currently at least used by the program Microsoft Money.
• 451 Unavailable For Legal Reasons - access to the resource is closed for legal reasons, for example, at the request of government authorities or at the request of the copyright holder in case of copyright infringement. Introduced in the IETF draft by Google, with the error code being a reference to Ray Bradbury's novel Fahrenheit 451. Was added to the standard on December 21, 2015.

server error

Example of 502 Bad Gateway error

Codes 5xx are allocated for cases of unsuccessful operation due to the fault of the server. For all situations other than using the HEAD method, the server must include in the body of the message an explanation that the client will display to the user.

• 500 Internal Server Error - any internal server error that is not included in the scope of other class errors. Introduced in HTTP/1.0.
• 501 Not Implemented - the server does not support the capabilities required to process the request. A typical response for cases when the server does not understand the method specified in the request. If the method is known to the server, but it is not applicable to this resource, then you need to return a 405 response. Appeared in HTTP/1.0.
• 502 Bad Gateway - the server, acting as a gateway or proxy server, received an invalid response message from the upstream server. Introduced in HTTP/1.0.
• 503 Service Unavailable - the server is temporarily unable to process requests for technical reasons(maintenance, overload, etc.). In the Retry-After header field, the server can specify the time after which the client is recommended to repeat the request. Although it may seem obvious to immediately break the connection during an overload, it may be more effective to install of great importance Retry-After fields to reduce the frequency of redundant requests. Introduced in HTTP/1.0.
• 504 Gateway Timeout - the server acting as a gateway or proxy server did not wait for a response from the upstream server to complete the current request. Introduced in HTTP/1.1.
• 505 HTTP Version Not Supported - the server does not support or refuses to support the HTTP protocol version specified in the request. Introduced in HTTP/1.1.
• 506 Variant Also Negotiates - As a result of an erroneous configuration, the selected variant points to itself, causing the binding process to be interrupted. Experimental. Introduced in RFC 2295 to complement the HTTP protocol with technology Transparent Content Negotiation.
• 507 Insufficient Storage - there is not enough space to complete the current request. The problem may be temporary. Introduced in WebDAV.
• 509 Bandwidth Limit Exceeded - used when a web platform exceeds its allotted limit on traffic consumption. In this case, the site owner should contact his hosting provider. At the moment, this code is not described in any RFC and is used only by the “bw/limited” module included in the hosting control panel cPanel, where it was introduced.
• 510 Not Extended - the server does not have the extension that the client wants to use. The server may additionally transmit information about extensions available to it. Introduced in RFC 2774 to add support for extensions to the HTTP protocol.
• 511 Network Authentication Required - this response is sent not by the server to which the request was intended, but by an intermediary server - for example, the provider's server - in case the client must first log in to the network, for example, enter a password for a paid Internet access point. It is assumed that the body of the response will return a Web authorization form or redirect to it. Introduced in draft RFC 6585.
• 520 Unknown Error, occurs when the CDN server was unable to handle a web server error; non-standard CloudFlare code,
• 521 Web Server Is Down, occurs when CDN connections are rejected by the web server; CloudFlare custom code.
• 522 Connection Timed Out, occurs when the CDN was unable to connect to the web server; CloudFlare custom code.
• 523 Origin Is Unreachable, occurs when the web server is unreachable; CloudFlare custom code.
• 524 A Timeout Occurred, occurs when the connection timeout between the CDN server and the web server expires; CloudFlare custom code.
• 525 SSL Handshake Failed, occurs when there is an error in the SSL handshake between the CDN server and the web server; CloudFlare custom code.
• 526 Invalid SSL Certificate, occurs when the web server’s encryption certificate cannot be verified; CloudFlare custom code.

Error when executing a server application: causes and methods of correction

Quite often, many users may see the message “An error occurred while executing the server application” on their monitor screen when performing some operations to open files. Let's try to look at several situations and understand what it is and how to get rid of such a scourge.

What is a "server application execution error"?

Among all the situations that lead to this type of problem, the most common is the problem of playing multimedia files. In this case, most often the server execution error occurs when trying to view a video.

As is known, standard Windows Media Player is far from ideal and does not always work correctly as a multimedia tool installed on the system by default. In addition, a different kind of situation may arise. This may be due, for example, to programs such as 1C, installation of MS Link Server 2013, etc. Only in this case the user receives a message like “Error executing the command.”

For obvious reasons and due to the complexity of the latest programs, we will not consider them, but will focus on the components responsible for the correct opening of multimedia files.

Viruses and system recovery

If the user receives a message that a server application execution error has occurred, the first thing to do is run a check computer system for the presence of viruses (some malware can lead to such consequences).

If the check does not produce results even when using an independent portable antivirus with fresh databases, it is worth looking at exactly when the error first appeared, and then trying to roll back the system to its original state using a restore from any checkpoint that preceded this situation. It may very well be that this approach will help (especially if multimedia updates have recently been installed).

Problems with drivers, codecs and the DirectX platform

On the other hand, neither viruses nor updates may have anything to do with it. If suddenly the system reports that an error of this type occurred during an operation, it is very likely that, for example, the video accelerator drivers require updating or that the codecs and decoders used in a video file have a higher version than those installed on this computer.

As is already clear, these components simply need to be updated. For video cards, you can use Task Manager, download the file with the latest driver version from the manufacturer's official website manually, or update it using specialized utilities For automatic search and update.

The same applies to the codec and decoder package. Fortunately, today we can find the latest distribution of the same K-Lite package Codec Pack On the Internet it is not difficult. The only thing you need to pay attention to is the mandatory check with anti-virus software if it was not downloaded from an official source.

Often the problem when an error occurs when executing a server application may be due to the presence outdated version DirectX. There is nothing easier than going to the official Microsoft website, downloading the latest DirectX release from there and reinstalling all its components.

Simple commands for troubleshooting

If the above methods do not help, and the error occurs again and again when running the server application, you will have to use the command line. You can call it from standard menu“Run” by writing cmd in the field.

After a black window opens like old system DOS, you need to sequentially enter two commands regsvr32 jscript.dll and regsvr32 vbscript.dll, after each of them pressing the Enter key.

After this, a system reboot will be required. True, in some cases even this may not give desired result. Then you will need to enter additional sfc teams/scannow. In theory, in combination with the previous two, it should save the user from further errors and failures.

Problems with Windows Media Player

Now a few words about the “native” Windows player. As a rule, the error when executing a server application appears in it. And this doesn’t even apply to viewing. streaming video online, and even by simply opening a video file.

The simplest solution would be to install any other player, say, VLC Media Player or something like that. If the file you are looking for opens with such a player without problems, then the problem really lies in the player Windows Media Player. You can refuse it.

But if you are already a supporter of this program and do not want to change your preferences in any way, you can use another radical method. Not to mention updating the player, you will have to contact installed components Windows.

To do this, you need to use the Programs and Features section in the Control Panel (in older operating systems this is the Add and Remove Programs section), where there is a special menu for enabling and disabling system components. In the list of installed software, find Windows Media Player and uncheck the box next to it. We reboot the system, after which we go back to the same section and return the checkbox to its place. A reboot is required again.

With a very high degree of probability it can be said that this error will be eliminated, although, in principle, no one can say exactly how to disable and restart the “native” player affects the correctness of its operation. It may very well be that the developers themselves are not aware of this.

Conclusion

So we looked at the most likely situations of server application execution errors, and indicated the main methods for correcting them. However, if an error occurs while executing the server application, these are not all the methods, because sometimes if there are failures in the “OS” itself, you may need to boot from the installation disk or flash drive, update other components, etc. We have given only the simplest options.

What does DNS error mean?

If you see a DNS error while using your computer or the Internet, remember that there is a problem with the settings. If this problem is not resolved, the user will not be able to visit the desired website.

What is DNS?

For a domain, DNS will be the name of the service and will help in gaining access to resources on the Internet. The goal is to translate the address the user enters into the browser. Translation is carried out from the language used into the computer language. This procedure helps the computer read and understand the address in order to open access to the site passing through the server.

What is a DNS error?

This type of error for a specific website is mainly due to the lack of an active connection to the network. It also means that the equipment is not able to connect to the Internet to convert the entered address. For this reason, the computer is not able to visit the selected site.

Errors occur for certain reasons, and most often they can be easily resolved. Sometimes the device shows them only for certain resources. In this case, the address may be entered incorrectly or there may be no record of it on the network.

What should you pay attention to first?

If the server is not found due to an error DNS lookup, there may not be any problems with the computer. For this reason, you should pay attention to the recommendations presented and use them.

• It is worth checking whether difficulties arise when trying to access one site or all. In the first case, the resource may undergo some changes or encounter operational problems. The user should wait or clear the DNS cache using the ipconfig /flushdns command in a special line as an administrator.
• If possible, you should check: the DNS error appears on one device used or on others as well. If all devices are affected, then the problem may be with the provider. In this case, you should wait until the problem is resolved.
• When connecting using Wi-Fi router it must be completely turned off and restarted. The next time you try to access the site, the DNS server error will likely go away.
• When connecting to the Internet without using a Wi-Fi router, it is recommended to go to the list of connections on your computer. Next you need to turn off the local network and turn it on again.

It is worth understanding that after these manipulations the DNS error may remain. In such a situation, it is worth using other methods to correct it.

Using Google Public DNS

• You need to go to the list of device connections. The easy way To do this, press the Win+R key combination and enter the command ncpa.cpl.
• It is worth choosing the connection used to access the Internet. He is high speed connection PPPoE, L2TP or the local network. The required element is selected and the “Properties” item is clicked.
• The TCP/IPv4 protocol is selected among the components used by the connection.
• If the server is not found due to a DNS lookup error, it is important to check what settings are available in the DNS server settings. When receiving an address automatically, you should proceed to entering addresses. Then the values ​​8.8.8.8 and 8.8.4.4 are specified. Otherwise, you must first set it to receive automatically.
• After saving the settings, you should run the command line as an administrator and run ipconfig /flushdns.

Troubleshooting browser problems

Checking DNS connections is possible when using a different browser. To do this, download any web browser. On this moment There are a large number of them, and they are mostly provided free of charge. After the browser is open, you need to connect to the Internet. If the service is not found again due to a DNS lookup error, then there are no errors in the browser. This means there is a problem with other computer settings.

At complete absence problems, the user must troubleshoot the old browser. Quite often they arise due to proxy settings. Accordingly, it is necessary to change them.

Cleaning and changing DNS

First of all, if a DNS error appears, you should clear the cache manually, since the setting becomes outdated over time. This can be done from the command line. This procedure is simple, but it may not be effective. If the error DNS connections will not be eliminated, it is worth changing the service.

The user has the ability to independently enter an alternative DNS server to make a connection. To do this, go to the ncpa.cpl section and select the active connection, and then go to Properties. You need to find the TCP/IPv4 network protocol entry, which is located in the “Network” tab. Then properties and the option to go to the server address are selected. In the Preferred field DNS server the user must enter 208.67.222.222. Then in the Alternate DNS server field you need to enter 208.67.220.220. Newly created DNS servers will be open source.

Slow server response when using Google

In this case, an error in searching for a DNS server means that Googlebot is not able to contact it. This happens because it is not working or there is a problem with DNS routing for the user's domain. Most warnings and errors do not affect the functioning of the robot. Their occurrence can also be explained by a long reaction, which is an unpleasant moment for users.

The first thing you should do is make sure that Google is crawling your site. To do this, you should use the tool for the main page of the resource. Google will have access to the site if the user returns the content without defects. The DNS service may be provided by your web hosting provider or another company. It is worth contacting her if the code appears DNS errors probe finished or others.

The server can be configured for a site using wildcards so that it starts responding to requests for subdomains. This approach will be successful if the content of the resource can be created by users, and at the same time for each personal page provided separate domain. It's worth noting that in some situations this may result in duplicate content on hosts with different names. In most cases, this prevents the resource from being crawled by Googlebot.

Performing a virus scan on your computer

The previously discussed methods may not help. If the DNS error still appears on the screen, and it is not caused by factors that affect the computer externally, then you should scan it for viruses. The user may already have an antivirus installed on their device. It is recommended to use Kaspersky, and its free trial version is suitable. Bitdefender in a similar design would also be an excellent option.

The level of detection and the ability to effectively eliminate viruses, while restoring system parameters, are quite high in these antiviruses than in their analogues. In this case it is worth using full check systems. Application this method can be really useful if you can't get rid of the problem in the browser itself.

Antivirus malfunction

It is worth paying attention to the fact that the antivirus itself in some cases can cause problems with connecting to the Internet. This can also be fixed. To carry out the procedure, “ Safe mode" In this case, the computer will restart, during which only the necessary ones will be loaded. operating system files. This will help determine whether the problem is caused by an antivirus or another program. To verify this, it is recommended to do the following:

• First of all, you should turn off your antivirus. If there are no connection errors, you should uninstall the antivirus and install a new one.
• Next, you need to reboot the device. While loading it, hold down the F8 key.
• You should select “Safe Mode with Networking” from the options provided.
• The connection is then checked. If you successfully connect to the network, you can conclude that the problem lies in the program that is currently running on the computer.

It is necessary to carefully study the startup files and disable programs until the faulty one is found.

Router

If the server is not found due to a DNS lookup error, it's worth looking at the router again. Rebooting it may not help in this case. In some situations, settings become damaged. The most correct and quick solution is to reset the device to default settings. As a result, the wireless network parameters will be reset. Along with them, the information transmitted through the port will disappear.

To complete the procedure, you must press and hold the Reset button, which is located on the back panel of the device. In this case, you may need a pointed object, such as a paper clip. Then you need to reconfigure the router. After resetting the device, you should change the wireless network settings, if used by the user. This will reset all Accounts and administrator passwords. Making the settings is a simple procedure, but it requires care and correct actions. If the problem was in the router, then after the work done it should be completely resolved.

Additionally, there is a possibility that the router is completely faulty. If you can't reset it and reinstall it, you should contact your Internet provider. In this case, it will be possible to determine the cause of the difficulty connecting to the network. In addition, the procedure will be performed by a specialist.

The need to indicate the DNS of your hosting in the domain record

A name server is designed to assist in finding information about a specific site. By completing a record in their domain, the user will provide the Internet audience with information in the right direction that will lead to the right place.

If you leave the previous provider's data in the domain record, the user will be transferred to a server that no longer has the site. In this case, it will be impossible to access the site, since the provider has deleted the resource record from the DNS. Correct execution is quite important, and failure to follow the recommendations can lead to difficulties.

You should follow the steps described in the material if the server is not found due to a DNS error. The tips presented will be useful, because they help determine the cause of the problem and eliminate it in a timely manner. The information indicated above will become relevant for Internet users, since many of them are faced with the described difficulty. In addition, you can turn to specialists if you yourself cannot get rid of the problem that has arisen with gaining access to sites. This will be the most correct solution in this case.

What is an internal server error?

Vladislav!!!

An error is a discrepancy between two groups of objects, one of which is a standard (a grammatical rule, the correct answer to a problem, a solution that would lead to the desired result), and the second is something that occurs in reality. Errors occur in all areas of human activity. Probability theory and statistics have been developed to analyze measurement errors. The inaccuracy of measurements in the microcosm is one of the principles of quantum mechanics. There are many historical examples in which mistakes led to catastrophic consequences. Many aphorisms are devoted to errors; they are interpreted by philosophers, poets, writers, historians and representatives of many other disciplines. Thus, many dialytic philosophers agree with the statement “they learn from mistakes.” Skeptics and agnostics believe that all our ideas are most likely erroneous.
It depends on the server error...
404 (Not Found or No Resource)
Indicates that there is no resource at this address.
405 (Method Not Allowed)
Indicates that a request method is not provided for this address.
406 (Not Acceptable or Invalid request)
Indicates that the request has no content objects matching the response.
407 (Proxy Authentication Required or Registration required on the proxy server)
Indicates that the client needs to be authenticated. Proxy-Authorization and Proxy-Authenticate are used.
408 (Request Timeout or Request processing time has expired)
This means that the request was not made within the time set by the server.
409 (Conflict)
Indicates that there is a conflict between the request and the state of the resource at the moment.
410 (Gone or Resource permanently deleted)
Indicates that the resource has been permanently deleted.
411 (Length Required)
Indicates that the server does not accept a request with an unspecified Content-Length. You must specify the correct Content-Length in the request header.
412 (Precondition Failed or Any precondition is not met)
Indicates that the server refuses to process the request due to exceeding its size limit.
413 (Request Entity Too Large)
Indicates that the server will not process the request due to its large size.
414 (Request-URI Too Long or The resource identifier in the request exceeds the maximum length)
Indicates that the requested address exceeds the maximum length.
415 (Unsupported Media Type or this device type is not supported)
Indicates that the request object has a format different from the request format.
500 (Internal Server Error or Error inside the server)
Indicates that an internal failure occurred on the server while processing the request.
501 (Not Implemented or There is no implementation of this function)
Indicates that the function requested by the client is not supported by the server or the server cannot recognize the request method.
502 (Bad Gateway or Poor Gateway)
Indicates that there was a failure on the server that is used as the gateway.
503 (Service Unavailable)
Indicates that any of the server services are currently unavailable.
504 (Gateway Timeout or Gateway Timeout Expired)
Indicates that the gateway has exceeded the maximum time limit.
505 (HTTP Version Not Supported or This version HTTP is not supported)
Indicates that the HTTP version specified in the request is not supported by the server.

User deleted

500. Internal Server Error (Russian: Internal server error) - any internal server error that is not included in the scope of other errors of class 5xx. The server is unable to complete a valid request, or does not support requests of the specified type.
Look at: http://ru.wikipedia.org/wiki/HTTP_404#404

What does it mean: Error: HTTP 500 - internal server error?

I can't get to the site. The browser shows:

Error: HTTP 500 - Internal server error

What does it mean? Is this the end of the site?

Galina Vasilna

Codes starting with 5XX mean that the request was completed correctly, but the server is currently unable to cope. When they don't open for a while, the browser should respond. Each browser responds differently. I have a Yandex browser, it most often asks, should I wait or close? But sometimes it shows "error no...."

There are many server response codes, their meanings are different. The simplest thing is to try refreshing the page by pressing F5. Quite often this resolves the issue. You can ask what this or that code means, it’s here

You can try to solve the issue this way:

Or here is another version of the explanation, which is more suitable for whom:

Foxanoreth

This is an internal server problem, and you definitely won’t be able to solve it from the side of an ordinary third-party user. You should wait a little, for example about half an hour, while doing other things, and then try to contact the server again later.

We have released a new book “Content Marketing in in social networks: How to get into your subscribers’ heads and make them fall in love with your brand.”

Subscribe

Internal server error is an HTTP protocol status class that means that the user's operation/request failed and the server itself is to blame.

More videos on our channel - learn internet marketing with SEMANTICA

You've run out of food. You need to go to the grocery store. There is a sign on the door - “Accounting”. You are without food.

The user wants to visit the site. A request is sent to the server. And if there are any problems on the server, then the person will see an error message in the browser window.

What are the server errors?

As we've learned, internal server errors constitute a class of HTTP statuses.

• . Indicates a wide range of server errors, if they do not belong to the following problems of the class in question.
• 501. Means that the server does not have the necessary capabilities to process the user request. Typically, a 501 error appears when the server cannot recognize the request method. If the server recognizes the request method, but it cannot be used on this Internet resource, error 405 is displayed (occurred due to the user’s fault).
• . Occurs when the server acts as a proxy or gateway. The error indicates that the upstream server is sending an invalid response.
• . Displayed when the site is unable to process user requests. This may be due to overload, maintenance problems, technical problems, and so on. Most often, when a 503 error is displayed, the Retry-After field indicates the time when the user needs to repeat the request.
• 504. Here again the server acts as a gateway or proxy server. It forwards the request to the upstream server, but does not wait for a response, and therefore cannot complete processing of the request.
• 505. Indicates that the request version is not supported by the server.
• 506. This means that the current version of the server has an incorrect configuration. In this regard, the binding process does not reach completion and is interrupted all the time.
• 507. There is no space on the server to complete the request and process it. Problems of this kind may be temporary and easily fixed.
• 509. If an Internet resource has spent all the traffic that was allocated to it, this error occurs. To resolve the problem, you need to contact your hosting provider.
• 510. This error can be encountered in cases where the client makes a request and wants to use a certain extension, but the server does not use and cannot provide this extension.
• 511. This error does not come from the server itself, which the user is accessing, but from an intermediary, which can be a provider. Typically, the problem occurs when the client needs to log in to global network(specify the password for the paid access point). In this case, a special field for authorization is displayed in the response form.
• 520. Indicates that there is an error, but the CDN server cannot correctly process the error and display it to the client.
• 521. Occurs in situations where the server rejects the content delivery network connection.
• 522. Displayed when the data communication system cannot connect to the server and is timed out waiting for a server response.
• 523. The server cannot be “reached”; when accessing the server, serious obstacles arise, overcoming which is currently not possible.
• 524. Connection time has expired between the required server and the content delivery network server.
• 525 If errors occur during the handshake between the server itself and the CDN server, code 525 is displayed.
• 526. Indicates that there is currently no way to validate the encryption certificate.

What to do if they write “Server error”

The listed errors usually arise due to the .htaccess file, themes and plugins. Let's consider options for solving the problem.

So, you liked the new theme and installed it. Everything would be fine, but then an internal server problem arises. To restore the server's functionality, select one of the following methods:

Via FTP

We go into it and look for a folder with themes. Open the folder and correct/delete the theme that is currently posted on the site. We go to the site and see a blank page without errors.

Open the WordPress admin panel, then the theme, and receive a notification that another theme has been activated. A little advice: do not delete standard themes, they serve as a standard and can be activated after the site is restored.

Via PhpMyAdmin

If you have deleted/edited the standard theme, you need to download and install it again. This can be done from the following resources: TwentyTen, TwentyEleven, TwentyTwelve. After downloading, open PhpMyAdmin, then the database.

Go to the SQL tab and copy the code below into it.

Please note that the topic name must be specified correctly. Then the site will work as usual.

If the problem is with plugins, the server does not work correctly and the site is displayed differently. At the same time, access to the console is preserved, which allows you to disable this or that plugin. Sometimes an installed plugin may conflict with other plugins that are already installed and activated on the resource. Then it crashes and generates an internal error. You can disable the plugin in 3 steps:

1. Open the FTP resource.
2. Open the folder with existing plugins.
3. Delete/change the name/edit the plugin.

If the errors are problems with the .htaccess file, you need to do the following:

1. Open FileZilla, the “Server” menu and check the box next to the “Force hidden files” item. We update the list of files and find our .htaccess file.

2. Open the file through notepad/text editor. A text is displayed in front of you - a list of instructions and rules for the functioning of the web server. Review the file and correct any errors. An alternative option is to delete the file completely and then write with using WordPress new file(open the admin panel, then “Options”, then “Permalinks”. Select the right option, click "Save").

If the above measures do not give the desired result, you must contact a qualified programmer.

As you can see, the list of errors is quite wide. If identified, they must be eliminated as early as possible.