404 Error with Mercure public link #60119

Asmitta-01 · 2025-04-02T11:11:24Z

Asmitta-01
Apr 2, 2025

I use Symfony UX and i followed this to implement a chat using mercure in my app: https://symfony.com/bundles/ux-turbo/current/index.html#sending-async-changes-using-mercure-a-chat. My config:

###> symfony/mercure-bundle ###
# The URL of the Mercure hub, used by the app to publish updates (can be a local URL)
MERCURE_URL=https://127.0.0.1:8800/.well-known/mercure
MERCURE_PUBLIC_URL=https://127.0.0.1:8800/.well-known/mercure
MERCURE_JWT_SECRET="sIsF/hvg/Z4Yu0N9VNboDc1Aro1i2Pondk1FkHFsUr8="
###< symfony/mercure-bundle ###

But i have a 404 error when i open the mercure link: https://127.0.0.1:8800/.well-known/mercure.
Here is my compose.yaml:

  mercure:
    image: dunglas/mercure
    restart: unless-stopped
    environment:
      # Uncomment the following line to disable HTTPS,
      #SERVER_NAME: ':80'
      MERCURE_PUBLISHER_JWT_KEY: 'sIsF/hvg/Z4Yu0N9VNboDc1Aro1i2Pondk1FkHFsUr8='
      MERCURE_SUBSCRIBER_JWT_KEY: 'sIsF/hvg/Z4Yu0N9VNboDc1Aro1i2Pondk1FkHFsUr8='
      # Set the URL of your Symfony project (without trailing slash!) as value of the cors_origins directive
      MERCURE_EXTRA_DIRECTIVES: |
        cors_origins https://127.0.0.1:8800
    # Comment the following line to disable the development mode
    command: /usr/bin/caddy run --config /etc/caddy/dev.Caddyfile
    healthcheck:
      test: [ "CMD", "curl", "-f", "https://localhost/healthz" ]
      timeout: 5s
      retries: 5
      start_period: 60s
    volumes:
      - mercure_data:/data
      - mercure_config:/config
###< symfony/mercure-bundle ###

And my docker logs:

2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.484836,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":3622020710,"previous":9223372036854775807}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.4874907,"msg":"using config from file","file":"/etc/caddy/dev.Caddyfile"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.4901364,"msg":"adapted config to JSON","adapter":"caddyfile"}
2025-04-01 12:10:23 mercure-1  | {"level":"warn","ts":1743502223.4901993,"msg":"Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies","adapter":"caddyfile","file":"/etc/caddy/dev.Caddyfile","line":6}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.495413,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//[::1]:2019","//127.0.0.1:2019","//localhost:2019"]}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.4956708,"logger":"http.auto_https","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.4957626,"logger":"http.auto_https","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.4960418,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00075a480"}
2025-04-01 12:10:23 mercure-1  | {"level":"warn","ts":1743502223.5079937,"logger":"pki.ca.local","msg":"installing root certificate (you might be prompted for password)","path":"storage:pki/authorities/local/root.crt"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.5112717,"msg":"warning: \"certutil\" is not available, install \"certutil\" with \"apt install libnss3-tools\" or \"yum install nss-tools\" and try again"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.5113342,"msg":"define JAVA_HOME environment variable to use the Java trust"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.5152311,"logger":"tls","msg":"storage cleaning happened too recently; skipping for now","storage":"FileStorage:/data/caddy","instance":"2b849cd0-fd72-411b-b196-9eb643d788ec","try_again":1743588623.5152261,"try_again_in":86399.9999993}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.515562,"logger":"tls","msg":"finished cleaning storage units"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.6227891,"msg":"certificate installed properly in linux trusts"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.624046,"logger":"http","msg":"enabling HTTP/3 listener","addr":":443"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.6242604,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details."}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.6245792,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
2025-04-01 12:10:23 mercure-1  | {"level":"warn","ts":1743502223.624839,"logger":"http","msg":"HTTP/2 skipped because it requires TLS","network":"tcp","addr":":80"}
2025-04-01 12:10:23 mercure-1  | {"level":"warn","ts":1743502223.6249208,"logger":"http","msg":"HTTP/3 skipped because it requires TLS","network":"tcp","addr":":80"}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.6249309,"logger":"http.log","msg":"server running","name":"remaining_auto_https_redirects","protocols":["h1","h2","h3"]}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.6249385,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["localhost"]}
2025-04-01 12:10:23 mercure-1  | {"level":"info","ts":1743502223.6271732,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}

My project is on https://127.0.0.1:8800, i run it with symfony serve --port=8800. Do you know why i have that issue please ?

Answered by Asmitta-01

Apr 3, 2025

I reverted back all my changes then followed this course: https://symfonycasts.com/screencast/turbo/mercure (Chapter 47-52).
It works now.

Comparing changes, it seems that i should have juste uncomment the #SERVER_NAME: ':80' line in the compose.yaml. And the mercure port is random, so each time if i want to access i should do try http://127.0.0.1:<random_port>/.well-known/mercure. We can get the port with the command:

 symfony var:export --multiline | grep MERCURE

View full answer

MatTheCat · 2025-04-02T15:25:11Z

MatTheCat
Apr 2, 2025

I think the public URL is supposed to be the hub’s, not your app’s. Don’t you have a docker-compose.override.yml or something similar to publish your mercure service’s ports?

6 replies

MatTheCat Apr 2, 2025

If I refer to https://symfony.com/doc/current/setup/symfony_server.html#docker-integration MERCURE_URL and MERCURE_PUBLIC_URL should automatically be created so you don’t need to populate them.

Asmitta-01 Apr 2, 2025
Author

The env file by default:

###> symfony/mercure-bundle ###
# See https://symfony.com/doc/current/mercure.html#configuration
# The URL of the Mercure hub, used by the app to publish updates (can be a local URL)
MERCURE_URL=https://example.com/.well-known/mercure
# The public URL of the Mercure hub, used by the browser to connect
MERCURE_PUBLIC_URL=https://example.com/.well-known/mercure
# The secret used to sign the JWTs
MERCURE_JWT_SECRET="!ChangeThisMercureHubJWTSecretKey!"
###< symfony/mercure-bundle ###

So i should leave it like that ? How will i know then the mercure url ?

MatTheCat Apr 2, 2025

IIUC you should remove them so that they don’t override the Symfony server’s.

Never used this functionality though so I’m not sure 😅

Asmitta-01 Apr 3, 2025
Author

I reverted back all my changes then followed this course: https://symfonycasts.com/screencast/turbo/mercure (Chapter 47-52).
It works now.

Comparing changes, it seems that i should have juste uncomment the #SERVER_NAME: ':80' line in the compose.yaml. And the mercure port is random, so each time if i want to access i should do try http://127.0.0.1:<random_port>/.well-known/mercure. We can get the port with the command:

 symfony var:export --multiline | grep MERCURE

Answer selected by Asmitta-01

MatTheCat Apr 3, 2025

the mercure port is random

Yes because your Compose config doesn’t map it to a fixed port on your host. That’s why the Symfony server is supposed to create mercure env vars for you.

seb-jean · 2025-04-12T08:08:22Z

seb-jean
Apr 12, 2025

@Asmitta-01 But can you access the URL in HTTPS?

4 replies

Asmitta-01 Apr 12, 2025
Author

Yes

seb-jean Apr 12, 2025

Did you set up a specific configuration for Docker?

Asmitta-01 Apr 12, 2025
Author

My configuration is the default one.

###> symfony/mercure-bundle ###
  mercure:
    image: dunglas/mercure
    restart: unless-stopped
    environment:
      # Uncomment the following line to disable HTTPS,
      SERVER_NAME: ':80'
      MERCURE_PUBLISHER_JWT_KEY: 'sIsF/hvg/Z4Yu0N9VNboDc1Aro1i2Pondk1FkHFsUr8='
      MERCURE_SUBSCRIBER_JWT_KEY: 'sIsF/hvg/Z4Yu0N9VNboDc1Aro1i2Pondk1FkHFsUr8='
      # Set the URL of your Symfony project (without trailing slash!) as value of the cors_origins directive
      MERCURE_EXTRA_DIRECTIVES: |
        cors_origins https://127.0.0.1:8000
    # Comment the following line to disable the development mode
    command: /usr/bin/caddy run --config /etc/caddy/dev.Caddyfile
    healthcheck:
      test: ["CMD", "curl", "-f", "https://localhost/healthz"]
      timeout: 5s
      retries: 5
      start_period: 60s
    volumes:
      - mercure_data:/data
      - mercure_config:/config
###< symfony/mercure-bundle ###

seb-jean Apr 12, 2025

My configuration in compose.yaml is similar to yours.
When you do symfony var:export --multiline | grep MERCURE, what result do you get?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

404 Error with Mercure public link #60119

{{title}}

Replies: 2 comments 10 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

404 Error with Mercure public link #60119

Replies: 2 comments · 10 replies

Asmitta-01 Apr 2, 2025 Author

Asmitta-01 Apr 3, 2025 Author

Asmitta-01 Apr 12, 2025 Author

Asmitta-01 Apr 12, 2025 Author

Replies: 2 comments 10 replies

Asmitta-01 Apr 2, 2025
Author

Asmitta-01 Apr 3, 2025
Author

Asmitta-01 Apr 12, 2025
Author

Asmitta-01 Apr 12, 2025
Author