• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Issue Websocket configuration, site can't be reached

immc

New Pleskian
Server operating system version
Ubuntu 24.04.3 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.74 Update 3
My first go at testing a websocket connection per instructions provided via a Laravel script I'm installing onto a Plesk Obsidian 18.0.74 Update 3 server running Ubuntu 24.04.3 LTS and I'm having trouble getting this to work. Per the instructions I'm supposed to:
- Create and update the configuration file:

[program:websocket]
process_name=%(program_name)s_%(process_num)02d
command=/usr/bin/php /var/www/vhosts/mydomain.org/httpdocs/artisan websocket:init
autostart=true
autorestart=true
user=www-data
numprocs=1
redirect_stderr=true
stdout_logfile=/var/www/vhosts/mydomain.org/httpdocs/storage/logs/websocket.log
stderr_logfile=/var/www/vhosts/mydomain.org/httpdocs/storage/logs/websocket.log

Run the following:
sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl start websocket
- websocket: ERROR (no such process)

sudo supervisorctl status
- websocket:websocket_00 RUNNING pid 111662, uptime 0:58:04.

Type to list all running processes:

ps aux | grep [websocket]

I see the process in this list under user=www-data.
???

Open a web browser and navigate to the following URL:

ws://my.ap.address:8090/

I get the following error:

This site can’t be reached

The webpage at ws://66.179.243.47:8090/ might be temporarily down or it may have moved permanently to a new web address.

ERR_UNKNOWN_URL_SCHEME

This might be tripping me up:

sudo ufw status verbose
sudo ufw allow 8090/tcp
sudo ufw enable
- Type y to continue.
sudo systemctl restart ssh

sudo ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disable (routed)
New profiles: skip

To
8090/tcp | ALLOW IN ANYWHERE
8090/tcp (v6) ALLOW IN ANYWHERE (v6)

Verify listening ports via SSH:

sudo ss -tlnp | grep 8090
LISTEN 0 511 0.0.0.0:8090 0.0.0.0:* users: (("php", pid=111662, fd=5))


Are there any additional steps I need to take to be able to access the websocket?

Any responses appreciated.
 
Back
Top