root@debian:~# lsof -i:8084
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nginx 1056 root 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1057 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1058 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1059 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1060 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1061 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1062 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1063 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
nginx 1066 www-data 46u IPv4 16898 0t0 TCP localhost:8084 (LISTEN)
You can change Hestia CP port with this command:
v-change-sys-port 8083
This is the email reminder I received
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: [emerg] bind() to 127.0.0.1:8084 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed
I searched for the port located in the etc/nginx directory and found that the file
is located in/etc/nginx/conf.d/stats.comnf. After modification, it was found that nginx could not start.
Does this file default to 8084? Why do I receive abnormal notifications? How should I operate?
I’m sorry but I don’t understand what you want to do.
Nginx listens on ports 80, 443 and 8084 only on 127.0.0.1 for nginx status.
Hestia control panel uses another Nginx instance and it listens by default on port 8083.
Now, what you want to change?
I have checked the configuration file and found that the port in /etc/nginx/conf.d/status.conf
is set to 8084. Is this a misconfiguration? Please review or help me correct this error
I have checked all the servers where I have installed the Hestia panel. The port in the file is 8084
No It is fine keep it like it it might break certiain functions in the “Server” monitor tabs…
How should I handle email exception notifications.
I don’t know what you mean. If you receive that mail is because there is a problem, another process is listening on port 8084 or there are some stuck nginx processes on port 8084 and you should take a look.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.