nginx -t fails due to someone messing with it
January 02, 2021 03:16PM
We have a community server which someone seems to have changed in a manner I can't quite track down.

`nginx -t` returns

```
nginx: [emerg] BIO_new_file("/etc/ssl/nginx/cloud.example.com.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/nginx/cloud.example.com.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed
```

Any assistance in tracking down and fixing this error appreciated!
Re: nginx -t fails due to someone messing with it
January 02, 2021 04:03PM
Here is output from ../nginx/error.log

2021/01/02 13:51:19 [emerg] 17656#17656: BIO_new_file("/etc/ssl/nginx/cloud.example.com.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(’/etc/ssl/nginx/cloud.example.com.crt’,‘r’) error:2006D080:BI
O routines:BIO_new_file:no such file)
2021/01/02 14:00:01 [error] 10054#10054: *765928 connect() failed (111: Connection refused) while connecting to upstream, client: 172.93.55.252, server: leapchat.noisebridge.info, request: “GET / HTTP/1.1”, upstream: "http://[::1]:8080/
", host: “leapchat.noisebridge.info”
2021/01/02 14:00:01 [warn] 10054#10054: *765928 upstream server temporarily disabled while connecting to upstream, client: 172.93.55.252, server: leapchat.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://[::1]:8080/”, host
: “leapchat.noisebridge.info”
2021/01/02 14:00:02 [error] 10054#10054: *765931 connect() failed (111: Connection refused) while connecting to upstream, client: 172.93.55.252, server: effective.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://[::1]:8082
/”, host: “effective.noisebridge.info”
2021/01/02 14:00:02 [warn] 10054#10054: *765931 upstream server temporarily disabled while connecting to upstream, client: 172.93.55.252, server: effective.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://[::1]:8082/”, hos
t: “effective.noisebridge.info”
2021/01/02 14:57:40 [error] 10054#10054: *768357 upstream prematurely closed connection while reading response header from upstream, client: 94.21.206.73, server: gossip.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://[::
1]:8008/”, host: “gossip.noisebridge.info”, referrer: “https://github.com/ssbc/ssb-server/wiki/Pub-Servers”
2021/01/02 14:57:40 [warn] 10054#10054: *768357 upstream server temporarily disabled while reading response header from upstream, client: 94.21.206.73, server: gossip.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://[::1]:
8008/”, host: “gossip.noisebridge.info”, referrer: “https://github.com/ssbc/ssb-server/wiki/Pub-Servers”
2021/01/02 14:57:40 [error] 10054#10054: *768357 upstream prematurely closed connection while reading response header from upstream, client: 94.21.206.73, server: gossip.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://127
.0.0.1:8008/”, host: “gossip.noisebridge.info”, referrer: “https://github.com/ssbc/ssb-server/wiki/Pub-Servers”
2021/01/02 14:57:40 [warn] 10054#10054: *768357 upstream server temporarily disabled while reading response header from upstream, client: 94.21.206.73, server: gossip.noisebridge.info, request: “GET / HTTP/1.1”, upstream: “http://127.0.
0.1:8008/”, host: “gossip.noisebridge.info”, referrer: “https://github.com/ssbc/ssb-server/wiki/Pub-Servers”
2021/01/02 14:57:40 [error] 10054#10054: *768357 no live upstreams while connecting to upstream, client: 94.21.206.73, server: gossip.noisebridge.info, request: “GET /favicon.ico HTTP/1.1”, upstream: “http://localhost/favicon.ico”, host
: “gossip.noisebridge.info”, referrer: “https://gossip.noisebridge.info/”
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 70
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready