• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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.
 
Updates:
- Re-imaged the VPS server.
- Added the Firewall extension.
- Enabled Firewall protection which allowed me to create a rule allowing TCP on port 8090 to my IP as the source.
Yet still I'm unable to access the websocket URL: ws://66.179.243.47:8090/.

Also:
- Unchecked: Restrict the ability to follow symbolic links.
- Unchecked: Proxy mode
- Added the following to Additional nginx directives:

location / {
proxy_pass http://66.179.243.47:8090
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;
}

Yet still I'm unable to access the websocket URL: ws://66.179.243.47:8090/.
It shouldn't be this complicated.
 
Back
Top