Closed sayou closed 2 weeks ago
UPDATE:
after running Mercure using :
MERCURE_PUBLISHER_JWT_KEY='!ChangeThisMercureHubJWTSecretKey!' MERCURE_SUBSCRIBER_JWT_KEY='!ChangeThisMercureHubJWTSecretKey!' SERVER_NAME=https://localhost ./mercure run
I got a little close to solving the problem, but it started giving me this error:
EventSource's response has a MIME type ("text/plain") that is not "text/event-stream". Aborting the connection.
Thanks for the kind words!
Wouldn't it be simpler to use plain HTTP between NGINX and the hub? If they are on the same machine, there is no benefit in encrypting the inner traffic.
The MIME type error is weird, could you copy the full request and response (including headers) please?
The problem has been resolved by adopting measures discussed earlier (https://github.com/dunglas/mercure/issues/854).
I think that the documentation needs a more detailed and thorough explanation on the official website.
Hello,
Firstly, I want to express my gratitude for the Mercure Hub. It's been a vital part of my web development work.
I am encountering an issue with setting up an Nginx reverse proxy for the Mercure hub on my VPS (not using Docker). Despite following the configuration guides, I'm persistently facing a "502 Bad Gateway" error.
Here's a breakdown of my setup and the problem:
SSL_do_handshake() failed (SSL: error:0A000438:SSL routines::tlsv1 alert internal error:SSL alert number 80)
.I've attached my Nginx configuration and the relevant logs for your reference. Any insights or suggestions to resolve this would be immensely helpful.
Thank you for your time and support.
vHost code:
Caddyfile code:
my .env:
realtime.html:
Best regards,
PS: I use Symfony 6 & API platform