Hello Akala,

can you check what you have in the packetfence pki logs ?

/usr/local/packetfence-pki/logs

Regards

Fabrice



Le 2017-07-28 à 11:51, Akala Kehinde via PacketFence-users a écrit :
> Hello Antoine,
>
> I still get the error even though the output below looks good:
>
> [root@egelsbach conf]# iptables -S | grep 9393
> -A input-management-if -p tcp -m tcp --dport 9393 -j ACCEPT
> [root@egelsbach conf]# ps -edf | grep packetfence-pki
> root      6108     1  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6111  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6113  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6114  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6116  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6117  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6118  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6120  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6121  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        6122  6108  0 12:36 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> pf        7132  6108  0 12:43 ?        00:00:00 /usr/sbin/httpd -f
> /usr/local/packetfence-pki/conf/httpd.conf
> root     19256 13884  0 17:49 pts/9    00:00:00 grep --color=auto
> packetfence-pki
> [root@egelsbach conf]# iptables -S | grep 9393
> -A input-management-if -p tcp -m tcp --dport 9393 -j ACCEPT
> [root@egelsbach conf]# 
> [root@egelsbach conf]# netstat -nlp | grep 9393
> tcp6       0      0 :::9393                 :::*                  
>  LISTEN      6108/httpd          
> [root@egelsbach conf]# 
>
>
> Regards,
> Kehinde
>
> On Fri, Jul 28, 2017 at 5:50 PM, Akala Kehinde <kehindeak...@gmail.com
> <mailto:kehindeak...@gmail.com>> wrote:
>
>     Hello Antoine,
>
>     I still get the error even though the output below looooks good:
>
>
>
>
>     Regards,
>     Kehinde
>
>     On Fri, Jul 28, 2017 at 3:59 PM, Antoine Amacher via
>     PacketFence-users <packetfence-users@lists.sourceforge.net
>     <mailto:packetfence-users@lists.sourceforge.net>> wrote:
>
>         Hi,
>
>         Can you make sure the pki is properly started,
>
>         ps -edf | grep packetfence-pki
>
>         netstat -nlp | grep 9393
>
>         and that iptables is allowing it:
>
>         iptables -S | grep 9393
>
>         Thanks
>
>
>         On 07/28/2017 06:53 AM, Akala Kehinde via PacketFence-users wrote:
>>         Hello Guys,
>>
>>         I get a Bad Request 400 when I try
>>         accessing https://172.16.100.2:9393/
>>         <https://172.16.100.2:9393/> i.e. the PKI server interface on
>>         PF 7.2.
>>
>>         Any idea what might be wrong?
>>
>>         Regards,
>>         Kehinde
>>
>>
>>         
>> ------------------------------------------------------------------------------
>>         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
>>         PacketFence-users@lists.sourceforge.net
>>         <mailto:PacketFence-users@lists.sourceforge.net>
>>         https://lists.sourceforge.net/lists/listinfo/packetfence-users
>>         <https://lists.sourceforge.net/lists/listinfo/packetfence-users>
>
>         -- 
>         Antoine Amacher
>         aamac...@inverse.ca <mailto:aamac...@inverse.ca>  ::  www.inverse.ca 
> <http://www.inverse.ca> 
>         +1.514.447.4918 x130 <tel:%28514%29%20447-4918>  :: +1 (866) 353-6153 
> x130 <tel:%28866%29%20353-6153>
>         Inverse inc. :: Leaders behind SOGo (www.sogo.nu 
> <http://www.sogo.nu>) and PacketFence (www.packetfence.org 
> <http://www.packetfence.org>)
>
>
>         
> ------------------------------------------------------------------------------
>         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
>         PacketFence-users@lists.sourceforge.net
>         <mailto:PacketFence-users@lists.sourceforge.net>
>         https://lists.sourceforge.net/lists/listinfo/packetfence-users
>         <https://lists.sourceforge.net/lists/listinfo/packetfence-users>
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
> PacketFence-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/packetfence-users

-- 
Fabrice Durand
fdur...@inverse.ca ::  +1.514.447.4918 (x135) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org) 

------------------------------------------------------------------------------
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
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to