S
S
Shing2019-04-10 13:13:43
linux
Shing, 2019-04-10 13:13:43

NGINX won't restart, it looks like port 443 is busy, how can I fix it?

Nginx doesn't restart after I switch domain to SSL.
Issues

nginx: [emerg] bind() to 443 failed (98: Address already in use)

That is, port 443 is busy as I understand it.
netstat shows: tcp 0 0 :::443 :::* LISTEN 2488/
httpd
(98)Address already in use: make_sock: could not bind to address [::]:443
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443

in /etc/httpd/conf.d/ssl.conf Listen 443
ps centos 6.1, vestacp, letsencrypt

Answer the question

In order to leave comments, you need to log in

3 answer(s)
V
Vladimir, 2019-04-10
@Casufi

The Apache port is still busy, try to put it out in the services and check if autorun is installed on it.

F
Fixid, 2019-04-10
@Fixid

Everything is logical. There can only be one process on one port.
If you have a typical scheme where Nginx is a reverse proxy on localhost, then only it should have an ssl certificate. And httpd should respond over http to localhost for Nginx

T
TyzhSysAdmin, 2019-04-10
@POS_troi

Well, the logical behavior of services that want the same port.
You decide why you need all this, if Apache is not needed, then leave only nginx, if Apache is needed and nginx is also needed, then transfer Apache to another port and use nginx as a proxy.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question