Problem accessing myVesta on port 8083

[stud_muffler]

Hello!

I started having issue accessing myVesta by domain and by IP on port 8083.
It seems port 8083 is either blocked or no longer listen on.
All sites are up including domain and subdomain of the control panel but attempts to connect using secret URL producing 'Site Cannot be reached' message.
I can access the server by SSH and confirm that secret URL is correct.
Server is Debian 12 with all updates installed trough apt.

Where, how, and what should I check to troubleshoot and fix the issue?

Thanks!

[myVesta]

Code: Select all

sudo /usr/local/vesta/bin/v-update-sys-vesta-all

If it's still offline, try:

Code: Select all

chmod +x /usr/local/vesta/php/sbin/*
systemctl start vesta

[stud_muffler]

Code: Select all

sudo /usr/local/vesta/bin/v-update-sys-vesta-all

If it's still offline, try:

Code: Select all

chmod +x /usr/local/vesta/php/sbin/*
systemctl start vesta

Still getting this site cannot be reached.

sudo systemctl status vesta
● vesta.service - LSB: starts the vesta control panel
Loaded: loaded (/etc/init.d/vesta; generated)
Active: active (running) since Fri 2026-10-23 04:34:43 HST; 3h 58min ago
Docs: man:systemd-sysv-generator(8)
Process: 520 ExecStart=/etc/init.d/vesta start (code=exited, status=0/SUCCESS)
Tasks: 5 (limit: 2297)
Memory: 28.6M
CPU: 720ms
CGroup: /system.slice/vesta.service
├─ 559 "nginx: master process /usr/local/vesta/nginx/sbin/vesta-nginx"
├─ 618 "php-fpm: master process (/usr/local/vesta/php/etc/php-fpm.conf)"
├─ 627 "php-fpm: pool www"
├─ 628 "php-fpm: pool www"
└─6600 "nginx: worker process"

Oct 23 04:34:42 myvistacp.studdy.top systemd[1]: Starting vesta.service - LSB: starts the vesta control panel...
Oct 23 04:34:42 myvistacp.studdy.top vesta[520]: Starting vesta-nginx: vesta-nginx.
Oct 23 04:34:43 myvistacp.studdy.top vesta[520]: Starting vesta-php: vesta-php.
Oct 23 04:34:43 myvistacp.studdy.top systemd[1]: Started vesta.service - LSB: starts the vesta control panel.

PS C:\WINDOWS\system32> test-netconnection myvistacp.studdy.top -port 8083
WARNING: TCP connect to (185.235.177.158 : 8083) failed


ComputerName : myvistacp.studdy.top
RemoteAddress : 185.235.177.158
RemotePort : 8083
InterfaceAlias : Ethernet 2
SourceAddress : 192.168.0.186
PingSucceeded : True
PingReplyDetails (RTT) : 109 ms
TcpTestSucceeded : False



PS C:\WINDOWS\system32> test-netconnection myvistacp.studdy.top -port 443


ComputerName : myvistacp.studdy.top
RemoteAddress : 185.235.177.158
RemotePort : 443
InterfaceAlias : Ethernet 2
SourceAddress : 192.168.0.186
TcpTestSucceeded : True

[myVesta]

But the reason for that is not myvesta (vesta) service on port 8083, but nginx (or eventually apache2) on port 443.

See with:

Code: Select all

sytemctl status nginx
sytemctl status apache2

... and prompt AI for debugging.

[stud_muffler]

But the reason for that is not myvesta (vesta) service on port 8083, but nginx (or eventually apache2) on port 443.

See with:

Code: Select all

sytemctl status nginx
sytemctl status apache2

Both seems fine, I also checked iptables but did not see anything suspicious, however, the fix was to change to a different port...
Still not sure what is blocking original port.