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
Since we can supply a custom web port for maildev with the MAILDEV_WEB_PORT environment variable, this means that the HealthCheck will start failing because maildev is no longer listening to port 1080 for internal web traffic.
I'm wondering if the port used in the HealthCheck url should reference the environment variable instead of being hardcoded as 1080?
The text was updated successfully, but these errors were encountered:
The HealthCheck url currently seems to be hardcoded to port 1080
Since we can supply a custom web port for maildev with the
MAILDEV_WEB_PORT
environment variable, this means that the HealthCheck will start failing because maildev is no longer listening to port 1080 for internal web traffic.I'm wondering if the port used in the HealthCheck url should reference the environment variable instead of being hardcoded as 1080?
The text was updated successfully, but these errors were encountered: