-
The path of the iis bind ** is wrong, we should bind 12345, but we bind the 123456, which will also cause the **500 error.
The 500 InternalServer Error is mainly caused by the wrong password for IWAM. This error indicates that the IIS server is unable to resolve ASP**, and if you visit a static page to see if this problem also occurs.
If there is no problem with accessing static pages, then it is necessary to analyze the following situations:
Have you ever changed the name of your computer?
Whether the file directory where the site is located has custom security attributes.
Whether the domain policy has been adjusted after the domain controller has been installed. If this is one of the cases, please check back the changed parameter settings one by one to see if the problem is solved. If the static space cannot be accessed, the parsing has not yet taken effect.
-
Questions, none of your computer's business.
-
Internal Server 500 Error Reason:1) External resource timeout.
2) Triggered by wrong file and directory permissions through the issue.
3) In. The htaccess file is misconfigured.
Here's how to solve it.
External resources time out, and sometimes, the web server may need to respond to a request from a remote server to complete processing a request from a client. It is possible that these external resources may time out. This can be a php timeout.
In this case, the web server will return a 500 internal server error. We can fix this bug by increasing the timeout value or setting other appropriate timeout options so that the remote server will not return a timeout error, but instead wait for the request to be processed.
Caused by the wrong file and directory permission issues, which are the cause of the most internal server errors. If there is an extra file or if the permissions for the directory required to process the client request are set incorrectly, the wrong server access is returned. PHP script wrong permissions are an example of this type of problem.
This issue can be fixed by re-applying the correct permissions to the file or directory.
Misconfigured. Another common reason for htaccess file, 500 internal server error is in. Misconfiguration in the htaccess file.
Errors in URL rewrites can result, but are often not 500 internal server errors....Finding and correcting misconfigurations in the htaccess file can solve this problem.
-
1. Problem description, here we take Empire** as an example, after logging in to the backend, there is a "server error, 500 - internal server error".
2. Enter the IIS Manager in the server, find the IIS management page of the corresponding **, and select "Error Page".
3. In the new page, select one item with the transmutation code of 500, and then select the function setting on the right.
<>5. We will log in again to refresh the page, and then the error details will be displayed, and the detailed location of the error will be given. This way we can solve the problem based on this detailed location.
6. The error here is because the file cannot be accessed, and then we detect this file in the background. It may be because it was deleted by mistake or lost. We can make use of the files that were previously backed up to fix it. I'm replacing it with the file I backed up earlier.
7. After replacing the file, we can log in to the **background again to display it normally. This method four is suitable for any ** backend that uses the IIS server, and it is not only applicable to 500 server errors, as long as it is an internal server error, it can be detected in this way.
-
There are many reasons for the 500 error, and if it is a user rights issue, it can be solved by the following methods:
1. Double-click to turn on the computer.
2. Right-click on Local Disk.
3. Select "Properties" and click to <>
4. Click on the "Security" tab.
5. Select the user you want to modify the permissions and click "".
6. Tick "Full Control".
7. Then click "OK" to save the settings.
Some ** appear blank or not correctly in Internet Explorer. For example, some page content may be missing, or the colors and text may be incorrect. Some pages may not display at all. >>>More
First determine if it's caused by a network failure, if not, take a look at the methods below. >>>More
Possibly. But it's also possible that you have too much stuff on your computer.
The first thing that can tell you is that there are no problems with your network and routing. The situation you mentioned is that the firewall trusts the software or accesses ** and automatically prohibits access because it does not trust the plug-in; The second is because you are connected to multiple computers and other computers are opening BT and other software** things or the network itself, resulting in the network speed is too slow (because of the advantage of bandwidth and response speed, it will be faster than others**, QQ because the data exchange with the host is different from IE, so it is not easy to find), if this is the case, you can enter the ping command in the command box to ping the local telecom host to judge, the more the value in the ms column in the beating data** the faster the clear network speed, The command format is ping the telecom host IP (for example, -l 1024 -t for Jiangxi; The third is that the data flow of the ** you are accessing itself is abnormal, resulting in a short-term failure or slow access.
1: Only open one IE window, then maximize -- close IE, and open IE again. If that doesn't work, use the second method. >>>More