Replies: 2 comments
-
I have same configuration like you. Only difference is that I using Nginx server. In my case, I deployed code to test server. when check on my personal machine reverb work.(auth api fired and ping-pong happend). When check on other systems reverb not works. Auth api(/broadcasting/auth) not fired and socket connection shows finished. Vuejs .env
vuejs config.js
Note: REVERB_HOST value is same as domain name. Reverb.php return [
]; laravel .env
vuejs echo connection code
Added proxy setting also
Update: |
Beta Was this translation helpful? Give feedback.
-
I found the solution for this after lot of re-search. Need to create subdomain, and add proxy code in server config file. |
Beta Was this translation helpful? Give feedback.
-
Reverb Version
1.0
Laravel Version
11.9
Php Version
8.2
VueJS Version
3.0
Node Version
v20.18.0
Laravel Echo
1.16.1
Pusher-js
8.4.0-rc2
Description
I have Laravel 11 application (backend) and Vue (front) hosted in IIS (Server 2022). I'm not quite familiar working with websockets(Reverb) in IIS and read a lot of discussions in nginx, sail, etc.. and tried it but none are working so far. I'm receiving the error
WebSocket connection to 'wss://test.local:8080/app/1233455?protocol=7&client=js&version=8.4.0-rc2&flash=false' failed:
In the IIS Manager under Bindings this is our configuration:
VueJS front site:
type: https
hostname: test.local
port:443
laravel backend site:
type: https
hostname: test.local
port: 3004
So it's basically under the same hostname but in different ports.
For the Websocket, here's what I've done so far.
In the .env of backend
In the .env of front
Also the echo.js
Inside reverb.php
Inside broadcasting.php
Beta Was this translation helpful? Give feedback.
All reactions