Hello,

I'm trying to get HTTPS to work on my TL-SG3210 switch.

Unfortunately I'm not able to get a certificate chain working with the HTTPS module.

I tried the following two formats:

Bag Attributes
    localKeyID: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
    friendlyName: XXXXXXXXXXXX
subject=/C=<COUNTRY_CODE>/ST=stateOrProvinceName/L=Locality/O=Organisation/CN=xxxx/emailAddress=email
issuer=/C=<COUNTRY_CODE>/ST=stateOrProvinceName/L=Locality/O=Organisation/CN=domains CA/emailAddress=email
-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----
Bag Attributes: <No Attributes>
subject=/C=<COUNTRY_CODE>/ST=stateOrProvinceName/L=Locality/O=Organisation/CN=domains CA/emailAddress=email
issuer=/C=<COUNTRY_CODE>/ST=stateOrProvinceName/L=Locality/O=Organisation/CN=root CA/emailAddress=email
-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----
Bag Attributes: <No Attributes>
subject=/C=<COUNTRY_CODE>/ST=stateOrProvinceName/L=Locality/O=Organisation/CN=root CA/emailAddress=email
issuer=/C=<COUNTRY_CODE>/ST=stateOrProvinceName/L=Locality/O=Organisation/CN=root CA/emailAddress=email
-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----
Bag Attributes
    localKeyID: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
    friendlyName: XXXXXXXXXXXX
Key Attributes: <No Attributes>
 

And one without attributes:

-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----
 

In both cases, the file gets rejected.

If I only provide one certificate in the file, it works.

This guide talks about the format which certificates need to have.

It only says that 

-----BEGIN CERTIFICATE-----
*
-----END CERTIFICATE-----

Is supported.

Is it possible to have the switch use a certificate with a chain instead of just a certificate?

Kind regards