PiPass / blockpage

A temporary unblock solution and blockpage for your Pi-Hole system
BSD 3-Clause "New" or "Revised" License
196 stars 14 forks source link

Redirection Infinite Loop / Landing Page Never Loads #62

Closed advra closed 4 years ago

advra commented 4 years ago

I am able to access admin control panel of pihole fine at 192,168.1.2/admin however when accessing a website that has been blocked (in my case wololo.net) I get an infinite redirect loop (http://www.wololo.net/192.168.1.2/blocked/?url=www.wololo.net). I never see the PiPass landing page.

Any idea what I may be doing wrong? I have pihole installed in default location. Upon PiPass install I directed the document root location to /var/www/html which is where the admin and pihole folders reside.

image

roenw commented 4 years ago

Can you post the config.php file?

On Sat, Jan 4, 2020 at 11:43 AM, Adrian Alonzo notifications@github.com wrote:

I am able to access admin control panel of pihole fine at 192,168.1.2/admin however when accessing a website that has been blocked (in my case msn.com) I get an infinite redirect loop (http://msn.com/?url=msn.com). I never see the PiPass landing page.

Any idea what I may be doing wrong? I have pihole installed in default location. Upon PiPass install I directed the document root location to /var/www/html which is where the admin and pihole folders reside.

image

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

advra commented 4 years ago
<?php
/*
For your PiPass system to function properly, it's reccomended that you
modify all of these variables to appropriate values. An explanation of
each variable is listed as a comment below the variable.

NOTE: All PiPass files are dependent upon this one configuration file. Your 
changes will be widespread!
*/

$conf['show_tech_info'] = true;
// Should usually be set to true, unless you have specific reason to disable
// it. Determines whether the program should show technical info.

$conf['blockpage_url'] = "192.168.1.2/blockedpage/";
// The URL (not directory) of your blockpage. Setting this incorrectly can
// lead to SSL certificate SAN errors, which prompt the user that the
// connection is "not secure." It's highly reccomended that you change this.
// Example: "https://example.com/blockpage/"

$conf['unblock_url'] = "unblock-exec";
// In most cases this does not have to be changed. Only change it if your
// unblock page resides in a subpath which is not "unblock-exec"

$conf['safeurl'] = "about:home";
// Enter a URL of your choice to go to when a user clicks "back to safety"
// This should not be a directory.

$conf['adminemail'] = "adrian@gmail.com,";
// Your email. Used when a user requests a permanent unblock.

$conf['timezone'] = date_default_timezone_set("America/New_York");
// Your timezone. Used when displaying technical info.

$conf['date'] = date('m/d/Y h:i:s a', time());
// Format in which the date/time is presented to end users.

$conf['unblock_seconds'] = 604800;
// How many seconds to unblock a website for when a temporary unblock is
// executed by a user.

$conf['time_friendly'] = "1 week";
// A way of saying the amount of unblock seconds in english.
// For example, 300 seconds would equal 5 minutes.

$conf['pipass_v'] = "1.3";
// PiPass current version. Must be a NUMBER! Or else "update available" 
// will be showing forever and you will get a HEADACHE trying to debug.
?>
advra commented 4 years ago

Oh my apologies.. I needed to prepend http:// to the front. Changing it to the line below works:

$conf['blockpage_url'] = "http://192.168.1.2/blockedpage/";