Pterodactyl failed to obtaining a Lets Encrypt

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. crt.sh | 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: marcoserver.de

I ran this command: bash <(curl -s https://pterodactyl-installer.se/)

It produced this output: The process of obtaining a Let's Encrypt certificate failed!

My web server is (include version):

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

My hosting provider, if applicable, is: Strato.de

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):

Hey guys, i try to install pterodactyl, but i run into the same error all the time... idk what to do.

Does pterodactyl provide a more informative error than just that it failed?

Let's Debug shows the "All good" sign (Let's Debug), so without an actual error message, there's not much we can do.


is that a little helpfuller? i would send you the log aswell, but there is permission denied

control.marcoserver.de has a different IP address configured than the marcoserver.de you've mentioned in the questionnaire.

That IP address has some issues: Let's Debug.

From one of my Dutch ISPs I can't connect entirely: a timeout.

From a different Dutch ISP I'm getting a response from the firewall of the host with "communication administratively prohibited", but only on port 80/443 (from the few ports I've tried). Port 22 (SSH) seems to be working fine, while other ports like the random 1234 (very random indeed) are giving a timeout. So probably a firewall at work here.

2 Likes

yeah i wanted to connect the the sub domain to a vm. So i connected it like that.

to the firewall, yeah there is one but 80/433 is open

Not from my point of view, nor from LetsDebugs either. Any geoblocking going on perhaps?


and on the vm

It's not uncommon for hosted VPS to also have some kind of firewall set up in their VPS providers control panel. I think this is common on Amazon services, not sure about your Oracle VPS though. Worth taking a look.

Edit: looks like you sniped your post just a few seconds before mine :slight_smile:

yeah there is a firewall on oracle. but i put the prots already in there. :frowning:

You might want to put the order "in order": I think now the ICMP rules 2 and 3 are overruling the rules below them. The only port from that list that works is port 22. All the others don't. Also, port 22 is listed twice.. How is that even possible I'd wonder.. But I think that if you rearrange the order so that the port rules are above the ICMP rules, it should work.


like that?

Yes, exactly like that :slight_smile:

Hopefully it will do something when saved and in production.

Edit:
Weird.. Now I can't even connect to port 22?

okay, wait, i will try to put all the ports new into it

okay you can try again

Seems to be working now. I can connect to at least port 80. Port 443 is giving a "connection refused", but that's to be expected if there isn't anything listening yet.

oh true, it is worrking