What is 5xx status – This is Server related Error?
This group of HTTP status codes indicates that the server is aware that it is on error or is incapable of performing the request. The server response usually includes an explanation of the error situation and if it is a temporary or permanent condition. These response codes in this group are applicable to any request method.
What is 500 Server Error? – Internal Server Error
The web server responds with this status code when it has encountered an unexpected condition, which prevented it from fulfilling the request by the client.
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site’s server but the server could not be more specific on what the exact problem is.
Resolution Possibilities
The 500 Internal Server Error is a “server-side” error, meaning the problem is not with your PC or Internet connection but instead is a problem with the web site’s server.
Even though the issue is not yours to troubleshoot or resolve, there are a few things you can do:
If the 500 Internal Server Error message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders – and multiple charges! Most merchants have automatic protections from these kinds of actions but it’s still something to keep in mind.
- Retry the web page by clicking the refresh/reload button or trying the URL from the address bar again. Even though the 500 Internal Server Error is reporting a general error on the web site’s servers and not your computer, the server error may only be temporary. Trying the page again will often be successful.
- Come back later. The 500 Internal Server Error message is one of the most common error message seen when checking out during an online purchase so sales are often disrupted. This is usually a great incentive to resolve the issue very quickly.
- Try Clearing your cache and browser history. It could be possible that the page you are seeing is a cached version, so after the cache is cleared it will go away.
- You can check the error log button in cPanel under the logs section to see what errors are being given if you have cPanel hosting with us. Sometimes 500 errors can be due to syntax errors in a .htaccess file or other things you may be able to quickly fix yourself.
Crosscheck your cPanel if you have access:-
- First, log into cPanel within the “Shared Hosting” tab. View our guide herefor further details on how to do this.
- Scroll down to the “Metrics” section. And click the “Errors” icon
This log will display a list of error messages from your website. You will find detailed information about each error including: the date and time of the error, some information about the client receiving the error, description of the error and information about which folder or file is generating the error. From this log, you can seek resolution depending on the information about the error that you receive.
What is 501 Server Error? – Not Implemented
The web server responds with this status code when it does not support the functionality required to process the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
A 501 is an HTTP status code for not implemented. This status code is received when the web server does not support the facility required.
Note: A 501 error is not something you can fix, but rather will require a fix by the web server admin who manages the website and server you are trying to access.
Reason 1 – Web server overload!
If the server you’re attempting to load is experiencing high demand, it may be unable to complete your request and generate this error. If you’re experiencing this error on a page you know is functional, try loading the page again after a few minutes. If that is unsuccessful, try loading the page again later that day or the next day.
Reason 2 – Web server errors!
Visitors may also encounter this error when a web server does not properly respond to a browser’s request or the program making the request.
Reason 3 – Web server out of date!
Finally, in some rare situations, the web server may need a software upgrade to properly communicate with your web browser or program
What is 502 Server Error? Bad Gateway
The server responds with this status code when, while acting as a gateway or proxy, it received an invalid response from the upstream server it accessed in attempting to process the request.
The 502 Bad Gateway error is an HTTP status code that means that one server on the internet received an invalid response from another server.
502 Bad Gateway errors are completely independent of your particular setup, meaning that you could see one in any browser, on any operating system, and on any device.
The 502 Bad Gateway error displays inside the internet browser window, just like web pages do.
How the 502 Bad Gateway Error Appears
The 502 Bad Gateway can be customized by each website. While it’s fairly uncommon, different web servers do describe this error differently. Below are some common ways you might see it:
- 502 Bad Gateway
- 502 Service Temporarily Overloaded
- Error 502
- Temporary Error (502)
- 502 Proxy Error
- 502 Server Error: The server encountered a temporary error and could not complete your request
- HTTP 502
- That’s an error
- Bad Gateway: The proxy server received an invalid response from an upstream server
- HTTP Error 502 – Bad Gateway
Twitter’s famous “fail whale” error that says Twitter is over capacity is actually a 502 Bad Gateway error (even though a 503 Error would make more sense).
A Bad Gateway error received in Windows Update generates a 0x80244021 error code or the message WU_E_PT_HTTP_STATUS_BAD_GATEWAY.
When Google services, like Google Search or Gmail, are experiencing a 502 Bad Gateway, they often show Server Error, or sometimes just 502, on the screen.
Cause of 502 Bad Gateway Errors
Bad Gateway errors are often caused by issues between online servers that you have no control over. However, sometimes, there is no real issue but your browser thinksthere is one thanks to an issue with your browser, a problem with your home networking equipment, or some other in-your-control reason.
Note: Microsoft IIS web servers often give more information about the cause of a particular 502 Bad Gateway error by adding an extra digit after the 502, as in HTTP Error 502.3 – Web server received an invalid response while acting as a gateway or proxy, which means Bad Gateway: Forwarder Connection Error (ARR). You can see a complete list here.
An HTTP Error 502.1 – Bad Gateway error refers to a CGI application timeout problem and is better to troubleshoot as a 504 Gateway Timeout issue.
How to Fix a 502 Bad Gateway
The 502 Bad Gateway error is often a network error between servers on the internet, meaning the problem wouldn’t be with your computer or internet connection.
However, since it is possible that there’s something wrong on your end, here are some fixes to try:
- Try loading the URLagain by pressing F5 or Ctrl-R on your keyboard, or by clicking the refresh/reload button.
While the 502 Bad Gateway error is usually indicating a networking error outside of your control, it could be extremely temporary. Trying the page again will often be successful.
- Start a new browser session by closing all open browser windows and then opening a new one. Then try opening the webpage again.
It’s possible that the 502 error you received was due to an issue on your computer that occurred sometime during this use of your browser. A simple restart of the browser program itself could solve the problem.
- Clear your browser’s cache. Outdated or corrupted files that are being stored by your browser could be causing 502 Bad Gateway issues.
Removing those cached files and trying the page again will solve the problem if this is the cause.
- Delete your browser’s cookies. For similar reasons as mentioned above with cached files, clearing stored cookies could fix a 502 error.
If you’d rather not clear all of your cookies, you could first try removing only those cookies related to the site you’re getting the 502 error on. It’s best to remove them all but it won’t hurt to try the clearly applicable one(s) first.
- Start your browser in Safe Mode. Running a browser in Safe Modemeans to run it with default settings and without add-ons or extensions, including toolbars.
If the 502 error no longer appears when running your browser in Safe Mode, you know that some browser extension or setting is the cause of the problem. Return your browser settings to default and/or selectively disable browser extensions to find the root cause and permanently fix the problem.
Note: A browser’s Safe Mode is similar in idea to the Safe Mode in Windows but it’s not the same thing. You do not need to start Windows in Safe Mode to run any browser in its particular “Safe Mode.”
- Try another browser. Popular browsers include Firefox, Chrome, Internet Explorer, and Safari, among others.
If an alternative browser doesn’t produce a 502 Bad Gateway error, you now know that your original browser is the source of the problem. Assuming you’ve followed the above troubleshooting advice, now would be the time to reinstall your browser and see if that corrects the problem.
- Download Software Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1if you have MS Forefront TMG SP1 installed and receive the message Error Code: 502 Proxy Error. The network logon failed. (1790) or a similar message when accessing a web page.
Important: This is not a common solution to 502 Proxy Error messages and only applies in this particular situation. Forefront TMG 2010 is a business software package and you would know if you have it installed.
- Restart your computer. Some temporary issues with your computer and how it’s connecting to your network could be causing 502 errors, especially if you’re seeing the error on more than one website. In these cases, a restart would help.
- Restart your networking equipment. Issues with your modem, router, switches, or other networking devices could be causing 502 Bad Gateway or other 502 errors. A simple restart of these devices could help.
Tip: The order you turn off these devices isn’t particularly important, but be sure to turn them back on from the outside in. Check out that link above for more detailed help on restarting your equipment if you need it.
- Change your DNS servers, either on your router or on your computer or device. Some Bad Gateway errors are caused by temporary issues with DNS servers.
Note: Unless you’ve previously changed them, the DNS servers you have configured right now are probably the ones automatically assigned by your ISP. Fortunately, a number of other DNS servers are available for your use that you can choose from. See our Free & Public DNS Servers list for your options.
- Contacting the website directly might also be a good idea. Chances are, assuming they’re at fault, the website administrators are already working on correcting the cause of the 502 Bad Gateway error, but feel free to let them know about it.
See our Website Contact Information page for a list of contacts for popular websites. Most websites have social networking accounts they use to help support their services. Some even have telephone and email contacts.
Tip: If you suspect that a website is down for everyone, especially a popular one, checking Twitter for chatter about the outage is often very helpful. The best way to do this is to search for #websitedownon Twitter, as in #cnndown or #instagramdown.
- Contact your Internet Service Provider. If your browser, computer, and network are all working and the website reports that the page or site is working for them, the 502 Bad Gateway issue could be caused by a network issue that your ISP is responsible for.
Tip: See How to Talk to Tech Support for tips on talking to your ISP about this problem.
- Come back later. At this point in your troubleshooting, the 502 Bad Gateway error message is almost certainly an issue with either your ISP or with the web site’s network — one of the two parties might have even confirmed that for you if you contacted them directly. Either way, you’re not the only one seeing the 502 error and so you’ll need to wait until the problem is solved for you.
What is 503 Server Error? Service Temporarily Unavailable
A 503 Service Unavailable Error is an HTTP response status code indicating that a server is temporarily unable to handle the request. This may be due to the server being overloaded or down for maintenance. This particular response code differs from a code like the 500 Internal Server Error we explored some time ago. While a 500 Internal Server Error indicates an issue preventing the server from handling the request entirely, a 503 Service Unavailable Error is an indication that the server is still functioning properly, since it’s able to process the request and has opted to return the 503 response code.
The Problem is Server-Side
All HTTP response status codes that are in the 5xx category are considered server error responses. Unlike the 502 Bad Gateway Error we’ve looked at recently, which indicates that a server somewhere in the connection chain is down or unavailable, a 503 Service Unavailable Error simply indicates that the server is temporarily unable to handle the request, but that is is functioning as normal otherwise.
Start With a Thorough Application Backup
As with anything, it’s better to have played it safe at the start than to screw something up and come to regret it later on down the road. As such, it is critical that you perform a full backup of your application, database, and so forth, before attempting any fixes or changes to the system.
Diagnosing a 503 Service Unavailable Error
As mentioned, a 503 Service Unavailable Error indicates that the server (typically the actual web server on which your application is running) is temporarily unavailable. This is usually due to the server being “down” for scheduled maintenance, or due to a heavy load of traffic that is preventing it from properly serving all incoming requests.
Troubleshooting on the Server-Side
Here are some additional tips to help you troubleshoot what might be causing the 503 Service Unavailable to appear on the server-side of things:
Reboot the Server – If you or an administrator have the ability to do so, one of the simplest solutions is often to restart the web server hosting the application. If your application is spread over multiple servers, make sure all are rebooted in the proper manner so the system is brought back online as normal.
Check for Unexpected Maintenance – You may not realize it, but your server and/or application may be configured to go down for maintenance automatically. Many modern content management systems like WordPress will automatically download and install updates to their base software without any intervention on your behalf.
Server Connectivity Issues – While it may sound simple, it’s entirely possible that a 503 Service Unavailable Error simply indicates that a server somewhere in the chain is down or unreachable for whatever reason.
Improper Firewall Configuration – A firewall is a basic security device that monitors network traffic and acts as a gatekeeper, deciding which traffic is safe and which could be malicious. In most cases, all potentially harmful traffic is stopped (and may be logged for network admin use).
Check the Logs – Server logs are related to the actual hardware that is running the application, and will often provide details about the health and status of all connected services, or even just the server itself. Google “logs [PLATFORM_NAME]” if you’re using a CMS, or “logs [PROGRAMMING_LANGUAGE]” and “logs [OPERATING_SYSTEM]” if you’re running a custom application, to get more information on finding the logs in question.
Application Code or Script Bugs – If all else fails, it may be that a problem in some custom code within your application is causing the issue. Try to diagnose where the issue may be coming from through manually debugging your application, along with parsing through application and server logs.
What is 504 Server Error? Gateway Timeout
The 504 Gateway Timeout error is an HTTP status code that means that one server did not receive a timely response from another server that it was accessing while attempting to load the web page or fill another request by the browser.
In other words, 504 errors usually indicate that a different computer, one that the website you’re getting the 504 message on doesn’t control but relies on, isn’t communicating with it quickly enough.
Are You the Webmaster? See the Fixing 504 Errors on Your Own Site section further down the page for some things to consider on your end.
How You Might See the 504 Error
Individual websites are allowed to customize how they show “gateway timeout” errors, but here are the most common ways you’ll see one spelled out:
Causes of 504 Gateway Timeout Errors
Most of the time, a 504 Gateway Timeout error means that whatever other server is taking so long that it’s “timing out,” is probably down or not working properly.
Since this error is usually a network error between servers on the internet or an issue with an actual server, the problem probably is not with your computer, device, or internet connection.
What is 505 Server Error? VERSION NOT SUPPORTED
The server does not support, or refuses to support, the major version of HTTP that was used in the request message.
The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in Section 2.6 of RFC7230, other than with this error message. The server SHOULD generate a representation for the 505 response that describes why that version is not supported and what other protocols are supported by that server.
The Web server (running the Web site) does not support, or refuses to support, the HTTP protocol version specified by the client (e.g. your Web browser or our CheckUpDown robot) in the HTTP request data stream sent to the server.
The HTTP protocol has various versions identified as major.minor e.g. version 0.9, 1.0 or 1.1. The server is indicating that it is unable or unwilling to complete the request using the major version provided by the client – other than with this error message.
Assuming that your request identifies a valid major.minor version number (the request is not fundamentally corrupt), then this error should mostly only occur if you are trying to use version 1.0 or 1.1, but the Web server only supports the older 0.9 version.
Fixing 505 errors – general
Most Web browsers assume that Web servers support 1.x versions of the HTTP protocol. In practice very old versions such as 0.9 are little used nowadays, not least because they provide poorer security and performance than newer versions of the protocol. So if you see this error in your Web browser, the only option is to upgrade the Web server software. If version 1.x requests fail, it may well be because the Web server is supporting the 1.x protocol versions badly, rather than not supporting them at all.
The same arguments apply if your client is not a Web browser.
Fixing 505 errors – CheckUpDown
Our service monitors your site for HTTP errors like 505. It is our responsibility to support whatever versions of the HTTP protocol all Web servers understand. Because very old versions such as 0.9 are little used nowadays, our CheckUpDown robot uses 1.x versions of HTTP when we try to access the Web site. If these fail, it may well be because the Web server is supporting the 1.x protocol versions badly, rather than not supporting them at all.
Please contact us (email preferred) whenever you encounter 505 errors – there is nothing you can do to sort them out. We then have to analyse the underlying HTTP data streams and may have to liaise with your ISP and the vendor of the Web server software to agree how different HTTP protocol versions should be supported. In the worst case we may have to revise our program code supporting particular HTTP versions, which may take some time.
What is 506 Server Error? Variant Also Negotiates
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
Variant Also Negotiates, means that the negotiation for the server’s request results in circular references.
What is 507 Server Error? Insufficient Storage
(507) Insufficient Storage Errors are Generated when Injecting Large Attachments into Exchange 2013 Mailboxes
Synopsis
While migrating GroupWise XML files to Exchange 2013 mailboxes, large attachments fail to inject and the following error messages are generated:
Description: transaction error [add] the message exceeds the maximum supported size.
Or
Description: transaction error [add] the request failed. the remote server returned an error: (507) insufficient storage
The errors are caused by a default setting in the EWS web.config file that restricts the size of messages/attachments that can be injected.
The (507) error messages are generated when the Maximum Allowed Content Length setting (IIS Request Filtering rules) is not set to support large files.
This article will explain how to modify the configuration to allow the injection of large files and prevent ‘insufficient storage’ errors from being issued.
Solution
CAS servers have their own attachment size limits that restrict the size of messages/attachments that can be injected into Exchange mailboxes.
By default, CAS servers only accept email that has a combined attachment size of less than 64 MB, and such attachment limits are likely to be exceeded during an injection job.
When the attachment limit is exceeded during injection, (507) insufficient storage errors will be generated.
What is 508 Server Error? Resource Limit Reached
The ‘508 – Resource Limit is Reached’ error is one that leaves both website owners and people browsing the web a little bemused. In this article we focus on some tips for a website owner to be able to identify the cause and some practical remedies to this common problem amongst people using shared web hosting.
Establishing which limit is causing your ‘508 Resource Limit is Reached’ error
If you are a web site owner and you have detected that on occasion your site is issuing 508 errors to web site viewers, there are methods to identify what is the cause of the 508 errors you are experiencing. The majority of 508 errors are generated by cPanel based servers that are running Cloudlinux. The 508 error is generated by one of two things occurring on the server.
Memory usage (your account has exceeded the amount of memory allocated to your cPanel account and there is no available memory allocated to your account for the server to process your request as the memory is in use by other requests on the account)
Entry processes exceeded (your account has exceeded the amount of entry processes allowed that can be run simultaneously on the account at the time your request was sent to the web server)
Possible Causes of 508 Resource Limits being reached
There are many potential causes of the 508 error; some of the most common ones are listed below.
Your hosting provider has limits lower than the requirement of your website.
Website traffic spikes
You have rogue processes, back-end jobs or cron jobs that are impacting on your resource usage
Web Crawlers, Search Engines or Denial of Service Attacks
Poorly scripted plugins or code
What is 509 Server Error? Bandwidth Limit Exceeded
Bandwidth Limit Exceeded or Error 509 is a common error on the web space. This error means that your site is receiving too much traffic than the host can allow, depending on the server space you have purchased. Web hosting companies allocate you server space depending on your data requirements. Your website files are usually saved in a server from where they are downloaded after someone makes a query to display your website. Bandwidth Limit Exceeded or Error 509 is a common error on the web space. This error means that your site is receiving too much traffic than the host can allow, depending on the server space you have purchased. Web hosting companies allocate you server space depending on your data requirements. Your website files are usually saved in a server from where they are downloaded after someone makes a query to display your website. The more visitors your site receives, the more the bandwidth consumed.
How to fix Error 509
When your site starts displaying this error, you need to take action immediately. Here are some practical ways to fix the error permanently:
- Caching
Bandwidth is used when data is transferred from the web server to the end user’s computer and vice versa. Implementing caching ensures that when someone visits your site, a copy is saved on their browser. When they make subsequent visits, the site is retrieved from the browser instead of the host’s servers, ensuring that the allocated disk space remains intact.
- Upgrade your hosting plan
Hosting providers offer a wide range of hosting plans depending on your budget and/or bandwidth requirements. If you were on a budget when you purchased the initial hosting plan, you can consider upgrading to another plan. Your hosting provider will tell you the amount of space allocated and rates for upgrade or unlimited hosting.
- Reduce your files, especially images
Images take up a lot of disk space and reducing their size comes with many benefits. It boosts your site load speed hence boosting your SEO efforts and also optimizes disk space usage on your servers. This has a significant impact on bandwidth usage in the course of the month. If your server is always returning error 506 a few days to end month, you may need to consider optimizing your images to create space for some more downloads.In conclusion, error 509 can bring massive losses to your business. You need to constantly monitor your bandwidth usage to ensure that visitors are no met with Error 509 when they visit your site. Do not blame your host when you use up your allocated bandwidth. Collaborate with them to fix the problem as soon as possible.
What is 510 Server Error? Not Extended (RFC 2774)
The policy for accessing the resource has not been met in the request. The server should send back all the information necessary for the client to issue an extended request. It is outside the scope of this specification to specify how the extensions inform the client.
If the 510 response contains information about extensions that were not present in the initial request then the client MAY repeat the request if it has reason to believe it can fulfill the extension policy by modifying the request according to the information provided in the 510 response.
Otherwise the client MAY present any entity included in the 510 response to the user, since that entity may include relevant diagnostic information.
Search Engine Update Blog 