It is worth ubuntu 14, the panel is vesta, I recently put letsencrypt certificates, before that it didn’t seem to have fallen. The following errors are in the Apache logs:

[Sun Apr 17 04:05:22.536393 2016] [ssl:warn] [pid 30605] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366) [Sun Apr 17 04:05:22.536465 2016] [suexec:notice] [pid 30605] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec) [Sun Apr 17 04:05:29.932891 2016] [:notice] [pid 30606] mod_ruid2/0.9.8 enabled [Sun Apr 17 04:05:29.934234 2016] [ssl:warn] [pid 30606] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366) [Sun Apr 17 04:05:30.237438 2016] [mpm_prefork:notice] [pid 30606] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Sun Apr 17 04:05:30.237479 2016] [core:notice] [pid 30606] AH00094: Command line: '/usr/sbin/apache2'

Example of nginx logs:

 2016/02/17 15:19:40 [alert] 1133#0: worker process 1136 exited on signal 9 2016/04/09 13:38:22 [emerg] 23131#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2016/04/09 13:38:22 [emerg] 23131#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2016/04/09 13:38:22 [emerg] 23131#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2016/04/09 13:38:22 [emerg] 23131#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2016/04/09 13:38:22 [emerg] 23131#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2016/04/09 13:38:22 [emerg] 23131#0: still could not bind() 2016/04/11 02:11:22 [alert] 1100#0: worker process 1103 exited on signal 9

Most likely the Apache case is, I think, googled on the Internet, but due to my error there is little information, as I understood the case in ssl? How can I correct these errors?

  • There is not a line in your Apache logs about why he could fall. And nginx says that port 8083 is busy. Most likely you have some other application that uses this port. - Mike
  • And which he writes warnings about ssl can not lead to this? More in the logs there is nothing, it turns out the problem with the ports? - wpbloger
  • Well, there are warnings that not all clients will understand certificates by domain names. And nginx stupidly can not take a port and does not start at all. - Mike
  • It is interesting, but according to the dates these Apache logs are the same, with dates when the server was lying, where else you can see what is wrong, what logs I brought, I don’t know where to look anymore. - wpbloger

0