You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a simple containerized microservice that runs fine locally, but fails when deployed to an EC2 environment. This only started happening with v2.5.0, and I've confirmed that there is no problem using up to v2.4.4. Every HTTP request to the service, including to the health endpoint, fails with the following message:
I am not using web sockets (so far as I know), so this message is especially confusing. I can't see anything related that changed between 2.4 and 2.5, so I've been unable to deduce any settings I might try to remedy the issue. All requests are over HTTP (not HTTPS).
Task List
Steps to reproduce provided
Stacktrace (if present) provided
Example that reproduces the problem uploaded to Github
Full description of the issue provided (see below)
Steps to Reproduce
Create a simple service. Even just one that only supports the /health endpoint should work.
Create a docker container for the packaged application.
Deploy the container to an EC2 instance.
Expected Behaviour
Any request should succeed, even just a GET to /health.
Operating System: Linux ed999e65f16f 4.14.218-aptible.0 Publish Snapshots To Artifactory #10 SMP Tue Feb 2 16:44:40 UTC 2021 x86_64 Linux (ami-05da701d18f64756f)
Micronaut Version: v.2.5.0 and higher
JDK Version: openjdk version "13.0.2" 2020-01-14
The text was updated successfully, but these errors were encountered:
I have a simple containerized microservice that runs fine locally, but fails when deployed to an EC2 environment. This only started happening with v2.5.0, and I've confirmed that there is no problem using up to v2.4.4. Every HTTP request to the service, including to the health endpoint, fails with the following message:
I am not using web sockets (so far as I know), so this message is especially confusing. I can't see anything related that changed between 2.4 and 2.5, so I've been unable to deduce any settings I might try to remedy the issue. All requests are over HTTP (not HTTPS).
Task List
Steps to Reproduce
Expected Behaviour
Any request should succeed, even just a GET to /health.
Actual Behaviour
Receive a 404 error with the following message:
Environment Information
The text was updated successfully, but these errors were encountered: