Please follow the below template, it will help us to help you!
Hi, since all of the other threads are locked, I had to start a new one. I have the same issue as most of you lately. I am running a server with 5 nginx instances, and all of them have certificates (https only accessable), without PiHole, which I intended to be only local, as I got hacked thru PiHole several times in the past. No matter what I get 403 Forbidden error. Reinstalled PiHole, changed ports and stuff, even I wrote a whole new Nginx config for PiHole without the deny rules. Can you guys tell us what you have changed, so most of us users get the same error, cuz maybe if we know, we would find solutions by our selves? I hope I didn't insulted anyone. I very much like your software! Thanks in advance.
P.S. ports 80 and 443 are taken by nginx. That's what the debug tool tells me.
I've just reinstalled the PiHole. Issue persists. Also tried downgrading the branches. the web interface started working, also it blocked ads aswell, but there were some errors, and I reinstalled, which got me to 403 again. It's not port related, as I tried changing them.
[webserver]
domain = "pi.hole"
acl = ""
port = "80o,443os,[::]:80o,[::]:443os"
And, as the logs note,
[✗] tcp:0.0.0.0:443 is in use by nginx (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:0.0.0.0:80 is in use by nginx (https://docs.pi-hole.net/main/prerequisites/#ports)
Bro, I've tried like 10 different ports, which aren't used by anything. As I told already, I have some other services on the same server. Never had an issue before. I've tried on a RPI, which I have laying arround with a clean install of Ubuntu and latest PiHole using Nginx. By default after I install PiHole, I get 403?!, but then if I change the port to 81 in PiHole toml and leave 80 in the nginx instance corresponding to Pihole it works. This is not convenient by any standard and it has no logic at all... How can direct path lead to nowhere, while a non-existent path works?
Nginx config isn't working at all with PiHole 6.+. I have set who am I allowing to see the web interface and who can't. Setting PiHole on port, which is not corresponding in it's Nginx config, is useless.
On my server, which I intend to have PiHole installed, when I do this, I get 403 as I said earlier. On a RPI, which only has - clean Ubuntu, Clean PiHole and Nginx installed - IT DOES WORK. I realy don't know which is the culprit here. PHP or the web server?
Is there any chance I somehow install the previous version of PiHole and call it a win, cuz I did invest alot of time banging my head here.... Sorry, but all this is just not worth it.
You just don't care at all, do you? Ofcourse I searched your forum, and after all of the "fixes" provided didn't work for me, I opened a new thread. What I found was "why my nginx isn't working on 6 BETA".
Pi-hole works just fine per your own admission. It's your nginx setup that needs to be fixed. Take that as a semi-polite way of saying "It's not us, it's you."
Hey Mr 'Not-Bro'. This is me after a couple of weeks politely telling you, that PiHole 6 doesn't block ads anymore. Regex filters doesn't work, as they used to. Adlists, which were present in 5, don't work either. I'm not looking for a fix. I just wanted you to know that. All the best!
Please point out the part where you were "polite." I surely can't find it.
Since it's working for most everyone else (even with nginx), you most certainly have a configuration error. They issued notes that things would have to be changed to work as before, but it does work.