Hello again,
I'm having a few issues with the portal config after getting so close to a
clean upgrade (following the SAML.pm fun)
One of my latest torments (I'll keep it to one at a time) is the portal
apache instance binding to 127.0.0.1 in stead of our registration vlan
interface.
We hard coded it to the correct interface here:
https://github.com/inverse-inc/packetfence/blob/589a37c05ad1e6cb1ea57116c5d9c3920489749b/lib/pf/services/manager/httpd_portal.pm#L105
Which generated a slightly more sane version of :
/usr/local/pf/var/conf/httpd.conf.d/httpd.portal
but we still get a 503 when attempting to load the portal page. Where is a
good place to look for the portal complaints? I'm finding relevant logs
hard to pin down..
Something that may or may not be a factor, is that when attempting to add
portal as an "additional listening daemon" under
yourserver:1443/admin/configuration#configuration/networks/interfaces it
simply will not save, whereas adding radius will do. Again, cause of
failure somewhat unclear!
Thanks in advance,
David
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
