# Another 403 after 6.0+ upgrade

**URL:** <https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714>\
**Category:** Help\
**Created:** [April 1, 2025, 6:21pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714 "2025-04-01T18:21:42Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 6:21pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/1 "2025-04-01T18:21:42Z")

</div>

#### 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.

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [April 1, 2025, 6:35pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/3 "2025-04-01T18:35:20Z")

</div>

> [@dtrax](#):
>
> Can you guys tell us what you have changed

If you are asking what was changed from **Pi-hole v5** to **Pi-hole v6.0** , you need to read the Release Notes. There were lots of changes.

If you are asking what was changed in the last update (v6.1), the answer is: Nothing related to the web server ports.

* * *

Can you please upload a debug log (and post here **only the Token** ) so we can help you find what is wrong in your specific case?

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 7:03pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/4 "2025-04-01T19:03:11Z")

</div>

Hi, thanks for the quick reply. Here is the token - [https://tricorder.pi-hole.net/nmimOGRN/](https://tricorder.pi-hole.net/nmimOGRN/)

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.

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [April 1, 2025, 10:17pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/5 "2025-04-01T22:17:01Z")

</div>

> [@dtrax](#):
>
> It's not port related, as I tried changing them.

Not according to the debug log.

```plaintext
   [webserver]
     domain = "pi.hole"
     acl = ""
     port = "80o,443os,[::]:80o,[::]:443os"

```

And, as the logs note,

```plaintext
[✗] 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)

```

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 10:41pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/6 "2025-04-01T22:41:13Z")

</div>

> [@DanSchaper](#):
>
> Not according to the debug log.
> 
> ```auto
> 
> ```

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?

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [April 1, 2025, 10:51pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/7 "2025-04-01T22:51:11Z")

</div>

You are still getting 403 because the web server can't start if you try to use ports already in use.

Try to change the ports to 8080 and 8443 running this command:

```auto
sudo pihole-FTL --config webserver.port '8080o, 8443os'

```

Then try to access the web interface using one of the URLs below:

- [http://192.168.1.111:8080/admin](http://192.168.1.111:8080/admin)
- [https://192.168.1.111:8443/admin](https://192.168.1.111:8443/admin)
- [http://pi.hole:8080/admin](http://pi.hole:8080/admin)
- [https://pi.hole:8443/admin](https://pi.hole:8443/admin)

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 10:51pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/8 "2025-04-01T22:51:44Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [April 1, 2025, 10:53pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/9 "2025-04-01T22:53:42Z")

</div>

If you want to use `nginx` as reverse proxy, first you need to start Pi-hole web server and access the web interface using the links I posted above.

If this works, then you can try to change `nginx` configuration.

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 10:55pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/10 "2025-04-01T22:55:07Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [April 1, 2025, 10:56pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/11 "2025-04-01T22:56:36Z")

</div>

> [@dtrax](#):
>
> PHP or the web server?

There is no PHP in Pi-hole v6.

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 10:57pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/12 "2025-04-01T22:57:30Z")

</div>

> [@rdwebdesign](#):
>
> If you want to use `nginx` as reverse proxy, first you need to start Pi-hole web server and access the web interface using the links I posted above.

Bro, my previous installation of PiHole (5.x.x), had all that and had NO ISSUES! 6 doesn't want to work with nginx configuration.

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 10:59pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/13 "2025-04-01T22:59:41Z")

</div>

> [@rdwebdesign](#):
>
> There is no PHP in Pi-hole v6.

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.

---

<div class="post-metadata">

**Author:** ![rdwebdesign](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/rdwebdesign/32/51363_2.png) [@rdwebdesign](https://discourse.pi-hole.net/u/rdwebdesign)\
**Post date:** [April 1, 2025, 11:00pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/14 "2025-04-01T23:00:01Z")

</div>

> [@dtrax](#):
>
> Bro, my previous installation of PiHole (5.x.x), had all that and had NO ISSUES! 6 doesn't want to work with nginx configuration.

Now I'm sure you didn't read the [Release Notes for Pi-hole v6](https://discourse.pi-hole.net/t/introducing-pi-hole-v6/75863) and you also didn't search the forum for `nginx` configuration for Pi-hole v6.

Your `nginx` configuration for "PiHole (5.x.x)" won't work for Pi-hole v6. You will need to create a new one.

**EDIT:**  
This is just one of the examples of `nginx` configurations users are using with v6:

> [@Can't get v6 webinterface behind nginx reverse proxy to work](https://discourse.pi-hole.net/t/cant-get-v6-webinterface-behind-nginx-reverse-proxy-to-work/76231/4):
>
> Thanks! I just wanted to object because a location / with proxy\_pass http://127.0.0.1:8001/; should reverse proxy all paths including /admin... But weirdly, this config works, setting up two separate reverse proxies for /admin and /api So this is the full config I now use: server { listen 192.168.0.1:80; listen [::]:80 ; server\_name pi-hole.home; location / { return 301 $scheme://$host/admin/; } location /admin/ { …

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 1, 2025, 11:06pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/15 "2025-04-01T23:06:17Z")

</div>

> [@rdwebdesign](#):
>
> Now I'm sure you didn't read the Release Notes for Pi-hole v6 and you also didn't search the forum for `nginx` configuration for Pi-hole v6.

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".

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [April 1, 2025, 11:08pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/16 "2025-04-01T23:08:39Z")

</div>

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."

Oh, and I'm not your 'Bro'.

---

<div class="post-metadata">

**Author:** ![dtrax](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/d/e0b2c6/32.png) [@dtrax](https://discourse.pi-hole.net/u/dtrax)\
**Post date:** [April 16, 2025, 2:04pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/17 "2025-04-16T14:04:10Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![DanSchaper](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/danschaper/32/91_2.png) [@DanSchaper](https://discourse.pi-hole.net/u/DanSchaper)\
**Post date:** [April 16, 2025, 3:48pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/18 "2025-04-16T15:48:07Z")

</div>

Buh Bye!

---

<div class="post-metadata">

**Author:** ![nprampage](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/n/71c47a/32.png) [@nprampage](https://discourse.pi-hole.net/u/nprampage)\
**Post date:** [April 16, 2025, 8:12pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/19 "2025-04-16T20:12:21Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [May 7, 2025, 8:12pm UTC](https://discourse.pi-hole.net/t/another-403-after-6-0-upgrade/78714/20 "2025-05-07T20:12:38Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.