CyberHosting

How to set a "ln -s" link for the panel's ssl?

After I installed the ssl for my website, I found I still could not visit https://domain.tld:8090 as I did with https://domain.tld since the panel is with its own cert.

My idea is that I need to set a ln -s for the panel, making it using the ssl of my website, and I don't have to visit the panel by ip addr but by the registered domain.

I don't know where the existing ssl/certs are located on the hard drive because I made the installation by filling in the content of the certs into the ssl addition textboxes.

Could anybody be kindly to tell me where to find these files? the existing ssl certs for the domain and the certs of the panel?

Comments

  • @usmannasir said:
    You don't need to do that manually, read more details: http://docs.cyberpanel.net/doku.php?id=cyberpanel-on-ssl

    Thank you, usmannasir.

    If I understand you correctly, the referred link from the Docs suggests the website obtain another ssl cert from Letsencrypt, for example, a cert for http://www.domain.tld, and a different cert for http://panel.domain.tld ?

    My situation is, I somewhat want to keep the domains simple. When the users visit https://domain.tld, they visit my homepage, and when I visit https://domain.tld:8090, I visit my panel.

    Since I did obtain a set of cert files from Letsencrypt, it's not possible for me to get another set again for the same domain just with different ports.

    And, I filled in the ssl text boxes yesterday with the content of my cert and key, but after a while when I clicked open the text boxes, the filled in contents were gone?

  • Hello!

    If you issue hostname SSL for domain.com and it already has an SSL (from any part of control panel) , CyberPanel is not going to issue another Letsencrypt SSL for this domain, rather just copy the currently issued SSL to:

    /usr/local/lscp/cert.pem
    /usr/local/lscp/key.pem

    This is the SSL location for port 8090, and if SSL is not already issued for this domain, a new SSL will be issued.

    So you need not worry about that, and when you 'Add SSL' to apply your own custom SSL for a domain it does not fetch current SSL files from server, however it just saves the ssl.

    Regards

  • Thank you, usmannasir. Now I understand.

    I thought the term 'issue' only means issuing from Letsencrypt. In my idea, issuing from the same server is 'copying'.

  • rm -f /usr/local/lscp/cert.pem
    rm -f /usr/local/lscp/key.pem

    ln -s /etc/letsencrypt/domain.com/live/fullchain.pem /usr/local/lscp/cert.pem
    ln -s /etc/letsencrypt/domain.com/live/privkey.pem /usr/local/lscp/key.pem

    Works for me.
  • Sorry, should have been:

    rm -f /usr/local/lscp/conf/cert.pem
    rm -f /usr/local/lscp/conf/key.pem

    ln -s /etc/letsencrypt/yourdomain.com/live/fullchain.pem /usr/local/lscp/conf/cert.pem
    ln -s /etc/letsencrypt/yourdomain.com/live/privkey.pem /usr/local/lscp/conf/key.pem
  • Should be:
    ln -s /etc/letsencrypt/live/domain.com/fullchain.pem /usr/local/lscp/conf/cert.pem
    ln -s /etc/letsencrypt/live/domain.com/privkey.pem /usr/local/lscp/conf/key.pem
Sign In or Register to comment.
CyberPanel Discord

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!