Notes |
|
|
You enter your credentials on the login page, click the login button, and get an empty page?
Share your log entries when this happens. |
|
|
(0003430)
|
muhlig
|
2013-08-23 12:23
(edited on: 2013-08-27 07:08) |
|
After I click login button I get, depending on browser, empty page or message like "no network connection" or "page not available" or something like that. Before (PF 4, but earlier) I got nice release page and later redirect page.
|
|
|
(0003431)
|
muhlig
|
2013-08-27 02:21
(edited on: 2013-08-27 07:07) |
|
Francis, looks like I've found a difference between correct state of PacketFence and incorrect one. When using PF 4.0.5-2, portal_access_log shows just one line while registering node and release page doesn't show:
192.168.29.11 - - [27/Aug/2013:07:41:39 +0200] "POST /authenticate HTTP/1.1" 302 264 "https://pfhost.example.com/captive-portal" [^] "Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36"
This is HTTP 302 redirect "Moved temporarily".
However when using some older version (probably 4.0.2 devel) I can see two lines while registering and release page shows:
192.168.29.11 - - [27/Jun/2013:09:33:10 +0200] "POST /authenticate HTTP/1.1" 200 8100 "https://pfhost.example.com/captive-portal" [^] "Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36"
192.168.29.11 - - [27/Jun/2013:09:33:44 +0200] "POST /authenticate HTTP/1.1" 200 8100 "https://pfhost.example.com/authenticate" [^] "Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36"
Moreover, there is no redirect, the pages are just produced.
And, I found also in the older version there are portal_access_log lines present like this one:
192.168.29.11 - - [08/Aug/2013:13:36:32 +0200] "GET /access?destination_url=http%3A%2F%2Fwww.example.com%2F HTTP/1.1" 200 3089 "-" "Mozilla/5.0 (Windows NT 6.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36"
In fact these lines don't exist in the newer version. I assume $URL_ACCESS doesn't work at all:
RewriteRule ^%%URL_ACCESS%%$ /cgi-perl/register.cgi?mode=release [PT,QSA]
and I found too in the older version there are two register.cgi calls during registration:
Aug 07 12:10:22 register.cgi(0) INFO: 192.168.29.11 - 00:22:19:e7:e0:90 on registration page (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_html_captive_2dportal_register_2ecgi::handler)
Aug 07 12:10:23 register.cgi(0) INFO: 192.168.29.11 - 00:22:19:e7:e0:90 on registration page (ModPerl::ROOT::ModPerl::PerlRun::usr_local_pf_html_captive_2dportal_register_2ecgi::handler)
while in the newer version there is only one.
Hope it helps to find this annoying problem.
|
|
|
(0003432)
|
muhlig
|
2013-08-28 03:52
(edited on: 2013-08-28 07:23) |
|
Actually I've investigated the problem and found the last lines executed are lib/pf/web.pm end_portal_session sub lines 682 & 683:
print $portalSession->cgi->redirect(
"http://".$Config{'general'}{'hostname'}.".".$Config{'general'}{'domain'} [^]
.'/access?destination_url=' . uri_escape($destination_url)
);
exit(0);
The value of argument is:
http://packetfencehost.example.com/access?destination_url=http%3A%2F%2Fwww.example.com%2F [^]
This page can't be displayed. Why?
I've also found in rewrite.log lines like this one:
192.168.29.11 - - [28/Aug/2013:07:56:08 +0200] [packetfencehost.example.com/sid#7fb263354f60][rid#7fb263966df8/initial] (3) applying pattern '^/authenticate$' to uri '/authenticate'
but there are no lines with pattern '^/access$' applied to uri '/access' .
So I assume portal session module doesn't generate /access request. Why?
|
|
|
(0003959)
|
lmunro
|
2015-02-18 11:24
|
|
Not a bug.
Please use the mailing list for support questions. |
|