Run Mercure生产:404未找到

  • 本文关键字:Mercure 生产 Run mercure
  • 更新时间 :
  • 英文 :


我正在联系您,因为我无法让mercure在生产中工作。

二进制预构建运行良好,但当我尝试连接到集线器时,我会得到404 no found。

这是我运行的命令:

sudo MERCURE_PUBLISHER_JWT_KEY='eyJhbGciOiJIUzI1NiIsInR5cCI6...' MERCURE_SUBSCRIBER_JWT_KEY='eyJhbGciOiJIUzI1NiIsInR5cCI6...' SERVER_NAME=:3000 ./mercure run

服务器启动时显然没有任何问题:

2022/02/15 17:38:09.919 INFO    using adjacent Caddyfile
2022/02/15 17:38:09.920 WARN    input is not formatted with 'caddy fmt' {"adapter": "caddyfile", "file": "Caddyfile", "line": 3}
2022/02/15 17:38:09.921 INFO    admin   admin endpoint started  {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["[::1]:2019", "127.0.0.1:2019", "localhost:2019"]}
2022/02/15 17:38:09.922 INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc0000cb7a0"}
2022/02/15 17:38:09.935 INFO    tls     cleaning storage unit   {"description": "FileStorage:/root/.local/share/caddy"}
2022/02/15 17:38:09.935 INFO    tls     finished cleaning storage units
2022/02/15 17:38:09.935 INFO    autosaved config (load with --resume flag)      {"file": "/root/.config/caddy/autosave.json"}
2022/02/15 17:38:09.935 INFO    serving initial configuration

my.env配置如下:

###> symfony/mercure-bundle ###
MERCURE_URL=https://monsite.com/.well-known/mercure
MERCURE_PUBLIC_URL=https://monsite.com/.well-known/mercure
MERCURE_JWT_SECRET="eyJhbGciOiJIUzI1NiIsInR5cCI6..."
###< symfony/mercure-bundle ###

我的CaddyFile:

# Learn how to configure the Mercure.rocks Hub on https://mercure.rocks/docs/hub/config
{
{$GLOBAL_OPTIONS}
}
{$SERVER_NAME:monsite.com}
log
route {
encode zstd gzip
mercure {
# Transport to use (default to Bolt)
transport_url {$MERCURE_TRANSPORT_URL:bolt://mercure.db}
# Publisher JWT key
publisher_jwt {env.MERCURE_PUBLISHER_JWT_KEY} {env.MERCURE_PUBLISHER_JWT_ALG}
# Subscriber JWT key
subscriber_jwt {env.MERCURE_SUBSCRIBER_JWT_KEY} {env.MERCURE_SUBSCRIBER_JWT_ALG}
# Allow Subscribers
anonymous
# Extra directives
{$MERCURE_EXTRA_DIRECTIVES}
}
respond /healthz 200
respond "Not Found" 404
}

当我试图通过键入以下命令与邮递员一起访问集线器时:

https://monsite.com/.well-known/mercure

我得到一个404没有找到。

我在linux下debian 10与apache2。我不明白我做错了什么。谢谢你的帮助。

2022年2月21日编辑

嗨,Mehmet,这是我所做的:

在/etc/apache2/可用的站点monsite.conf和monsite-le-sl.conf中:

ProxyPass /mercure-hub http://localhost:8080/
ProxyPassReverse /mercure-hub http://localhost:8080/

在Caddyfile和Caddyfile.dev:中

{
{$GLOBAL_OPTIONS}
auto_https off }
{$SERVER_NAME::8080}

显然,集线器启动良好,我在控制台中没有错误:

debian@vps-...:/var/www/monsite/mercure$ sudo MERCURE_PUBLISHER_JWT_KEY='eyJhbGciOiJIUzI1NiIsInR5cCI6I...' MERCURE_SUBSCRIBER_JWT_KEY='eyJhbGciOiJIUzI1NiIsInR5cCI6I...' ./mercure run -config Caddyfile.dev
2022/02/21 13:31:20.672 INFO    using provided configuration    {"config_file": "Caddyfile.dev", "config_adapter": ""}
2022/02/21 13:31:20.675 WARN    input is not formatted with 'caddy fmt' {"adapter": "caddyfile", "file": "Caddyfile.dev", "line": 3}
2022/02/21 13:31:20.676 INFO    admin   admin endpoint started  {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["localhost:2019", "[::1]:2019", "127.0.0.1:2019"]}
2022/02/21 13:31:20.676 INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc0003fe700"}
2022/02/21 13:31:20.703 INFO    tls     cleaning storage unit   {"description": "FileStorage:/root/.local/share/caddy"}
2022/02/21 13:31:20.703 INFO    tls     finished cleaning storage units
2022/02/21 13:31:20.703 INFO    autosaved config (load with --resume flag)      {"file": "/root/.config/caddy/autosave.json"}
2022/02/21 13:31:20.704 INFO    serving initial configuration

无论我运行Caddyfile还是Caddyfile.dev,在访问时https://monsite.com/mercure-hub,我得到一个500的错误。

这是我的apache设置。也许对你有帮助。

打开nano/etc/apache2/可用站点/yourdomain.com-le-sl.conf

<IfModule mod_ssl.c>
<VirtualHost *:443>
DocumentRoot /var/www/html/yourdomain.com
DirectoryIndex /index.php
ServerName yourdomain.com
#Settings for mercure
ProxyPass      /mercure-hub     http://localhost:8080
ProxyPassReverse /mercure-hub   http://localhost:8080

<Directory /var/www/html/yourdomain.com >
AllowOverride None
Order Allow,Deny
Allow from All
FallbackResource /index.php
Options FollowSymLinks MultiViews
</Directory>
<Directory /var/www/html/yourdomain.com >
DirectoryIndex disabled
FallbackResource disabled
</Directory>

RewriteEngine on

Include /etc/letsencrypt/options-ssl-apache.conf
#YOUR SSL PEM FİLES
SSLCertificateFile /etc/letsencrypt/live …..
SSLCertificateKeyFile /etc/letsencrypt/live …..

</VirtualHost>
</IfModule>

你的球童选项应该喜欢

{
{$GLOBAL_OPTIONS}
auto_https off
}
{$SERVER_NAME::8080}#this parameter will run http://localhost:8080

美居司令部

MERCURE_PUBLISHER_JWT_KEY='YOUR_KEY' MERCURE_SUBSCRIBER_JWT_KEY='YOUR_KEY' ./mercure run -config Caddyfile

您可以尝试使用Caddyfile.dev进行测试。

MERCURE_PUBLISHER_JWT_KEY='YOUR_KEY' MERCURE_SUBSCRIBER_JWT_KEY='YOUR_KEY' ./mercure run -config Caddyfile.dev

设置后,您的商品将运行yourdomain.com/mercure-hub

经过一番挖掘,我试图弄清楚它返回500错误的原因。我去了apache日志,我收到了这样的错误消息:

"没有对URL/有效的协议处理程序。如果您正在使用DSOmod_proxy版本,请确保代理子模块包含在使用LoadModule"的配置;

所以我安装了缺失的组件:

sudo a2enmod ssl
sudo a2enmod proxy
sudo a2enmod proxy_balancer
sudo a2enmod proxy_http

我还通过在mercure hub的末尾添加斜杠来修改代理URL,否则我会得到404错误:

ProxyPass /mercure-hub/ http://localhost:8080/
ProxyPassReverse /mercure-hub/ http://localhost:8080/

重新启动apache,并更新了我的.env:中的Url

MERCURE_URL=https://monsite.com/mercure-hub/.well-known/mercure
MERCURE_PUBLIC_URL=https://monsite.com/mercure-hub/.well-known/mercure 

它很管用,非常感谢!

最新更新