FWIW, I also get the same bad request error after forcing apt with:
dpkg -i --ignore-depends=python-django-bootstrap3
packetfence-pki_1.0.4_all.deb
On Thu, Jun 22, 2017 at 4:06 PM, David Harvey <[email protected]>
wrote:
> Hi packetfence users,
>
> I've been attmepting to experiment with packetfence-pki, but have fallen
> at the first hurdle. Namely there doesn't seem to be a Debian Jessie
> package avialable as advertised at https://packetfence.org/
> doc/PacketFence_PKI_Quick_Install_Guide.html (section 3.1)
> http://inverse.ca/downloads/PacketFence/debian/pool/jessie/p/
>
> I attempted to install the generic deb, but predictably it wouldn't accept
> the pip installed version of django-bootstrap3 as apt doesn't know about
> "python-django-bootstrap3".
>
> Attempted to install from source
> <https://github.com/inverse-inc/packetfence-pki> which looked promising
> until there was no service file that came with make install, so using an
> init.d script (/etc/init.d/packetfence-pki.dpkg-new) admittedly origin
> unknown I managed to get to complaints over
> /usr/local/packetfence-pki/conf/server.crt and
> /usr/local/packetfence-pki/conf/server.key.
> I dutifully copied the packetfence ones, and although the service starts, I
> get a bad request 400 error when visiting https://server:9393.
>
> Now I understand I've mangled the instructions massively, so is there
> a) A correct way to do this on Jessie any more?
> b) A way of breathing life into my Frankenstein's monster?
>
> 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
