English
Magyar
Error code 500 indicates a server-side internal error: the server is unable to fulfil the request. Possible causes include incorrect settings, corrupted code, a database connection problem or server overload. Understanding website error messages helps to distinguish this from a 404 error, where the requested page cannot be found.
If you run a website, an error message may not provide much guidance at first, but it is an important indicator: the problem may be related to the request or to the server’s operation. Noting the exact error code and the page affected will help narrow down the possible causes.
The article explains the meaning of common HTTP error codes, the possible causes of 500 errors and the key points to consider when resolving them. You can also find out how to identify broken links, when it is advisable to redirect a deleted page, and how a useful 404 page can help guide visitors to other content.
Detecting 404 errors using Search Console and SEO tools
A 404 response code means that the server cannot find the requested document. When interpreting website error messages, the website therefore first examines the relevant URL and its HTTP response code. Persistent 500 errors indicate a different kind of problem: the server is unable to fulfil the request, which can impair the user experience and the site’s availability.
The NET::ERR_CERT_DATE_INVALID browser error indicates that the certificate’s expiry date is incorrect, or that the computer’s date and time are inaccurate. Check both, then verify that the website’s certificate is valid.
In your Google Search Console reports, locate the affected pages and the URLs returning a 404 error. Then open the relevant URL and check whether the error is caused by a typo, a changed path or deleted content. Also check your internal links: an old menu item or article link may direct visitors to a page that no longer exists.
SEO tools crawl a website’s links and response codes. Screaming Frog SEO Spider, Ahrefs Site Audit and SEMrush Site Audit, for example, can also identify URLs returning a 500 error. Compare the results URL by URL with the data from Search Console, then either fix the broken internal link or set up a 301 redirect if there is a relevant replacement page.
A 500 error on a visitor’s page can interrupt their browsing experience, for example when opening an article or a form. If the problem persists, Google may temporarily or permanently remove the affected pages from its index. Therefore, when rectifying the issue, prioritise important pages and those with many internal links pointing to them.
If you’re experiencing CMS or PHP issues, check for updates, plugins and the server log. An out-of-date CMS or an incompatible plugin can cause a 500 error. In the case of WordPress, deactivate all plugins and then reactivate them one by one; this will help you identify the element causing the error. PHP version 7.2 or earlier is considered outdated; in such environments, it is recommended to upgrade to PHP version 8.0 or 8.1. For Apache, the /var/log/apache2/error.log file, and for Nginx, the /var/log/nginx/error.log file, can help identify the cause of the error.
Check the links on your website on a monthly basis to ensure that broken links do not go unnoticed. Contact your hosting provider if you haven’t modified any content, but an important URL continues to return a 404 error. It is advisable to seek assistance from your hosting provider if several pages are returning a 500 error, or if the server logs indicate configuration, database or resource issues.
By re-enabling your WordPress plugins one by one, you can identify which one is causing the error. Check the page after each re-enable; this will allow you to narrow down the possible causes step by step and tailor the fix to the problematic plugin.
404 pages and redirecting visitors
Your custom 404 page appears when a visitor tries to access a URL for which no document is available. In the case of a hard 404 error, the server sends a 404 response code and the website’s error page is displayed in the browser. This page should do more than simply state that the content cannot be found: it should help the visitor to continue browsing.
A well-designed 404 page briefly explains the error and then offers specific options for what to do next. Include a search box or recommended content and products on the page. For example, if someone mistypes the title of an older blog post, the search function can help them find the updated version of the post. A link back to the homepage can also be useful, but it shouldn’t be the only option provided.
Do not automatically redirect non-existent URLs to the homepage. In such cases, the server may send a 200 status code, whilst the visitor sees an error page. This results in a ‘soft 404’ error, as the status code indicates a successful load, but the content cannot be found. A page that has actually been deleted should receive a 404 response, or be redirected to an appropriate replacement page, if one exists.
Assess the performance of your 404 page based on the visitor’s journey. 36 per cent of visitors landing on a non-existent page click the browser’s back button. Therefore, ensure the search bar, main navigation and key categories are clearly visible. For example, on an online shop’s error page, a recommendation for the relevant product category may be more useful than a general link to the homepage.
The design of the error page should match the rest of the website. Retain the header, navigation and branding elements so that visitors know they are still on the same website. The error message should be easy to understand, and the search box should accept product names, article titles or topics. Test the page by opening a non-existent URL and check the response code as well.
The title and description that appear in search results, as well as the H1 heading visible on the page, each serve a specific purpose. Every page should have a unique title and meta description, whilst the H1 heading should clearly state the page’s topic. On a 404 page, for example, the H1 heading might state that the page being searched for cannot be found, whilst the description might suggest using a search engine or the site’s navigation.
- Page title: give a concise description of the page’s content.
- Meta description: summarises what visitors will find on the page.
- H1 heading: should appear as a single main heading and describe the topic of the page.
- 404 page: provide specific options for searching or moving on.
If an internal link still points to an old address, correct the link on the original page. This way, visitors won’t keep encountering the same error, and the 404 page will only appear for addresses that have genuinely been removed or were entered incorrectly.
301 redirects and fixing broken links
A 301 redirect can be used when there is a relevant replacement for a deleted page. In this case, the browser is taken to the new address, and the server indicates that the redirect is permanent. This is different from the 302 HTTP status code, which indicates a temporary redirect. The 3xx group of HTTP status codes generally indicates a redirect.
First, find out why the original link isn’t working. Open the URL in question, then check whether the error is caused by a typo, a changed address or deleted content. If only the page’s address has changed, update the internal link to the new address. If a link to an external website is no longer valid, find a working destination page on the same topic.
When redirecting, the new page must offer a relevant alternative. For example, the product page for a discontinued product could be redirected to a genuinely related product category. Do not automatically redirect every incorrect URL to the homepage. If the content of the new destination does not match that of the old page, the visitor will not find what they are looking for.
Assign the redirect rule to the relevant route, then check the result. Open the old URL in your browser and check that the correct new page loads. Then test the new address directly as well. If it redirects to yet another address, review the rules and remove any unnecessary steps.
When fixing broken links, don’t just change the redirect rule. Find the page containing the old link and update the destination URL. Check the navigation, footer, articles and sitemap as well. This ensures that visitors and web crawlers are taken directly to the correct page.
- Typo: please correct the address in the link.
- Moved content: please update the internal link or set up a 301 redirect.
- Page permanently deleted with no replacement: let the server return a 404 response.
- Temporarily moved content: please use a temporary redirect appropriate to the situation.
Even after reorganising your content, be sure to check your links. Changing a menu item can leave broken links on several subpages. Once you’ve made the correction, review the affected pages, the response code and whether the content of the new destination matches the old one. This will help you distinguish between a broken link and a problem caused by a deleted page.
When modifying redirect rules, check the configuration carefully and do not automatically assume that an incorrect response is due to a content issue. An incorrect setting or typo in a faulty .htaccess file can cause a 500 error. Therefore, after saving the rule, check the relevant URL, and if an error appears, review the newly modified setting. It is worth keeping your rules organised so that a specific redirect can be easily identified. During testing, also ensure that the correction does not affect the behaviour of other routes. If you have modified several rules, check the affected URLs individually; this makes it easier to determine which setting requires further correction.
It is not recommended to automatically redirect URLs pointing to a 404 error page to the homepage, as this can cause a ‘soft 404’ error. First, examine such a URL based on its content and purpose. If there is no relevant, related replacement page, do not set a destination that does not provide an answer to what the visitor was looking for. After making the correction, try accessing the old URL and check that the result matches the actual state of the content. Review the rules from time to time, particularly when you delete or reorganise pages. This will prevent a previously correct setting from later leading to a misleading destination page.
The role of HTTP codes in troubleshooting and redirection
The HTTP status code indicates how the server handled the browser’s request. They can be categorised into five groups based on their first digit: 1xx, 2xx, 3xx, 4xx and 5xx. When troubleshooting, first check which code is displayed. Then check whether the problem affects a single URL or multiple pages.
1xx codes are informational responses. An HTTP status code of 100 indicates that the client may proceed with the request. The HTTP status code 101 indicates a protocol switch. The HTTP status code 102 indicates that the server has received and is processing the request. These are not the same as a response indicating that a web page is ready.
2xx codes indicate a successful request, such as the 200 OK response. The 201 HTTP status code indicates that a resource has been created. The 202 HTTP status code indicates a request that has been accepted but not yet completed. The HTTP status code 204 indicates a successful request with no response message. The 205 response requests that the document view be reset, whilst 206 indicates partial content.
The 3xx group indicates a redirect. A 301 response indicates a permanent redirect, whilst a 302 HTTP status code indicates a temporary redirect. The 303 HTTP status code directs the user to a resource located at a different URL. When troubleshooting, check the destination address and the redirect chain. If one address redirects to several further addresses, the browser may eventually end up on the wrong page or be unable to load the content.
4xx codes indicate client-side errors, whilst 5xx codes indicate server-side errors. The 400 HTTP status code indicates an incorrect or invalid request. The 401 response indicates an authentication issue, whilst the 403 response indicates an authorisation issue. A 404 code means the document cannot be found, whilst a 410 code indicates that the resource has been permanently removed. A 500 code indicates an internal server error.
In the case of a 502 Bad Gateway, a 503 Service Unavailable or a 504 Gateway Timeout, some sort of server-side or inter-server problem is preventing the request from being fulfilled. A 502 error may indicate a communication fault, a 503 indicates that the service is temporarily unavailable, whilst a 504 indicates that the intermediary server did not receive a response in time.
- 502: Check the connection between the servers.
- 503: Check that the server is available and not undergoing maintenance.
- 504: find out which server or background process is causing the delay in the response.
Once you have interpreted the code, compare the affected URL with a working page. If only one URL is faulty, check its request and settings. If several pages return a 5xx error code, check the server logs and background processes. After rectifying the issue, request the same URL again and check whether the browser is now receiving the correct response.
Possible causes and solutions for error messages
Alongside the error code, make a note of the affected URL, the time the error occurred and any changes made prior to it. This information will help you distinguish between browser, website and server issues.
What the 400 Bad Request error means and how to fix it
An HTTP status code in the 400 range indicates that the server is unable to process the request because it is incorrect or invalid. First, check the URL, then try opening the page again. If the error only occurs in one browser, clear the cookies for that particular website and try again.
When submitting the form, please check that you have filled in all the required fields correctly. If the same response appears in another browser, please note down the exact address and the action you took. This information will help the operator investigate how the system processed your request.
The 401 Unauthorised and 403 Forbidden errors
HTTP status code 401 indicates missing or invalid authentication details. Code 403 indicates that the account used for the request does not have permission to access the content in question. Therefore, for a 401 error, check your login details; for a 403 error, check the access rights assigned to the account.
If you manage the website, check the relevant user role and the site’s access settings. Do not include passwords or access tokens in error reports. If you share logs with the operator, remove any credentials and personal data from them first.
DNS, connection and timeout errors
A DNS error indicates that the browser cannot resolve the domain name, whilst a connection error means that a connection to the server cannot be established. A timeout occurs when a response is not received in time. If only one website is affected, check the domain name and then try accessing it from a different network.
If several websites are unavailable, check your device’s network connection. If only your own domain isn’t loading, make a note of the exact error message displayed by your browser and the affected URL. These details will help you distinguish between a DNS resolution issue and a server outage.
Troubleshooting steps for website errors
Start troubleshooting by noting down the affected URL, the response code and the time the error occurred. Then try opening the page in a different browser, and check whether any other pages are also affected. If the error appeared after an update, examine the most recent change and test reverting it.
If you’re experiencing error code 500, check the server logs, the PHP code, the .htaccess settings and the database connection. Ensure that only authorised persons have access to the logs; do not disclose login details, session IDs or personal data. Redact sensitive sections before sharing, and do not send the entire log file if the relevant error details are sufficient.
If you need to identify the cause of the error by checking logs or settings, the hosting troubleshooting guides can help you choose which checks to carry out next. The error report sent to the provider should include the URL, the response code and the time, but should not contain any passwords or other confidential information.
aWh: Web hosting
aWh offers web hosting to those looking for hosting to run their websites. If recurring 503 or 500 errors are server-side, examining the logs and the affected URLs will help determine whether the issue lies with the website’s code, its configuration or the hosting environment. Based on this, the next troubleshooting step can be identified more precisely.
The right solution depends on the type of hosting and resources you need to run your website. Web hosting may be suitable for simpler websites, whilst KVM VPS is an option for environments requiring greater flexibility. Domain registration and Windows VPS are also available.
Take a look at aWh’s web hosting services, or get in touch with aWh.
Establish a clear troubleshooting process
Interpreting website error messages helps with decision-making when an operational routine is established based on experience. Make a note of when the error occurs, which functions it affects, and what changes preceded it. This way, the next investigation can be based on specific precedents rather than guesswork. As well as keeping updates and configuration changes up to date, ensure that your backups are also up to date so that you can restore the system to a previous state following any incorrect changes.
If the recurring error is server-side, choosing the right hosting environment may also be part of the solution. aWh offers web hosting, KVM VPS and domain registration, so you can find a solution to suit a range of website and operational requirements. The exact nature of the error and the website’s operational requirements will help you determine the next steps.
If you need support with the next step, ask the aWh team for help. With well-organised error logs, you too can keep your website running more reliably.
Frequently asked questions about website errors
Error Code 500: What does it mean and how can it be resolved on a website?
Error code 500 indicates an internal server error, so start by checking the server-side operations. If the error appeared after an update, revert to the last change and then check the page again. Make a note of the affected URL and the time the error occurred. If only one feature is faulty, such as the contact form, check its code and database connection first.
What are the possible causes of a 500 error code?
A 500 error can be caused by incorrect server settings, corrupted PHP code, database connection issues or a lack of resources. When using a CMS, incompatibility between an updated plugin and the existing system is also a possibility. Note whether the error began after an installation and whether it also affects the admin panel. Identifying the timing of the issue can help narrow down the changes to investigate.
How can you identify 404 errors?
Identify 404 pages by comparing the results obtained during website crawling with the landing pages visited by users. Also check the sitemap: it should not contain any URLs that no longer serve content. Then look for internal links pointing to the affected URL. Links appearing in the navigation bar, footer or frequently visited articles are particularly important.
How can you identify URLs returning a 500 error?
Run a website crawl, then filter out the URLs returning a 500 status code. Group the results by path or page type: if several product pages follow the same pattern, a shared template or database query may be affected. Compare the errors with the crawl times using the dates in the server logs. This will help you distinguish between persistent errors and one-off response issues.
What are the potential drawbacks of a 404 error?
A 404 error can interrupt a visitor’s journey, for example, before they reach a product description or an important information page. If an internal link leads there, the website’s own navigation may also appear to be faulty. Search engine bots cannot access the content either, so check whether the page has actually been deleted. If the URL has simply changed, restore the link to the correct new page.
What could be the solution if you get an ‘error 404’?
First, check the URL, as even a single typo can result in a ‘404 error’ message. If the content has been moved, update the old links or redirect the URL to the new page that is actually relevant. If the page has been permanently removed and there is no suitable replacement content, do not send the visitor to an unrelated page. The website’s search function can help visitors find relevant content.
What are the most common website error messages?
Common error codes include 400, 401, 403, 404 and 500, as well as 502, 503 and 504. A 400 indicates an invalid request, a 401 requests authentication details, a 403 denies access, and a 404 means the content cannot be found. 5xx codes indicate a server-side issue. Alongside the exact code, make a note of which page it appeared on and following which action.
When should you ask for help?
Please seek assistance if several pages consistently return a 5xx error, the log indicates a server or database error, or if you are unable to make changes to the settings due to insufficient permissions. In the case of a single broken link, the website operator can first correct the content or the URL. If the server’s response is incorrect, forward the relevant URL, the response code and the time of the error to your hosting provider.