-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nginx: [emerg] invalid number of arguments in "upstream" directive in /etc/nginx/conf.d/default.conf:71 #2144
Comments
It's unclear to me whether your
...or your If your
If |
This makes me think that you have a |
@rhansen , that's right: there's also a |
No, it's not. |
Yes, it is the
|
Ah, thanks, I removed it again - I thought it might be missing here. 👍🏼 |
There's a difference between unset and set to the empty string. |
This is set by this Dockerfile:
And
But I don't need to run Pi-hole with nginx-proxy… 🤷🏼♂️ Everything is fine with my Should we also ask the people from Pi-hole to leave this line 34 from |
This is another instance of |
Bugs
I'm using https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/with-nginx-proxy/mariadb/fpm which uses
FROM nginxproxy/nginx-proxy:alpine
via this Dockerfile. I've setVIRTUAL_HOST
and removed all images and rebuild them all. But it still says:Everything was fine until Jan, 18th - before my
docker-compose.yml
worked fine. What did you change that I have overseen and what am I missing?docker exec nameofyournginxproxycontainer nginx -T
My workaround
I "fixed" it and get my NC up and running again by removing these lines within my docker container
fpm_proxy_1
from/etc/nginx/conf.d/default.conf
:There's also #1674 unanswered, hopefully someone will help via an issue!?
The text was updated successfully, but these errors were encountered: