我试图用多台服务器实现Laravel。
我有一个App服务器和一个队列工作服务器正在运行。我试图从队列工作服务器广播我的通知,但是
光照\广播\广播异常:推送错误:。在/home/forge/my-app/vendor/laravel/framework/src/Illuminate/Broadcasting/Broadcasters/PusherBroadcaster.php:128中
在App中,在Network中,我可以确认它连接到websocket。我使用了亚历克斯·布马职位并安装了反向代理。如果我在App中广播,它就能工作
server {
listen 6002 ssl http2;
listen [::]:6002 ssl http2;
server_name example.com;
index.php
location / {
proxy_pass http://127.0.0.1:6001;
proxy_read_timeout 60;
proxy_connect_timeout 60;
proxy_redirect off;
# Allow the use of websockets
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}App &队列工作器位于专用网络中,可以相互连接。但是,当我尝试从队列工作服务器广播时,它无法工作。
我很难理解如何让它发挥作用。
php artisan websockets:serve?如果是这样的话,我需要给--host={private-ip}标志吗?broadcasting.php中,我为队列工作者的env添加了App的私有ip作为PUSHER_ENDPOINT_HOST。这是正确的吗?'pusher' => [
'driver' => 'pusher',
'key' => env('PUSHER_APP_KEY'),
'secret' => env('PUSHER_APP_SECRET'),
'app_id' => env('PUSHER_APP_ID'),
'options' => [
'cluster' => env('PUSHER_APP_CLUSTER'),
'encrypted' => in_array(config('app.env'), ['production', 'staging']),
'host' => env('PUSHER_ENDPOINT_HOST', '127.0.0.1'),
'port' => 6001,
'scheme' => 'http'
],
],更新:正如@KamleshPaul建议的那样,我做了一些修改。下面是我所有的代码。
我在应用服务器和工人服务器上都有这些信任。我正在这两个平台上运行php artisan websockets:serve,App成功地连接到套接字。但是,队列工作人员不发送通知。
两个php artisan websockets:serve都显示:“在端口6001上启动WebSocket服务器.”
但它似乎不起作用。(顺便说一句,我使用的是Laravel,允许的端口如下:
.env
PUSHER_APP_ID=aaa
PUSHER_APP_KEY=bbb
PUSHER_APP_SECRET=ccc
PUSHER_APP_CLUSTER=mt1
PUSHER_HOST=socket.my_domain.com
PUSHER_PORT=433
PUSHER_SCHEME=https
VITE_PUSHER_APP_KEY=${PUSHER_APP_KEY}
VITE_PUSHER_APP_CLUSTER=${PUSHER_APP_CLUSTER}
VITE_PUSHER_HOST=${PUSHER_HOST}
VITE_PUSHER_SCHEME={PUSHER_SCHEME}
VITE_PUSHER_PORT={PUSHER_PORT}echo.js
window.Echo = new Echo({
broadcaster: 'pusher',
key: import.meta.env.VITE_PUSHER_APP_KEY,
cluster: import.meta.env.VITE_PUSHER_APP_CLUSTER,
wsHost: import.meta.env.VITE_PUSHER_HOST,
wsPort: import.meta.env.VITE_PUSHER_PORT || 443,
forceTLS: true,
disableStats: true,
scheme: import.meta.env.VITE_PUSHER_SCHEME,
enabledTransports: ["ws", "wss"],
}broadcasting.php
'pusher' => [
'driver' => 'pusher',
'key' => env('PUSHER_APP_KEY'),
'secret' => env('PUSHER_APP_SECRET'),
'app_id' => env('PUSHER_APP_ID'),
'options' => [
'cluster' => env('PUSHER_APP_CLUSTER'),
'encrypted' => true,
'host' => env('PUSHER_HOST'),
'port' => env('PUSHER_PORT'),
'scheme' => env('PUSHER_SCHEME')
],
],socket.my_domain.com的nginx
# FORGE CONFIG (DO NOT REMOVE!)
include forge-conf/socket.my_domain.com/before/*;
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name socket.my_domain.com;
server_tokens off;
root /home/forge/socket.my_domain.com/public;
# FORGE SSL (DO NOT REMOVE!)
ssl_certificate /etc/nginx/ssl/socket.my_domain.com/1262458/server.crt;
ssl_certificate_key /etc/nginx/ssl/socket.my_domain.com/1262458/server.key;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
ssl_prefer_server_ciphers off;
ssl_dhparam /etc/nginx/dhparams.pem;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Content-Type-Options "nosniff";
index index.html index.htm index.php;
charset utf-8;
# FORGE CONFIG (DO NOT REMOVE!)
include forge-conf/socket.my_domain.com/server/*;
location / {
proxy_pass http://127.0.0.1:6001;
proxy_read_timeout 60;
proxy_connect_timeout 60;
proxy_redirect off;
# Allow the use of websockets
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
location = /favicon.ico { access_log off; log_not_found off; }
location = /robots.txt { access_log off; log_not_found off; }
access_log off;
error_log /var/log/nginx/socket.my_domain.com-error.log error;
error_page 404 /index.php;
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php/php8.0-fpm.sock;
fastcgi_index index.php;
include fastcgi_params;
}
location ~ /\.(?!well-known).* {
deny all;
}
}
# FORGE CONFIG (DO NOT REMOVE!)
include forge-conf/socket.my_domain.com/after/*;发布于 2021-12-02 05:29:11
创建子域socket.yourapp.tld,然后创建nginx,如下所示
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name socket.yourapp.tld;
# Start the SSL configurations
ssl on;
ssl_certificate /etc/letsencrypt/live/socket.yourapp.tld/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/socket.yourapp.tld/privkey.pem;
location / {
proxy_pass http://127.0.0.1:6001;
proxy_read_timeout 60;
proxy_connect_timeout 60;
proxy_redirect off;
# Allow the use of websockets
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}那么在broadcasting.php中,您需要更改这些
'host' => socket.yourapp.tld,
'port' => 433,
'scheme' => 'https'javascript也是如此。
export default new Echo({
broadcaster: "pusher",
key: "key",
wsHost: process.env.REACT_APP_WS_HOST,
wsPort: process.env.REACT_APP_WS_PORT || 443,
forceTLS: process.env.REACT_APP_WS_PORT === 433,
disableStats: true,
enabledTransports: ["ws", "wss"],
authorizer: (channel, options) => {
return {
authorize: (socketId, callback) => {
axios
.post(
`${process.env.REACT_APP_MARKETPLACE_URL}broadcasting/auth`,
{
socket_id: socketId,
channel_name: channel.name,
},
{
headers: {
Authorization: `Bearer ${token}`,
},
}
)
.then((response) => {
callback(false, response.data);
})
.catch((error) => {
callback(true, error);
});
},
};
},参考链接https://beyondco.de/docs/laravel-websockets/basic-usage/ssl#usage-with-a-reverse-proxy-like-nginx
发布于 2021-12-02 19:39:55
我终于想出来了。下面这些设置适用于我。希望它能为您节省一些时间:)
我决定在像在文档中描述这样的子域方法上使用反向代理。
对于子域的nginx,唯一不同于默认Laravel配置的是location / {}。只要复制你的Laravel应用程序的nginx配置,更改server_name并替换location / {},就可以了。
window.Echo = new Echo({
broadcaster: 'pusher',
key: import.meta.env.VITE_PUSHER_APP_KEY,
cluster: import.meta.env.VITE_PUSHER_APP_CLUSTER,
wsHost: import.meta.env.VITE_PUSHER_HOST,
wsPort: import.meta.env.VITE_PUSHER_PORT || 443,
forceTLS: true,
disableStats: true,
scheme: import.meta.env.VITE_PUSHER_SCHEME,
enabledTransports: ["ws", "wss"],
});// broadcasting.php
'pusher' => [
'driver' => 'pusher',
'key' => env('PUSHER_APP_KEY'),
'secret' => env('PUSHER_APP_SECRET'),
'app_id' => env('PUSHER_APP_ID'),
'options' => [
'cluster' => env('PUSHER_APP_CLUSTER'),
'encrypted' => true,
'host' => env('PUSHER_HOST'),
'port' => env('PUSHER_PORT'),
'scheme' => env('PUSHER_SCHEME'),
],
],// websockets.php
'apps' => [
[
'id' => env('PUSHER_APP_ID'),
'name' => env('APP_NAME'),
'key' => env('PUSHER_APP_KEY'),
'secret' => env('PUSHER_APP_SECRET'),
'host' => env('PUSHER_HOST'),
// 'capacity' => null,
'enable_client_messages' => false,
'enable_statistics' => false,
],
],// .env file
PUSHER_APP_ID=HIDDEN_ID
PUSHER_APP_KEY=HIDDEN_KEY
PUSHER_APP_SECRET=HIDDEN_SECRET
PUSHER_APP_CLUSTER=mt1
PUSHER_HOST=socket.example.com;
PUSHER_PORT=6001
PUSHER_SCHEME=http
VITE_PUSHER_APP_KEY=${PUSHER_APP_KEY}
VITE_PUSHER_APP_CLUSTER=${PUSHER_APP_CLUSTER}
VITE_PUSHER_HOST=${PUSHER_HOST}
VITE_PUSHER_SCHEME=https
VITE_PUSHER_PORT=433php artisan websockets:serve:在我的案例中- App & Worker服务器。在我的例子中,如果我将ssh写入服务器并编写php artisan websockets:serve,它就不会像在本地那样显示即将出现的消息或连接,所以请注意。

一些资源:
https://stackoverflow.com/questions/70194340
复制相似问题