The let’s encrypt integration with PF is pretty simple, it’s baed of the HTTP 
challenge.

If you want to use let’s encrypt service, your DNS name 
self-service.dangote-group.con needs to resolve a public IP address that is 
bind to the management interface over 443 and 80.

Thanks,

Ludovic Zammit
Product Support Engineer Principal

Cell: +1.613.670.8432
Akamai Technologies - Inverse
145 Broadway
Cambridge, MA 02142
Connect with Us:         <https://community.akamai.com/>  
<http://blogs.akamai.com/>  <https://twitter.com/akamai>  
<http://www.facebook.com/AkamaiTechnologies>  
<http://www.linkedin.com/company/akamai-technologies>  
<http://www.youtube.com/user/akamaitechnologies?feature=results_main>

> On May 19, 2021, at 1:29 PM, Ezeh Victor <vickeyzed...@gmail.com> wrote:
> 
> HIi,
> 
> My packetfence version is v10.2.0.
> 
> I tried using the GUI to upload the required files.
> the private key generated when generating a .csr file was used in conjunction 
> with the .crt file and this was the error message
> 
> <image.png>
> 
> Generating the .csr from the GUI does not generate a private key to be used 
> in filling the data requirements.
> 
> How can I tackle this?
> 
> Also, trying out the let's encrypt option gives this error when testing 
> public access
> 
> <image.png>
> 
> What is the procedure to use either?
> 
> On Wed, 19 May 2021 at 13:00, Zammit, Ludovic <luza...@akamai.com 
> <mailto:luza...@akamai.com>> wrote:
> Hello,
> 
> Which PacketFence version are you using ? If it’s a version > v10 use the GUI 
> for it, otherwise, the server.pem is a bundle of : server.key server.crt and 
> intermediates if any.
> 
> Thanks,
> 
> Ludovic Zammit
> Product Support Engineer Principal
> 
> Cell: +1.613.670.8432
> Akamai Technologies - Inverse
> 145 Broadway
> Cambridge, MA 02142
> Connect with Us:       <https://community.akamai.com/>  
> <http://blogs.akamai.com/>  
> <https://urldefense.com/v3/__https://twitter.com/akamai__;!!GjvTz_vk!EcqHJUqV-wetV_DNm6yHnvvryi_qAFOdRAAcDbLbwCFp561F3FVPuGjCi8Wzbg$>
>   
> <https://urldefense.com/v3/__http://www.facebook.com/AkamaiTechnologies__;!!GjvTz_vk!EcqHJUqV-wetV_DNm6yHnvvryi_qAFOdRAAcDbLbwCFp561F3FVPuGi5eEi6EA$>
>   
> <https://urldefense.com/v3/__http://www.linkedin.com/company/akamai-technologies__;!!GjvTz_vk!EcqHJUqV-wetV_DNm6yHnvvryi_qAFOdRAAcDbLbwCFp561F3FVPuGjd3VOgFg$>
>   
> <https://urldefense.com/v3/__http://www.youtube.com/user/akamaitechnologies?feature=results_main__;!!GjvTz_vk!EcqHJUqV-wetV_DNm6yHnvvryi_qAFOdRAAcDbLbwCFp561F3FVPuGg54xdavA$>
> 
>> On May 19, 2021, at 4:23 AM, Ezeh Victor via PacketFence-users 
>> <packetfence-users@lists.sourceforge.net 
>> <mailto:packetfence-users@lists.sourceforge.net>> wrote:
>> 
>> Hi,
>> 
>> I have been having an issue using a third-party SSL certificate on PF for 
>> the captive portal.
>> 
>> Based on the documentation, the directive was to change the server.crt and 
>> server.key files in the /usr/local/pf/conf/ssl/ folder.
>> 
>> I generated the server.csr file using openssl req -new -newkey rsa:2048 
>> -nodes -keyout server.key -out server.csr. command
>> 
>> I renamed the corresponding files to server.crt and server.pem and copied 
>> them to the /usr/local/pf/conf/ssl/ folder and included the server.key file 
>> generated during the server.csr generation.
>> 
>> After doing this, I restarted the haproxy portal for the change to take 
>> effect and it failed until  I replace the server.pem file with the original 
>> one.
>> 
>> Please I need assistance with this.
>> 
>> What am I missing?
>> _______________________________________________
>> PacketFence-users mailing list
>> PacketFence-users@lists.sourceforge.net 
>> <mailto:PacketFence-users@lists.sourceforge.net>
>> https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!C54N4JbJxSylz8oux_xKUlZBH1GUAKLr-30v-tBM_yic5PBVVZ9_bOER9HTRj4iI$
>>  
>> <https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!C54N4JbJxSylz8oux_xKUlZBH1GUAKLr-30v-tBM_yic5PBVVZ9_bOER9HTRj4iI$>
>>  
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to