nginx errors spewed (at random) running latest insiders?

Created by: slimsag

Ensure you are running clean (rm -rf ~/.sourcegraph), without any existing nginx configuration.

Run the latest insiders server image, according to docs.sourcegraph.com instructions. See error logs in console:

23:53:42           frontend | ✱ Sourcegraph is ready at: http://127.0.0.1:7080
23:53:43       repo-updater | t=2019-01-14T23:53:43+0000 lvl=eror msg="failed to run repository clone purge" worker=repo-purge error="Get http://127.0.0.1:3178/list?cloned: dial tcp 127.0.0.1:3178: connect: connection refused"
23:55:50              nginx | 2019/01/14 23:55:50 [crit] 88#88: *1 connect() to [::1]:8080 failed (99: Address not available) while connecting to upstream, client: 172.17.0.1, server: , request: "GET /sign-in?returnTo=%2F HTTP/1.1", upstream: "http://[::1]:8080/sign-in?returnTo=%2F", host: "localhost:7080"
00:05:29              nginx | 2019/01/15 00:05:29 [crit] 88#88: *16 connect() to [::1]:8080 failed (99: Address not available) while connecting to upstream, client: 172.17.0.1, server: , request: "POST /.api/graphql?CurrentAuthState HTTP/1.1", upstream: "http://[::1]:8080/.api/graphql?CurrentAuthState", host: "localhost:7080", referrer: "http://localhost:7080/site-admin"

The actual app seems to work okay though? Why do we get these errors?