Laravel Websockets

alphaproject1998

I have tried pretty much everything to get laravel websockets to work, even with port 6001 open and only laravel listening on it, still timeout on every attempt, I have it allowed in the firewall and have tried reverse proxy yet still nothing

aaPanel_Kern

Hello, does the security group of the server provider need to be open as well? Is the server accessible locally normal?

alphaproject1998

aaPanel_Kern sorry I'm not sure what you mean with that I don't understand what you are saying

aaPanel_Kern

Use the command to access curl -k http://127.0.0.1:6001 Can it be accessed normally?
If you can, please check whether the security of the server provider requires the opening of port 6001?

alphaproject1998

aaPanel_Kern

I checked in my server provider and the provider is not blocking the port it is handled by the server and the server (in aaPanel) has the port open

aaPanel_Kern

Hello, is this port listening?

alphaproject1998

aaPanel_Kern
Yeah it is listening

aaPanel_Kern

Use the command to access curl -kvv https://127.0.0.1:6001 Can it be accessed normally?

alphaproject1998

aaPanel_Kern

It does connect but it says 404 Not Found after it connects yet it is listening on that port and laravel-websockets are up and running

aaP_hareeshnarayan1982
Hey, thanks I have done that in a similar way in apache:
RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) wss://127.0.0.1:6001/$1 [P,L]

ProxyPass /ws wss://127.0.0.1:6001/
ProxyPassReverse /ws wss://127.0.0.1:6001/

I have also tried:

RewriteEngine On
RewriteCond %{REQUEST_URI}  ^/socket.io            [NC]
RewriteCond %{QUERY_STRING} transport=websocket    [NC]
RewriteRule /(.*)           wss://localhost:6001/$1 [P,L]
  
ProxyPass / https://localhost:6001/
ProxyPassReverse / https://localhost:6001/

aaP_hareeshnarayan1982

Did you add configuration in Nginx/Apache to support websockets? .eg: we use signalR and add following configs to nginx.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
proxy_http_version 1.1;

DimmmCom

alphaproject1998

ProxyPass /ws http://localhost:6001/ upgrade=websocket

DimmmCom

alphaproject1998 ^/socket.io

I just now noticed in your config the mention of the socket.io library. If you clients connect to the socket server through the browser using JS socket.io, the config will be a bit different. This should help

ProxyPass /socket.io/ http://localhost:6001/ upgrade=websocket

Too little information you provide to understand the issue)

alphaproject1998

DimmmCom
Hey, that doesn't seem to change anything either :/

alphaproject1998

DimmmCom
Thanks and yeah I do know to restart apache xD

Sadly that doesn't seem to change the issue either, here is some of the info I have so far:

I get this in the website console (firefox):

The connection to wss://[domain]:6001/socket.io/?EIO=4&transport=websocket was interrupted while the page was loading.
Firefox can’t establish a connection to the server at wss://[domain]:6001/.

and this in chrome:

WebSocket connection to 'wss://[domain]:6001/socket.io/?EIO=4&transport=websocket' failed: WebSocket is closed before the connection is established.

This on the websocket dashboard "Channels current state is unavailable" & in console:

The connection to wss://[domain]:6001/app/[key]?protocol=7&client=js&version=4.3.1&flash=false was interrupted while the page was loading.

This when I run curl -v http://127.0.0.1:6001

Trying 127.0.0.1:6001...
Connected to 127.0.0.1 (127.0.0.1) port 6001
GET / HTTP/1.1
Host: 127.0.0.1:6001
User-Agent: curl/8.5.0
Accept: /
Empty reply from server
Closing connection
curl: (52) Empty reply from server

This when I run npx wscat -c ws://127.0.0.1:6001

error: socket hang up

This when I run netstat -tulnp | grep 6001

tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 4173832/php

I have also checked both in aaPanel and on my server provider that the port is open, and that only laravel websockets should be using that port, I have a laravel + nuxt app that works fine using nuxt's websockets but this app fails using laravel-websocket :/ oh and I do check that it is actually running before all this and no error logs in laravel or in the console that is running the websocket

DimmmCom

I don't write about restarting apache after a config change, I think it's clear enough)

DimmmCom

alphaproject1998 but this app fails using laravel-websocket

alphaproject1998 The connection to wss://[domain]:6001/socket.io/?EIO=4&transport=websocket was interrupted while the page was loading.
Firefox can’t establish a connection to the server at wss://[domain]:6001/.

Does laravel-websocket support working with Socket.IO? As far as I remember laravel-websocket doesn't have Socket.IO protocol implementation.

alphaproject1998

DimmmCom

I found some that used it, I have tried pusher and Ably as per the laravel docs but all give the same issues which is why I came here

DimmmCom

alphaproject1998 I don't think it's related to aaPanel and it's unlikely you'll get help here with Laravel and Socket.IO configuration. As always you don't give enough information to be of any help. You write that you found an implementation of Laravel-websocket with Socket.IO, but attach at least a link to such a framework, I personally don't know such frameworks to support Socket.IO v.4. Support for version 2 of Socket.IO I've met, but the fourth version of the protocol is not supported. I myself am a developer of a plugin that realizes the interaction of Swoole server with Socket.IO. I am inclined to believe that you do not have a handshake on the Laravel side. If proxying didn't work, the errors would be 5xx, and you have 404.

aaP_hareeshnarayan1982

DimmmCom
I too feel that, this is not related to panel. We are running SignalR with dontnet backend and React Front end without any issues. We use Nginx, so the configurations are different. But We never had issues with websockets with aapanel.