Browse by Popular
Domain Name
- What is a domain name?Eligibility criteria for registering .AU domain namesPremium domain names explained
Web Hosting
View All
Email Hosting
- Outlook 365 (Classic) Email Setup GuideMail app setup for iOS (iPhone + iPad)Gmail (webmail) email setup
Google Workspace
- Getting Started with Google WorkspaceGoogle Workspace support resourcesTransferring an existing Google Workspace service to VentraIP
Account
- How do I reset my VIPcontrol password?How do I create a VentraIP account?How can I see who accessed my VentraIP account?
Troubleshooting
- How do I clear my browser cache?Troubleshooting a ‘500 internal server' errorTroubleshooting with a ping test
Troubleshooting 4xx HTTP Errors
This article will go through various 4xx HTTP errors that you commonly come across, and how to troubleshoot them.
4xx errors are considered client side errors.
400 – Bad request
The server is unable to process the request due to a client error. This can be due to a few things such as a malformed request , size of the request being too large, invalid request message framing, or deceptive request routing.
Fix
To resolve this, make sure the URL is spelt correctly and doesn’t contain any encoded characters, any API calls you’re making is sent correctly. Clear your browser cache or if you are uploading a file, ensure that the file doesn’t exceed the website’s limit.
401 – Unauthorised
The error usually means that authentication is required to reach the requested resource or page, this also can simply mean “unauthenticated”
Fix
Make sure to enter the correct login details when prompted in your browser or you are sending authentication details in your request.
403 – Forbidden
This means that the request was valid, however the server refuses action. This is more typically caused by access controls, security plugins, permissions, or ModSecurity.
Fix
We have a seperate guide on how to troubleshoot 403 errors here:
404 – Not found
This usually means that the page or resource cannot be found or is not available, but could be in the future.
Fix
Make sure the resource or page is uploaded and or available, if you’re getting 404’s on only subpages and your website is WordPress, we have a guide on fixing this here
418 – I’m a Teapot
This response code is a little easter egg and tells the client that the server is a teapot and is not used to brew coffee. Mainly now, its used as an alternative of a 403.
With us, if you get this error code back, it usually means that your request is hitting a ModSecurity rule used to fight malicious bot traffic.
Fix
Please ensure that the request that you’re making contains a user agent header and ensure that you try not to make coffee in a teapot.
429 – Too many redirects
This status code indicates the browser/client has sent too many requests in a given amount of time effectively “rate limiting” the connections. This is commonly caused by a redirect loop that has been created.
Fix
To resolve, try clearing your browser’s cache and cookies, or test the site in an Incognito/Private window to see if its browser related, failing that, check your websites .htaccess file or CMS for any redirects that could be causing the loop.
Need help?
If you’re not quite sure where to look, or if you have any questions, feel free to contact our Technical Support Team via eTicket with your issue or query and we will be happy to help.
