Francis Daly Wrote:
---
> "Default" there means that if a server{} block does not have any
> listen directive, it is equivalent to "listen *:80" (or "listen *:8080"
if
> running as non-root).
>
> Your "letsencrypt" server{} block does not have an
So, just to be clear, these are the ones running now without varnish. Of
course the lines with listen 80 are changed to listen 8080, and when I
restart nginx, it appears on ports 80, 8080 and 443.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,265791,265796#msg-265796
OK, was trying to keep the post relevant and succinct, but here goes with
the config. Its a newly set up server, so pretty much standard.
=
# cat nginx.conf
user www-data;
worker_processes auto;
pid /run/nginx.pid;
events {
worker_connections 768;
# mu
Robert Paprocki Wrote:
---
> Without showing your nginx config it's unlikely that anyone will be able
to
> troubleshoot. Likely there is a stray listen directive that's causing
this.
There are no stray listen directives. I've checked many times.
Hi,
I'm having an odd problem here. I'm trying to set up nginx with a varnish
proxy in front of it. The box is Ubuntu 15.10, nginx 1.9.3, varnish 4.0.3.
For testing I set up varnish on port 8080, and nginx was running on port 80
and 443. I shut down both, edit the config files so that varnish is
