View Attach (2) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
jpg
 sni_https_port.jpg 629.5 kB 1 05-Dec-2023 05:32 Ada Csaba
jpg
 sni_portecle.jpg 101.0 kB 1 05-Dec-2023 05:32 Ada Csaba

This page (revision-12) was last changed on 05-Dec-2023 05:32 by krivacsz

This page was created on 05-Dec-2023 05:32 by Ada Csaba

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 5 changed 2 lines
1.)
Edit the HTTPS server_item in your prefs page, advanced tab. Enable the SNI checkbox. Then it will be SNI ready and can be used.
1.) Edit the HTTPS server_item in your prefs page, advanced tab. Enable the SNI checkbox. Then it will be SNI ready and can be used.\\
At line 8 changed 2 lines
2.)
On the HTTPS port, you need a keystore specified...it can be anything generic, but I suggest putting in www.domain1.com stuff in it...its name must be "main.jks". The name is important to follow along with the example.
Now you have two different methods you can do for keystore management. Either one global keystore in JKS format with all private keys and certificates in it, or multiple keystores each with a single private key certificate in it.
At line 11 changed 2 lines
3.)
Now you need two other files. www.domain1.com_main.jks and www.domain2.com_main.jks All files should be in the same folder that you specified for main.jks. Each should have their own set of keystore info, do not put multiple in one keystore as that is not how the system is designed. They must all use the same passwords too.
!Method #1
Download and use the tool named "Portecle". Use it to create multiple private keys, import trusted certificates, import CA reply files. This method can support wildcard certificates mixed with other domain certificates too as pattern matching is allowed on t he certificate alias names. Then configure the HTTPS port to use this one keystore like normal.
---
!Method #2
1.) On the HTTPS port, you need a keystore specified...it can be anything generic, but I suggest putting in www.domain1.com stuff in it...its name must be "main.jks". The name is important to follow along with the example.\\
At line 15 added 2 lines
2.) Now you need two other files. www.domain1.com_main.jks and www.domain2.com_main.jks All files should be in the same folder that you specified for main.jks. Each should have their own set of keystore info, do not put multiple in one keystore as that is not how the system is designed. They must all use the same passwords too.\\
Version Date Modified Size Author Changes ... Change note
12 05-Dec-2023 05:32 2.308 kB krivacsz to previous
11 05-Dec-2023 05:32 2.27 kB Ada Csaba to previous | to last
10 05-Dec-2023 05:32 2.268 kB Ada Csaba to previous | to last
9 05-Dec-2023 05:32 2.273 kB Ada Csaba to previous | to last
8 05-Dec-2023 05:32 2.214 kB Ada Csaba to previous | to last
7 05-Dec-2023 05:32 2.214 kB Ada Csaba to previous | to last
6 05-Dec-2023 05:32 2.098 kB Ada Csaba to previous | to last
5 05-Dec-2023 05:32 1.982 kB Ben Spink to previous | to last
4 05-Dec-2023 05:32 1.357 kB Ben Spink to previous | to last
3 05-Dec-2023 05:32 1.385 kB Ben Spink to previous | to last
2 05-Dec-2023 05:32 1.315 kB Ben Spink to previous | to last
1 05-Dec-2023 05:32 1.05 kB Ada Csaba to last Server Name Inclusion (SNI)
« This page (revision-12) was last changed on 05-Dec-2023 05:32 by krivacsz
G’day (anonymous guest)
CrushFTP11 | What's New

Referenced by
HTTP(S)

JSPWiki