Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: admin.phillipmorrison.com
I ran this command: Logged in using /login
It produced this output: SSL_ERROR_RX_RECORD_TOO_LONG
My web server is (include version): Linode Server-Ubuntu-18.4
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot):
My problem is: the certificate is working fine on site, but I have added an api to the backend which is running on a different port. I copied the nginx page that the cerbot changed when adding the ssl and then changed the server name and port. Then set it up as a new service in systemd. It would seem this is not the right thing to do?