Let's encrypt not working for pritunl

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: hvtdc.org

I ran this command:

It produced this output:

My web server is (include version): running pritunl version 1.29.2664.67

The operating system my web server runs on is (include version): ubuntu 18.04 (bionic reaver

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): version 1.16.0

So my pritunl server is up and running, the DNS records are updated and resolving but when I try to connect a user to the server it times out due to a let's encrpyt error on the domain. Ive ran certbot but the machine says something else is bound to port 80 which is believe is attached to pritunl already.
Here is a screenshot of the pritunl log
image

Any insight as to what could be causing this would be greatly appreciated.

Pritunl seems to be shipping a build-in client, probably based on acme_tiny. So certbot isn't used at all.

Unfortunately, the log you're showing is only saying that something with the challenge didn't pass, not why.. Isn't there more information in the pritunl log?

Here is a better shot of what happens when I do try to connect to our own domain.

Unfortunately, it's not giving more information about why the challenge is failing.

are there some commands I can run on the server to display more useful data that would help?

I'm not familiar with pritunl, maybe you could check its documentation?

You could show the vhost config section/file that serves that domain name.
You could also show more detail to the command run.
You could also confirm the external IP matches the current DNS resolve for hvtdc.org.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.