• URL syntax error caused by incorrect spelling in the URL or the use of illegal characters
• Expired or corrupted browser cookies or cache files could be causing the issue

• Generic server errors such as misconfiguration or faulty programing

* How to correct error code 400: *

• Refreshing the page can resolve a temporary issue
• Check for spelling and the use of illegal characters can provide a proper connection

• Clearing your browser’s cookies and cache files can sometimes resolve the issue

403: Forbidden

• The server’s file permissions are dictated in a way that does not allow the user to access the content
• Sometimes htaccess files can restrict access improperly
• Trying to access a URL that is not available or restricted

* How to correct error code 403: *

• Similar to correcting a 400 error, refreshing the page can fix a momentary issue
• Clearing your browser’s cookies and cache files can fix the error if it comes from a corrupted cache
• Check to make sure that the file permissions on the server are correctly set to allow access to authorized users

404: Not Found

• A broken link by means of incorrect or outdated information or if the page has been moved without updating the link
• The URL entered in the browser is incorrect due to a typo or wrong spelling
• The page was deleted, moved, or renamed without proper redirection

* How to correct error code 404: *

• Sometimes the page might load after refreshing the browser or trying the URL again, just like before
• Make sure the URL is typed correctly and if it’s a link, verify that it points to the right address
• Move up one directory level in the URL to see if there’s a higher-level page that works to help you navigate to the information you’re looking for

408: Request Timeout

• Slow internet speeds can cause requests to stall and timeout
• Very large requests with a lot of data can take a long time to process which can leading to timeouts
• An overloaded server may be slow to respond to requests and will timeout

* How to correct error code 408: *

• Call AT&T (Just kidding)
• Check your connectivity, change networks, or restart your devices
• Increase your request timeout limit on your web server to give requests more time to complete before timing out
• Optimize database queries that return results too slowly to prevent them from causing timeouts

500: Internal Server Error

• Problems with the server-side code, such as syntax errors in .NET (C#), PHP, Python, or Ruby scripts
• The web application is unable to connect to its database due to incorrect credentials, corrupted database, or network problems
• The server runs out of resources like CPU, memory, or disk space, which can happen if the server is overloaded or misconfigured

* How to correct error code 500: *

• Hire better programmers (Just kidding again, or am I?)
• If the issue is temporary, once again a simple refresh can re-establish a successful connection
• Corrupted cache or cookies can cause persistent issues, so clearing them might resolve the error
• If the problem persists, reaching out to the website’s support team can help as they can troubleshoot and fix the issue from the server side

502: Bad Gateway

• The server could get overloaded which means that it’ll runs out of resources. This could be because of an unexpected spike in traffic or low memory
• Network issues like DNS issues, that’s when the URL that a person can read (www.foo.com) doesn’t translate properly to the corresponding IP address (192.0.2.44), or a server being down
• Firewall blocks and trouble with the proxy can prevent proper communication between servers

* How to correct error code 502: *

• As usual, number one correction method is simply to refresh the page to eliminate the possibility of a momentary issue.
• Ensure that DNS settings are correct and that the firewall isn’t incorrectly blocking the server
• Clear the browser cache to dispose of corrupted files that may be lingering

503: Service Unavailable

• A high volume of requests being sent to the server that exhausts all the available resources
• The server is going through maintenance work
• The server could be under a Distributed Denial of Service (DDoS) attack which is where a high volume of requests by bots overwhelm the system

* How to correct error code 503: *

• Refreshing the system and restarting the page is still the number one way to fix the error, simply because it could very well be a momentary issue
• Restarting your router, modem, and computer can help, especially if there’s a DNS Failure error
• Check if the web server is going down for maintenance and wait for it to be completed

Justin Tadros is a Project Manager and Data Analyst at The Training Boss. Justin has a bachelor degree in Theater performance from Rollins College and currently pursuing his Masters in business at the University of Center Florida.  Justin is certified on Microsoft Power BI and Progress Sitefinity Sales accreditation with on going training on Python and CMS technologies.  Justin performs in theaters in Orlando, Boston, Alaska and stand up comic whenever the opportunity arises.  His passion for performing and bringing incredible customer service to any industry he approaches is second to his commitment, dedication and hard work.