EspoCRM Login Failing in Production

[jayaram]

Hi All,

We’re running EspoCRM (latest) in AWS ECS (Fargate).

I’d really appreciate it if the EspoCRM experts, contributors, and maintainers could kindly help review and confirm if our fix is correct or suggest a better approach.

We have two environments:

• Staging → Working fine
• Production → Login fails (browser + API)

Environment:
1. Both staging & production use the same Docker image (espocrm/espocrm:latest).
2. Aurora MySQL backend (credentials verified)

In the production environment (ECS Fargate, EspoCRM container), users were unable to log in to the CRM. The application returned “Wrong username/password”, even though credentials were confirmed correct from the database.

Impact:

1. Login requests (both browser and API) failed in production.
2. The staging environment (same image, same configuration) worked fine.
3. No new logins could be established, affecting all users.

Response:
When tested with cURL, we get a 405 Method Not Allowed error:
HTTP/2 405
Allow: GET, DELETE, PUT, PATCH
ERROR: 405 Method Not Allowed
Must be one of: GET, DELETE, PUT, PATCH
File: /var/www/html/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php

Investigation:
1. DB credentials and user password hashes verified
2. Auth method: Espo
3. No failed login limit entries


@espocrm-team @crm-experts

[item]

Hi,
i just give my experiment ..
You need clear cache browser (all) and so .. you need log off the other instance of espoCrm.

So basicly, try one instance with Firefox .. other with Google Chrome for sample.

Hope another user can help you.