For my staging environment I’m using mailcatcher.
In my stack file I have an lb node using the tutum haproxy image, which is linked to my application and to mailcatcher in order to access to web UI.
Then my application is linked to the mailcatcher instance so that it can send emails to it.
When I try to access the mailcatcher page, I can access it, but I have some calls failing with a 502 error. For instance, while the HMTL request worked fine (200), and same for the CSS request, the JS download is failing with the 502 error.
Next try, this time the CSS wont load (502) but the JS will.
Another try and only the HTML works, or even worst, nothing work, I have 502 error on the HTML download.
Before using Docker cloud and haproxy, I was using an nginx-proxy docker image, and docker-compose in order to orchestrate the app.
I have never seen this behavior before.
Mailcatcher is using websockets, so my first though was that the WS connection is the issue. But in the end it’s not, as first step would be to have the CSS and the JS loading correctly.
Also, I tried to change the image, and here I got it working fine, but the day after I had to redeploy the instance and I got the errors again…
I have tried to add the
-v falg to the mailcatcher process, but I don’t have more logs and I don’t see anything special on the haproxy instance.
Can someone help me please ?