Environment:
Outlook OAuth token requests return:
HTTP/1.1 404 NotFound
This affects all Outlook-connected mailboxes and calendar sync.
Testing shows:
VPS host request -> 200 OK
Fresh curl container on same Docker network -> 200 OK
EspoCRM container using default TLS -> 404 NotFound
EspoCRM container capped to TLS 1.2 -> 200 OK
The same behaviour occurs against both the tenant-specific and organizations Microsoft endpoints. The client ID, secret, redirect URI and admin consent are valid.
This appears to be a TLS 1.3 interoperability issue in the current official container runtime. Forcing PHP cURL to TLS 1.2 resolves the Microsoft endpoint request. Has anyone else encountered this, and is a rebuilt image or supported workaround planned?
- EspoCRM 10.0.2
- Official image: espocrm/espocrm:10.0.2
- Debian 13.5
- PHP 8.4.23
- cURL 8.14.1
- OpenSSL 3.5.6
Outlook OAuth token requests return:
HTTP/1.1 404 NotFound
This affects all Outlook-connected mailboxes and calendar sync.
Testing shows:
VPS host request -> 200 OK
Fresh curl container on same Docker network -> 200 OK
EspoCRM container using default TLS -> 404 NotFound
EspoCRM container capped to TLS 1.2 -> 200 OK
The same behaviour occurs against both the tenant-specific and organizations Microsoft endpoints. The client ID, secret, redirect URI and admin consent are valid.
This appears to be a TLS 1.3 interoperability issue in the current official container runtime. Forcing PHP cURL to TLS 1.2 resolves the Microsoft endpoint request. Has anyone else encountered this, and is a rebuilt image or supported workaround planned?