If someone comes across an error page on your site, there’s a good chance they’ll get annoyed and leave. This can result in plenty of lost engagement and sales. One particularly common error to be aware of is the “405 Method Not Allowed” message.
This error can be tricky to navigate, as it indicates that something has gone wrong without telling you why it occurred. Fortunately, with a little effort and patience, you can be back up and running before long.
In this post, we’ll explain what a 405 error is and show you the different ways it can appear. We’ll then talk you through some of the ways you can fix this error on your WordPress site. Let’s get to it!
Encountering the HTTP 405 “Method Not Allowed” error can be frustrating, but this issue is usually easy to resolve. This article will explain what causes the 405 status code, along with actionable solutions to get your website or application running smoothly again.
What is the HTTP 405 Error?
The 405 error occurs when the HTTP request method used is not supported for the requested page or resource. For example, a GET request is issued instead of a POST request, or vice versa.
Specifically the 405 status code means
- The requested URL exists on the server.
- The URL has valid routing configured on the server.
- But the HTTP method used in the request is not allowed for that URL.
Some common examples that trigger a 405 error:
- Submitting a form to a URL using GET instead of POST
- Accessing a URL via POST that only accepts GET
- PUTting or DELETEing a resource that is configured for different methods.
The 405 response indicates the server knows the request method cannot be handled properly It’s essentially the server rejecting unsupported HTTP verbs sent to URLs
Common Causes of the 405 Error
Here are some typical causes of the 405 status appearing:
-
Incorrect HTTP method – The client used POST but the URL requires GET, for instance.
-
Web server misconfiguration – The enabled HTTP methods don’t match the application’s needs.
-
Application flaws – The app code has bugs in request handling logic.
-
Incompatible REST API – The API endpoints don’t support the HTTP verbs the client is using.
-
Plugin conflicts – An installed plugin is conflicting with the core application methods.
-
Weak authentication – URLs that should require auth are accessible without it.
-
Cached outdated pages – Cached pages have old method requirements compared to live pages.
-
Restrictive firewall rules – Firewalls blocking the required HTTP methods can trigger 405s.
Finding the specific source of the issue takes some debugging but it’s typically one of these common factors.
How to Fix the 405 Error
Try these troubleshooting steps to fix HTTP 405 errors:
Fix 1: Double Check the URL
Often the 405 status results from trying to access the wrong URL or submitting data to the incorrect page.
- Verify the complete URL path matches an actual endpoint.
- If submitting a form, ensure the form’s action URL matches the processing page.
Sometimes a single character typo in a URL can trigger a bogus 405. Carefully check for any discrepancies.
Fix 2: Check your domain’s DNS configuration
An incorrect DNS setup can cause a 405 error, especially right after changing domains.
-
Confirm the domain name is propagating correctly and all subdomains are mapped accurately in the DNS records.
-
For WordPress sites, the DNS must be configured for www vs non-www access to avoid conflicts.
Fix 3: Fix WordPress file and folder permissions
If using WordPress, wrong filesystem permissions on directories and files can prevent proper HTTP method handling:
- Reset permissions on the /wp-admin, /wp-includes and /wp-content folders to 755.
- Set permissions on wp-config.php and other root files to 644.
- Resetting folder/file permissions often resolves 405 errors on WordPress sites after transfers or migrations.
Fix 4: Deactivate newly installed plugins and themes
Recently added plugins and themes can introduce 405 triggering conflicts:
- Temporarily deactivate new plugins and switch to a default theme like Twenty Twenty.
- If the 405 error goes away, turn plugins back on one-by-one until you identify the problematic plugin.
- Update or replace incompatible plugins or themes causing 405 conflicts.
Fix 5: Inspect the latest database changes
If the 405 started after database changes like imports or migrations, query the database:
- Check for any URL or file path issues in menus, content, or metadata.
- Compare to a known good database backup to spot problematicredirects, slugs, or links.
- Use a tool like interconnect/it to scan URLs and identify any broken links, paths, or URL issues.
Fix 6: Check your server configuration
Double check that your web server, reverse proxy, or CDN is configured properly:
- Verify the HTTP methods enabled match your application’s requirements. Enabling more methods can help.
- Inspect middleware, rewrite rules, and routing handlers for anything blocking supported verbs.
- Confirm HTTP headers and methods are passed through proxies and CDN networks appropriately.
Properly configuring the server and infrastructure prevents 405s.
How to Prevent 405 Errors
Here are some tips to avoid 405 errors going forward:
-
Carefully check URLs and form actions before launching a site. Test thoroughly.
-
Use Postman or cURL to validate that endpoints accept the expected HTTP methods.
-
Implement API request validation to catch bad requests early.
-
Make sure REST API endpoints, controllers, and routes are configured for the correct verbs.
-
Only install reputable plugins and themes that won’t conflict with core methods.
-
Monitor site error logs for potential 405 triggers and proactively resolve them.
With vigilance during development and testing, you can minimize encountering those pesky HTTP 405 errors on your live site.
405 Error Troubleshooting Recap
-
Double check all URLs are valid.
-
Verify DNS records are properly configured.
-
Set correct file and folder permissions (WordPress sites).
-
Deactivate plugins and switch themes to isolate conflicts.
-
Inspect the database for issues.
-
Check server and infrastructure configuration.
Following this 405 error troubleshooting guide should help you find and fix the source of the problem so you can get your application running smoothly again.
When to Contact Your Host or Support
If you still can’t determine the cause of the 405 after thorough debugging and troubleshooting, it’s time to engage help:
-
Managed WordPress hosts can investigate and resolve issues on their infrastructure.
-
Your web host support team may need to check the server logs or change configuration.
-
For coding issues, contact your in-house or outsourced development team.
-
API developers can ensure endpoints accept the expected HTTP methods.
With the right help, tricky 405 errors can usually be resolved quickly.
The 405 Method Not Allowed error indicates a mismatch between the HTTP request method and the URL endpoint configuration. While frustrating, a bit of targeted troubleshooting should get your web application back on track in no time. Using the tips in this guide, you can master how to fix those pesky 405 errors for good.
Roll Back Any Recent WordPress Updates
Updates are wonderful things. They typically bring a wealth of exciting new features and can help to fix any ongoing bugs and patch security holes. However, despite their good intentions, updates can occasionally cause some issues.
If you updated WordPress just before the 405 Method Not Allowed error message started to appear, the new code could be the root of the problem. This also applies to any extensions or themes you may have recently upgraded – although we’ll focus more on that aspect in the next section.
If you feel that an update might be at fault, it’s worth reverting back to the previous version of WordPress. As we’ve already touched on, make sure you have a full site backup ready before doing this – you don’t want to make any irreversible changes.
While you can do this manually, the easiest way to roll back WordPress updates is to use a plugin. There are many available options that will largely automate the process, meaning that you’re less likely to make mistakes.
Having a tool like this in your arsenal also means that you can prevent similar issues from happening in the future. Of course, if rolling back the latest update doesn’t fix the problem, remember to re-update your site or restore your backup.
Check for Any Unexpected Database Changes
Although the above step should resolve any plugin- or theme-related issues, it doesn’t guarantee that all changes made by your extensions have been fully reverted. This is especially true for many WordPress plugins. They are often given complete access to your database as soon as you hit Install, meaning that their changes go deeper than you might initially think.
Unless the developer explicitly codes against it, a plugin may be able to modify database records that don’t “belong” to it but are instead managed by WordPress itself. In this scenario, the plugin may not know how to revert those alterations to database records, so it will ignore them during the uninstallation process.
Diagnosing this particular problem can be difficult, but if you still suspect that a plugin or theme is the cause of the 405 Method Not Allowed error, checking your database directly is your best course of action. To do that, you’ll need to open your site’s database, and manually look through the tables and records modified by the extension. If you’re not sure what to look for, getting in touch with your developer is a smart idea at this point (as well as for the remaining steps on this list).
How to fix Error 405 the request Method is inappropriate for the URL
What is http 405 method not allowed error?
HTTP 405 Method Not Allowed Error means that when your browser tries visiting a webpage or API endpoint or other resource whose server handles it in a way different from what it expects, then an error message like 405 Method Not Allowed is sent back.
What is a 405 error?
The 405 error happens when a client attempts to use an HTTP method that is not allowed by the server. For example, this issue can occur when a user tries to use a method such as PUT or DELETE on a resource that only allows GET or POST requests.
What is http 405?
HTTP 405 is a status code that conveys “Method Not Allowed.” When encountered, it signifies that the server recognizes the request method but has been configured to disallow it for the targeted resource. Put, while the server understands what the client wants to do, that specific action is not permitted for the requested URL.
Why does my server return a 405 error?
The server will return a 405 error if a client tries to access a particular resource via an unsupported or improper HTTP method. This error could appear, for instance, if you attempt to update data using the GET method rather than the proper POST or PUT technique. The 405 error can arise from a web server configuration issue.
