nginx (Address already in use), хотя он свободен
Форум — Admin
Всем привет. Я в какой-то момент перезапустил nginx, и возникла таккая проблема, что порт 443 не занаят, но nginx открыться на нём не может. Может кто-то сталкивался с таким? Есть решение как исправить? Уже перезагружал) ничего не помогло
Кто использует порт 443
root@mail:/etc/nginx/sites-available# ss -tulnp | grep ":443"
root@mail:/etc/nginx/sites-available#
sites-enabled
root@mail:/etc/nginx/sites-enabled# ls -l
total 12
lrwxrwxrwx 1 root root 377 Nov 30 02:59 3xui-api.conf
lrwxrwxrwx 1 root root 376 Nov 30 03:00 xau-api.conf
lrwxrwxrwx 1 root root 372 Nov 30 03:00 xau-client.conf
root@mail:/etc/nginx/sites-enabled# cat ./*
server {
listen 80;
server_name ***;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name ***;
ssl_certificate /certs/walk-ce.pem;
ssl_certificate_key /certs/walk-key.pem;
location / {
proxy_pass https://127.0.0.1:23446;
include /etc/nginx/proxy_params;
}
}
server {
listen 80;
server_name ***;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name ***;
ssl_certificate /certs/xau-ce.pem;
ssl_certificate_key /certs/xau-key.pem;
location / {
proxy_pass https://127.0.0.1:8443/api/v1;
include /etc/nginx/proxy_params;
}
}
server {
listen 80;
server_name ***;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name ***;
ssl_certificate /certs/xau-ce.pem;
ssl_certificate_key /certs/xau-key.pem;
location / {
proxy_pass https://127.0.0.1:8444;
include /etc/nginx/proxy_params;
}
}
sites-available
root@mail:/etc/nginx/sites-available# ls -l
total 12
-rw-r--r-- 1 root root 377 Nov 30 02:59 3xui-api.conf
-rw-r--r-- 1 root root 376 Nov 30 03:00 xau-api.conf
-rw-r--r-- 1 root root 372 Nov 30 03:00 xau-client.conf
root@mail:/etc/nginx/sites-available# cat ./*
server {
listen 80;
server_name ***;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name ***;
ssl_certificate /certs/walk-ce.pem;
ssl_certificate_key /certs/walk-key.pem;
location / {
proxy_pass https://127.0.0.1:23446;
include /etc/nginx/proxy_params;
}
}
server {
listen 80;
server_name ***;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name ***;
ssl_certificate /certs/xau-ce.pem;
ssl_certificate_key /certs/xau-key.pem;
location / {
proxy_pass https://127.0.0.1:8443/api/v1;
include /etc/nginx/proxy_params;
}
}
server {
listen 80;
server_name ***;
return 301 https://$host$request_uri;
}
server {
listen 443 ssl;
server_name ***;
ssl_certificate /certs/xau-ce.pem;
ssl_certificate_key /certs/xau-key.pem;
location / {
proxy_pass https://127.0.0.1:8444;
include /etc/nginx/proxy_params;
}
}
Запуск и вывод
root@mail:/etc/nginx/sites-available# systemctl restart nginx
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xeu nginx.service" for details.
root@mail:/etc/nginx/sites-available# journalctl -xeu nginx.service
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit nginx.service has finished with a failure.
░░
░░ The job identifier is 2287 and the job result is failed.
Nov 30 03:02:02 mail.fire-core.ru systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server...
░░ Subject: A start job for unit nginx.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit nginx.service has begun execution.
░░
░░ The job identifier is 2355.
Nov 30 03:02:02 mail.fire-core.ru nginx[13649]: nginx: [emerg] bind() to ***:443 failed (98: Address already in use)
Nov 30 03:02:02 mail.fire-core.ru nginx[13649]: nginx: [emerg] bind() to ***:443 failed (98: Address already in use)
Nov 30 03:02:03 mail.fire-core.ru nginx[13649]: nginx: [emerg] bind() to ***:443 failed (98: Address already in use)
Nov 30 03:02:03 mail.fire-core.ru nginx[13649]: nginx: [emerg] bind() to ***:443 failed (98: Address already in use)
Nov 30 03:02:04 mail.fire-core.ru nginx[13649]: nginx: [emerg] bind() to ***:443 failed (98: Address already in use)
Nov 30 03:02:04 mail.fire-core.ru nginx[13649]: nginx: [emerg] still could not bind()
Nov 30 03:02:04 mail.fire-core.ru systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit nginx.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 30 03:02:04 mail.fire-core.ru systemd[1]: nginx.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit nginx.service has entered the 'failed' state with result 'exit-code'.
Nov 30 03:02:04 mail.fire-core.ru systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server.
░░ Subject: A start job for unit nginx.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit nginx.service has finished with a failure.
░░
░░ The job identifier is 2355 and the job result is failed.