PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001769PacketFencecaptive portalpublic2014-02-11 07:312014-02-14 11:14
ReportererSitzt 
Assigned Tofdurand 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformLinuxOSUbuntuOS Version12.04.3 LTS
Product Version4.1.0 
Target VersionFixed in Version+1 
fixed in git revisionhttps://github.com/inverse-inc/packetfence/commit/57122f4dc4bdf4d73e64335f66519a1f0a889ce2 [^]
fixed in mtn revision
Summary0001769: Proxy Interception : 503 Service Unavailable
DescriptionI've enabled proxy interception for the default ports 8080 and 3128 and seems to work with regard to the log entries and the url changing to the packetfence fqdn.

But instead of the captive portal i get a
503 Service Unavailable Error

/etc/hosts has 127.0.0.1 for the fqdn of packetfence
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files? reverse_reproxy_error_log (681,741) 2014-02-11 07:49
https://www.packetfence.org/bugs/file_download.php?file_id=199&type=bug
? proxy_error_log (2,432) 2014-02-11 07:49
https://www.packetfence.org/bugs/file_download.php?file_id=200&type=bug
Issue History
Date ModifiedUsernameFieldChange
2014-02-11 07:31erSitztNew Issue
2014-02-11 07:45erSitztNote Added: 0003504
2014-02-11 07:49erSitztFile Added: reverse_reproxy_error_log
2014-02-11 07:49erSitztFile Added: proxy_error_log
2014-02-11 07:50erSitztNote Added: 0003505
2014-02-11 11:47fdurandNote Added: 0003506
2014-02-14 04:34erSitztNote Added: 0003507
2014-02-14 11:14fdurandfixed in git revision => https://github.com/inverse-inc/packetfence/commit/57122f4dc4bdf4d73e64335f66519a1f0a889ce2 [^]
2014-02-14 11:14fdurandStatusnew => resolved
2014-02-14 11:14fdurandFixed in Version => +1
2014-02-14 11:14fdurandResolutionopen => fixed
2014-02-14 11:14fdurandAssigned To => fdurand

Notes
(0003504)
erSitzt   
2014-02-11 07:45   
Just noticed that there are new logfiles:

proxy_error_log:
[Mon Feb 10 16:38:56 2014] [warn] proxy: No protocol handler was valid for the URL 127.0.0.1:444. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.

I've attached the error-logs as well
(0003505)
erSitzt   
2014-02-11 07:50   
In reverse_reproxy_error_log it looks like packetfence is trying to connect to 127.0.0.1:443 but nobody is listening there...

netstat -anp | grep 127.0.0.1
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1368/mysqld
tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 1162/memcached
tcp 0 0 127.0.0.1:444 0.0.0.0:* LISTEN 23968/apache2
tcp 0 0 127.0.0.1:9090 0.0.0.0:* LISTEN 23931/apache2
tcp 0 0 127.0.0.1:48460 127.0.0.1:11211 ESTABLISHED 24007/pfsetvlan
tcp 0 0 127.0.0.1:48448 127.0.0.1:11211 ESTABLISHED 23931/apache2
tcp 0 0 127.0.0.1:11211 127.0.0.1:48450 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:48462 127.0.0.1:11211 ESTABLISHED 24049/pfdhcplistene
tcp 0 0 127.0.0.1:11211 127.0.0.1:48463 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:48463 127.0.0.1:11211 ESTABLISHED 24048/pfdhcplistene
tcp 0 0 127.0.0.1:48535 127.0.0.1:11211 ESTABLISHED 23918/apache2
tcp 0 0 127.0.0.1:48457 127.0.0.1:11211 ESTABLISHED 23988/pfdns
tcp 0 0 127.0.0.1:11211 127.0.0.1:48454 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48480 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48448 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:48450 127.0.0.1:11211 ESTABLISHED 23948/apache2
tcp 0 0 127.0.0.1:48461 127.0.0.1:11211 ESTABLISHED 24050/pfdhcplistene
tcp 0 0 127.0.0.1:48444 127.0.0.1:11211 ESTABLISHED 23909/apache2
tcp 0 0 127.0.0.1:48454 127.0.0.1:11211 ESTABLISHED 23968/apache2
tcp 0 0 127.0.0.1:11211 127.0.0.1:48460 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48461 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48536 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48444 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:48536 127.0.0.1:11211 ESTABLISHED 23924/apache2
tcp 0 0 127.0.0.1:11211 127.0.0.1:48457 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48462 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:11211 127.0.0.1:48535 ESTABLISHED 1162/memcached
tcp 0 0 127.0.0.1:48480 127.0.0.1:11211 ESTABLISHED 24084/perl
udp 0 0 127.0.0.1:18120 0.0.0.0:* 23996/freeradius
udp 0 0 127.0.0.1:11211 0.0.0.0:* 1162/memcached
udp 0 0 127.0.0.1:161 0.0.0.0:* 1447/snmpd
(0003506)
fdurand   
2014-02-11 11:47   
Hello,
i have just tested and in fact you have to change in /etc/hosts file to resolv on the ip address where the portal is listening and not 127.0.0.1.

I will change the documentation.

Regards
Fabrice
(0003507)
erSitzt   
2014-02-14 04:34   
Changed the fqdn in /etc/hosts to the ip of packetfence in the registration network and it works just fine now.
Thanks