Seeing a 405 Method Not Allowed error? Learn what causes it and how to fix it fast, whether you’re browsing a site or building an API.
You submit a form, refresh a page, or call an API, and instead of the response you expected, you get “405 Method Not Allowed.” The page clearly exists. The server clearly knows what you’re asking. It just won’t let you ask for it that way.
Here’s the short version: a 405 error means the server understood exactly which action you were trying to perform, but that particular action isn’t allowed on that particular page or endpoint. It’s less about who you are or what you have permission to see, and more about how you’re trying to interact with something.
This error shows up for regular visitors after refreshing a submitted form or clicking a stale bookmark, and it shows up constantly for developers building or testing APIs. In this guide, you’ll learn what causes a 405 method not allowed error, how to fix it depending on whether you’re a visitor or someone managing a site or API, and how it fits alongside similar codes like 400, 403, and 404.
What Is a 405 Method Not Allowed Error?
A 405 method not allowed error means the server recognizes the type of request you sent, but has decided that specific type isn’t permitted for the page or resource you’re targeting. To understand this, it helps to know that every request carries an action label, called an HTTP method, that tells the server what you want to do.
The most common ones are GET, which asks the server to hand over information, and POST, which sends information to the server, often from a form. There are others too, like PUT for updating something and DELETE for removing it.
A server can be set up to allow only certain methods on a given page, and if your request arrives using one that isn’t on the approved list, you get a 405 instead of the result you wanted.
This is different from a 404, where the page simply doesn’t exist, and different from a 403, where access is blocked outright. With a 405, the resource is right there, and the server is even willing to interact with it, just not in the way your request is asking for.
What Causes a 405 Method Not Allowed Error?
A handful of situations tend to cause this 405 method not allowed error far more often than others.
Using the Wrong HTTP Method for a Page or Endpoint
The most frequent cause is a straightforward mismatch. If a page or API endpoint is only built to accept GET requests, and something sends it a POST, PUT, or DELETE instead, the server rejects it with a 405.
Resubmitting a Form After Refreshing
When you submit a form and then refresh the resulting page, your browser sometimes tries to resend the exact same request, including the method that was used. If that page no longer accepts that method, you’ll see a 405 instead of the form going through again.
Server Configuration Restricting Allowed Methods
Web server software often lets administrators explicitly define which methods are allowed for a given folder or route. If that configuration is too restrictive, or was set up incorrectly, it can block legitimate requests that should otherwise work.
Incorrect .htaccess Rules
On servers running Apache, a configuration file called .htaccess can include directives that limit which methods are permitted. An overly strict or mistakenly written rule in this file is one of the most common sources of unexpected 405 errors.
Application Routing Issues
Modern websites and APIs are often built with frameworks that define which methods each specific route supports. If a route is only coded to handle one method, any other method sent to that same address will be turned away with a 405.
Outdated Browser Cache or Cached Server Responses
Sometimes a browser or an intermediary cache holds onto an old version of how a page used to behave. If the server’s accepted methods have changed since that data was cached, a stale copy of the previous rules can produce a 405 METHOD NOT ALLOWED that no longer matches reality.
Web Application Firewall or Security Filters
Security tools sitting in front of a website or API sometimes block certain methods outright, particularly less common ones like PUT, DELETE, or TRACE, as a precaution. This can trigger a 405 even for requests that would otherwise be perfectly valid.
CMS or Plugin Conflicts
On platforms like WordPress, a plugin, theme, or core update can change how certain requests are expected to be formatted. This occasionally causes actions like comment submissions or login attempts to be rejected with a 405 METHOD NOT ALLOWED after an update.
Incorrect or Mismatched API Documentation
Sometimes the cause isn’t a bug at all. A developer may simply be using a method that the API’s documentation described incorrectly, or that changed in a newer version without being clearly communicated.
How to Fix a 405 Method Not Allowed Error
For Website Visitors
Try these steps first, in order:
- Avoid resubmitting the page. If the error appeared after a refresh, go back and navigate to the page fresh instead of resending the same form data.
- Clear your browser cache and cookies. This removes any outdated stored data that might be causing your browser to repeat an old request incorrectly.
- Try a different browser or device. This helps confirm whether the issue is tied to your specific setup.
- Check the URL you’re using. Make sure you followed a current link rather than an old bookmark that might point to a page whose behavior has since changed.
- Wait and try again later. If a recent site update caused the issue, it may be resolved once the site owner notices and fixes it.
- Contact the website. If the error keeps happening on an action that should work, like submitting a contact form, let the site owner know so they can investigate.
Tip: If the error only happens after a refresh, it’s very likely tied to your browser trying to resend a form submission, not a deeper problem with the site.
For Website Owners and Developers
If your site or API is producing 405 errors for requests that should be valid, work through this list:
- Check the Allow header in the response. Servers are required to list which methods are actually supported for that resource, which tells you immediately what’s permitted.
- Confirm your route or endpoint definitions. Make sure the method you’re expecting to use is explicitly coded to be accepted by that specific route.
- Review your .htaccess or server configuration file. Look for method restrictions or rewrite rules that may be blocking a method that should be allowed.
- Test with an OPTIONS request. Sending this type of request to an endpoint often returns a list of currently accepted methods, which helps you compare expectations against reality.
- Roll back recent plugin, theme, or CMS updates. If the error started right after an update, temporarily reverting it can confirm whether that update introduced the restriction.
- Review firewall and security filter settings. Check whether a security tool is blocking a method your application genuinely needs.
- Check server and application logs. Logs often show exactly which request came in and why it was rejected, saving time compared to guessing.
- Contact your hosting provider if necessary. If you don’t have direct access to server configuration files, your host can review settings you can’t see from your side.
Common 405 Method Not Allowed Messages
The exact wording can vary depending on the browser, server, or platform, but they all point to the same underlying mismatch:
- 405 Method Not Allowed – the standard version of this status code.
- HTTP Error 405 – the same error, referenced by its numeric code.
- 405 Not Allowed – a shortened version some servers display.
- Method Not Allowed: The requested method is not supported for this resource – a more descriptive explanation some platforms use.
- 405 Method Not Allowed (nginx) – points to Nginx specifically as the server enforcing the restriction.
405 vs 400 vs 403 vs 404 Errors
These codes all fall under client side errors, but each one signals a different kind of problem.
| Code | Meaning | Typical Cause | Who Usually Fixes It |
|---|---|---|---|
| 400 | Bad Request | The request itself is malformed or invalid | Visitor (request details) or site owner (server rules) |
| 403 | Forbidden | A rule or permission blocks access to a resource that exists | Site owner or server administrator |
| 404 | Not Found | The page or resource doesn’t exist at that address | Site owner or content editor |
| 405 | Method Not Allowed | The resource exists, but the method used isn’t supported there | Site owner or developer |
Frequently Asked Questions
Is a 405 Method Not Allowed error my fault? Sometimes, particularly if you resubmitted a form after a refresh or followed an old link. Just as often, it comes from a server configuration or coding issue that has nothing to do with anything you did.
Can I fix a 405 Method Not Allowed error? As a visitor, you can often work around it by avoiding a form resubmission, clearing your cache, or navigating to the page fresh. If the restriction is on the server, only the site owner or developer can permanently resolve it.
What is the difference between 405 and 403? A 403 blocks access to a resource no matter how you ask for it. A 405 means the resource is accessible, but the specific method your request used isn’t one of the accepted options.
Does a 405 error mean the website is down? No. The server is working and responding to you directly. It’s specifically rejecting the method your request used, while the rest of the site can continue functioning normally.
Why am I getting a 405 Method Not Allowed error? It’s usually caused by resubmitting a form, using an outdated link, or, on the server side, a configuration or routing rule that doesn’t allow the method being used for that resource.
Does clearing cache fix a 405 error? Sometimes, especially if your browser was holding onto an outdated request or cached page behavior. It won’t help if the restriction is a deliberate, current server setting.
Can a firewall cause a 405 Method Not Allowed error? Yes. Security tools and web application firewalls sometimes block certain methods, like PUT or DELETE, as a precaution, which can produce a 405 even for a legitimate request.
What should website owners check first? Start with the Allow header in the server’s response. It directly lists which methods are currently accepted, which narrows down the mismatch immediately.
Is a 405 error the same as a 404 error? No. A 404 means the resource doesn’t exist at all. A 405 means the resource does exist, but the method used to request it isn’t supported there.
Final Thoughts
A 405 Method Not Allowed error sounds technical, but it comes down to something simple: the resource you’re after is real, and the server is willing to work with it, just not through the specific method your request used.
If you’re a visitor, avoid resubmitting forms after a refresh, clear your cache, and try navigating to the page fresh before assuming something bigger is wrong.
If you manage the website or the API behind it, check the Allow header first, then work through your routing rules, server configuration, and any security filters that might be restricting a method your application actually needs. A 405 error is usually a quick fix once you line up the method being used with the one the server is expecting.