How to get renew a Certificate with no previous knowledge


#1

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: panel.spsurvival.com

I ran this command:N/A

It produced this output: N/A

My web server is (include version):Not sure

The operating system my web server runs on is (include version):Not sure

My hosting provider, if applicable, is:Pterodactyl.io

I can login to a root shell on my machine (yes or no, or I don’t know):Not sure

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):Pterodactyl (version unknown)

P.S. Im not the one who initially set this up, the person who did is MIA and our certificate expired yesterday, the 17th and i have no idea what i need to do in order to get our website address back up and working


#2

Hi,

Your control panel provider have a guide on obtaining certificates from Let’s Encrypt.
Is it possible that the previous staff used that?

https://pterodactyl.io/tutorials/creating_ssl_certificates.html#creating-a-certificate

Thank you


#3

Yes, it is possible that he used that, as he was the one who brought us to Pterodactyl. Only thing is, neither I nor my partner knew what he did really to make it work. On this front we are complete noobs.


#4

Can you log in to a command line on this server via SSH?


#5

Yes, someone has been able to do that before, but me personally, I have no idea on how to even start doing that.


#6

I think you’ll need to contact the hosting provider’s support to get SSH access because you’ll need credentials to log in this way—assuming that the previous person didn’t give you SSH credentials (username and password, or username and cryptographic key file).


#7

I have been able to connect to our SSH now, so thankfully thats taken care of, thank you all that helped with that.
But now I’m getting the error of “problem binding to port 443: Could not bind to IPv4 or IPV6.”
used the prompt of ’ certbot renew’


#8

Hi @ShadowPhoenix

can you first try

certbot certificates

to see, which certificates are used.

Then check /etc/letsencrypt/renewal, there are configuration files. Share their content.


#9

certbot%20certif

ive got those pictures of what it showed in my command prompt, not sure what else is needed though


#10

Capture


#11

Please check the content of this directory with ls:

ls -la /etc/letsencrypt/renewal

there should be the configuration file of your certificate. Open that and share the content.


#12

Capture


#13

Now check, if you have a nano editor. And use that to view / edit this file.

nano /etc/letsencrypt/renewal/panel.spsurvival.com.conf

#14

PS: Your http doesn’t work. But your https works, if I accept the certificate.

There is a login:

https://panel.spsurvival.com/auth/login

Are you able to login there? And is it possible that you can create there a new certificate?


#15

yes, that is my log in screen, and i am able to log in there


#16

And it doesnt look like i have a Nano editor
“-bash: nano: command not found”


#17

No, at least as far as i can see, im not able to make a new certificate there


#18

Then use

cat /etc/letsencrypt/renewal/panel.spsurvival.com.conf

to show the content of this file.


#19

Capture


#20

This looks good. You have used standalone as authenticator. And no installer. Checking your page you have a nginx.

D:\temp>download https://panel.spsurvival.com/ -h
Only SslPolicyErrors.RemoteCertificateChainErrors found
SSL error: RemoteCertificateChainErrors
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: no-cache, private
Content-Type: text/html; charset=UTF-8
Date: Sat, 20 Oct 2018 23:27:28 GMT
Location: https://panel.spsurvival.com/auth/login
Set-Cookie: pterodactyl_session=eyJpdiI6Ill6bldlVTZTYjRwQ2lZcEVvWHhZS3c9PSIsInZhbHVlIjoiZHBiUEh1OVFwek9PZTE2d3YrTXZwZldhbmF1bE9WYVwvYU4wcDRPd1wveXVVNERyRk16QThxcGFyVU1hdmQ4QnZCWVJnWW5pSHZjdEFEbzlPUlpzMDZlUT09IiwibWFjIjoiZDhkNDY4ZmFmZjYyZmNlYTA4NzU1ZjIzODgzNWE5YzZiZWI2NTRjZTFiMGFmZmExMzE2MjYwZGM2ZWZkODA5MSJ9; expires=Sat, 27-Oct-2018 23:27:28 GMT; Max-Age=604800; path=/; httponly
Server: nginx/1.14.0
X-Powered-By: PHP/7.2.7

Status: 302 Redirect

688,55 milliseconds
0,69 seconds

Your error

looks like there is a running nginx. Your certificate has only one domain name. So try

certbot --nginx -d panel.spsurvival.com

Perhaps certbot may ask you something.