---
title: "HTTP 405 Method Not Allowed — What It Means & How to Fix It"
description: "HTTP 405 Method Not Allowed: The HTTP method used in the request (GET, POST, PUT, DELETE, etc. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/405
---

# HTTP 405 Method Not Allowed

The HTTP method used in the request (GET, POST, PUT, DELETE, etc.) is not supported for the target resource. The server knows the resource exists but rejects the specific method.

## What does HTTP 405 mean?

The HTTP method used in the request (GET, POST, PUT, DELETE, etc.) is not supported for the target resource. The server knows the resource exists but rejects the specific method.

## Common causes

1. 1  
Sending a POST request to an endpoint that only accepts GET, or vice versa. The API supports the URL but not with that method.
2. 2  
A form submission uses GET instead of POST, or the frontend sends the wrong method due to a misconfigured fetch/axios call.
3. 3  
The server or framework has CORS preflight (OPTIONS) misconfigured, and the actual request method is being rejected.

## How to fix it

1. 1  
Check the Allow header in the response — it lists which HTTP methods the endpoint accepts. Switch to a supported method.
2. 2  
Review your API documentation to confirm the correct method for each endpoint. REST conventions: GET to read, POST to create, PUT/PATCH to update, DELETE to remove.
3. 3  
If OPTIONS requests fail, ensure your server handles CORS preflight correctly and lists the required methods in Access-Control-Allow-Methods.

## Monitor for HTTP 405 errors

Uptrack sends GET requests by default to check endpoint availability. If your health check endpoint only accepts POST, configure the monitor with the correct HTTP method to avoid false 405 alerts.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 200 OK](https://uptrack.app/http/200)
