400 Bad Request

marwalmw · July 9, 2019, 1:05pm

Please follow the below template, it will help us to help you!

Expected Behaviour:

[WEB interface should work]

Actual Behaviour:

[WEB interfave is not working - while trying to access 192.168.0.18/admin page, I only get a 400 Bad Request information]

Debug Token:

[ https://tricorder.pi-hole.net/png8haqjbr ]

RamSet · July 9, 2019, 6:23pm

There is a known error with CentOS and lighttpd.

See:

github.com/pi-hole/pi-hole

Accessing http://pi.hole produces "400 Bad Response" error on Fedora 29

opened 10:10PM - 26 Jan 19 UTC

closed 07:26PM - 10 May 20 UTC

golanv

Fixed in next release triage: Issue

**In raising this issue, I confirm the following:** `{please fill the checkboxes…, e.g: [X]}` - [X] I have read and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md). - [X] The issue I am reporting can be *replicated*. - [X] The issue I am reporting isn't a duplicate (see [FAQs](https://github.com/pi-hole/pi-hole/wiki/FAQs), [closed issues](https://github.com/pi-hole/pi-hole/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), and [open issues](https://github.com/pi-hole/pi-hole/issues)). **How familiar are you with the the source code relevant to this issue?:** 1 --- **Expected behaviour:** Accessing http://pi.hole should redirect one to http://pi.hole/admin automatically. **Actual behaviour:** "400 Bad Response" error. Also, the following error message is logged in the lighttpd error log: pihole (response.c.400) uri-path does not begin with '/': pihole/index.php -> 400 **Steps to reproduce:** 1. Install Fedora 29 (or at least lighttpd 1.4.52) 2. Install pihole 3. Go to http://pi.hole **Debug token provided by [uploading `pihole -d` log](https://discourse.pi-hole.net/t/the-pihole-command-with-examples/738#debug):** usxyflu4ki **Troubleshooting undertaken, and/or other relevant information:** Adding an index file in /var/www/html that redirects requests to /pihole/ works to prevent the 400 error. However, it seems like the problem is in the lighttpd.conf file. Assuming that the server.error-handler-404 is still the best way to handle a missing index file, then it's probably better to do a... - server.error-handler-404 = "pihole/index.php" + server.error-handler-404 = "/pihole/index.php" The above change fixes the problem and restores normal functioning. It seems the original configuration worked when I first installed pihole, so perhaps a lighttpd upgrade in Fedora 29 broke this original syntax (which may no longer be supported by lighttpd?). See: https://redmine.lighttpd.net/projects/lighttpd/wiki/Server_error-handler-404Details

Also, see the last post in that thread, the user seems to have a fix for CentOS Core 7

github.com/pi-hole/pi-hole

Accessing http://pi.hole produces "400 Bad Response" error on Fedora 29

opened 10:10PM - 26 Jan 19 UTC

closed 07:26PM - 10 May 20 UTC

golanv

Fixed in next release triage: Issue

**In raising this issue, I confirm the following:** `{please fill the checkboxes…, e.g: [X]}` - [X] I have read and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md). - [X] The issue I am reporting can be *replicated*. - [X] The issue I am reporting isn't a duplicate (see [FAQs](https://github.com/pi-hole/pi-hole/wiki/FAQs), [closed issues](https://github.com/pi-hole/pi-hole/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), and [open issues](https://github.com/pi-hole/pi-hole/issues)). **How familiar are you with the the source code relevant to this issue?:** 1 --- **Expected behaviour:** Accessing http://pi.hole should redirect one to http://pi.hole/admin automatically. **Actual behaviour:** "400 Bad Response" error. Also, the following error message is logged in the lighttpd error log: pihole (response.c.400) uri-path does not begin with '/': pihole/index.php -> 400 **Steps to reproduce:** 1. Install Fedora 29 (or at least lighttpd 1.4.52) 2. Install pihole 3. Go to http://pi.hole **Debug token provided by [uploading `pihole -d` log](https://discourse.pi-hole.net/t/the-pihole-command-with-examples/738#debug):** usxyflu4ki **Troubleshooting undertaken, and/or other relevant information:** Adding an index file in /var/www/html that redirects requests to /pihole/ works to prevent the 400 error. However, it seems like the problem is in the lighttpd.conf file. Assuming that the server.error-handler-404 is still the best way to handle a missing index file, then it's probably better to do a... - server.error-handler-404 = "pihole/index.php" + server.error-handler-404 = "/pihole/index.php" The above change fixes the problem and restores normal functioning. It seems the original configuration worked when I first installed pihole, so perhaps a lighttpd upgrade in Fedora 29 broke this original syntax (which may no longer be supported by lighttpd?). See: https://redmine.lighttpd.net/projects/lighttpd/wiki/Server_error-handler-404Details

system · July 30, 2019, 6:23pm

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