Update PiHole V6 /api subdomain
#751
Conversation
|
Confirmed that this solution solved the same issue I was facing after upgrading Pi-hole. Thanks! |
|
Worked for me :) I was not able to login on pihole via swag/nginx since I upgraded to v6. Uncommenting the lines on this PR fixed my issue |
that1matt
force-pushed
the
fix-pihole-v6-api
branch
from
73b17d9 to
095ca4c
Compare
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Not stale, just waiting for a CR. |
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Not stale. |
|
Im leaning towards merging #762 in favor of this, as it is more complete with information for the required setup for v6, as well as considering subfolder |
|
This pull request has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Description
Updating to PiHole v6 using a subdomain, caused 500 errors when trying to load the queries page, or make API calls.
Benefits of this PR and context
This change allows for PiHole v6+ to continue to work behind a subdomain reverse proxy.
How Has This Been Tested?
With the current setup, when accessing
/admin/queriesor theQuery Logtab on the right, you would get a pop up showing an error.With this new
/apiblock, theQuery Logloads as expected.Source / References
PiHole v6 Release Notes