This definitely took me way longer than it should have... but at least I finally have Homepage & Nebula Sync working with Pi-Hole v6

Some of the "tricky"parts that caused me a few hours of troubleshooting & headaches was because I use nginx as my reverse proxy & instead of Pi-Hole having a different setup that the rest of what's running on that device, I wanted it to use nginx too.

The first thing I had to do was update my nginx config to include the below:

...
    location /admin {
        proxy_pass http://{IP_Address}:{Port}/admin;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_hide_header X-Frame-Options;
        proxy_set_header X-Frame-Options "SAMEORIGIN";
        proxy_read_timeout 90;
    }

    location /api {
        proxy_pass http://{IP_Address}:{Port}/api;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_hide_header X-Frame-Options;
        proxy_set_header X-Frame-Options "SAMEORIGIN";
        proxy_read_timeout 90;
    }

        location / {
                proxy_pass http://{IP_Address}:{Port}/admin/;
                proxy_http_version 1.1;
                proxy_set_header Host $http_host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;

                client_max_body_size 0;
                add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload";
        }
}
...

I had seen a few posts mentioning making the above change, but what I must have been missing was having the "location /" at the end, instead of before /admin or /api.

While I continued testing Homepage to get the details to display on my dashboard, I noticed one of the errors was a failed lookup for my Pi-Hole domain name. I configured the Docker compose file to use my local network DNS to resolve that. I also had to play around with the API Key vs. App Password to figure out what the correct one was for Homepage. It ended up being the latter.

Then, Nebula Sync was at least connecting successfully, I still just needed to make the changes to the App Password, setting my local network DNS, & enable a setting that would allow services using the App Password to make changes (so that the replica device would actually be set with the same settings as the primary): webserver.api.app_sudo

Hopefully things are actually working as expected now, but we shall see what else might be broken that I didn't find yet 🙃