Question

Running Docker Image on the App Platform Is Not Accessbile on the Web

Posted on May 27, 2024
DigitalOcean App Platform App Platform
Asked by Code Space

Hi, I’m trying to use the docker image as the source in the app platform but unfortunately, the app isn’t accessible on the web after the successfully deployment.

This is the image we’re running to run, dunglas/mercure - Docker Image | Docker Hub

I also added 2 environment variables which are the: MERCURE_PUBLISHER_JWT_KEY and MERCURE_SUBSCRIBER_JWT_KEY with their respective values because there was a deployment error about missing JWT. After the deployment successful, I’m still unable to access the .well-know/mercure hub.

mercure-staging-tn9qc.ondigitalocean.app

There’s no error on the logs but I get this “Upgrade-Insecure-Requests” logs.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev

Site Moderator

• June 7, 2024

Hey!

As far as I can tell from the error that you’ve shared, there are requests being made with the “Upgrade-Insecure-Requests” header. This usually means that the request is being forced to upgrade from HTTP to HTTPS.

What you could do here, is to disable the HTTPS support as this is running behind a proxy.

So based on the official documentation, HTTPS support is automatically enabled. If you run the Mercure hub behind a reverse proxy, you usually want to use unencrypted HTTP. This can be done like that:

docker run \
    -e SERVER_NAME=':80' \
    -e MERCURE_PUBLISHER_JWT_KEY='!ChangeThisMercureHubJWTSecretKey!' \
    -e MERCURE_SUBSCRIBER_JWT_KEY='!ChangeThisMercureHubJWTSecretKey!' \
    -p 80:80 \
    dunglas/mercure

In the context of the App Platform you would need to make sure that you’ve defined the SERVER_NAME=':80' env variable, and that you’ve also specified port 80 as your service port.

Let me know if this fixes the error from the logs that you’ve shared!

- Bobby