Help? I can't get lets encrypt certbot configured in webmin -

ZeroDefects

Supreme Member
Jr. VIP
Joined
Dec 29, 2017
Messages
1,314
Reaction score
1,140
I've spent a significant time trying to get Let's Encrypt certbot loaded in webmin (apache). I've followed about 6 different tutorials but I am still unable to get the certbot loaded.

Anyone willing to answer a few questions?
 
What are your questions?
@dogstyle007 - Thanks for the offer to help!!

Tutorial I'm following is here in Virtualmin

Error:
request failed : Web-based validation failed : Failed to request certificate :
DNS-based validation failed : Only the official Let's Encrypt client supports DNS-based validation

I'm not sure if it makes a difference but the server is for hosting Mailwizz application
 
Last edited:
Why use webmin for that? Just login via ssh, do

Code:
sudo apt install certbot

and then run certbot with both www and non www versions of the domain. It's pretty easy.
Edit:
the command for generating certificate might look something like this:
Code:
certbot run  -d www.example.com -d example.com
 
I'm not a 'coder" - I guess it's time to learn :) I'll check out some tutorials.

Thanks for the tip @Gogol
 
@dogstyle007 - Thanks for the offer to help!!

Tutorial I'm following is here in Virtualmin

Error:
request failed : Web-based validation failed : Failed to request certificate :
DNS-based validation failed : Only the official Let's Encrypt client supports DNS-based validation

I'm not sure if it makes a difference but the server is for hosting Mailwizz application
You're welcome..

Well, first I'd recommend you switch to nginx web server it's a lot more better than Apache.

The error you are getting might relate to a few things..

First, Are you using a domain to get the certificate or just your server IP?

And are you using cloudflare?

Also, it will be a lot more convenient to manage your server yourself than using a web panel IMO.

You could search on Google how to setup nginx web server and learn yourself.
 
@dogstyle007 - Thanks for the offer to help!!

Tutorial I'm following is here in Virtualmin

Error:
request failed : Web-based validation failed : Failed to request certificate :
DNS-based validation failed : Only the official Let's Encrypt client supports DNS-based validation

I'm not sure if it makes a difference but the server is for hosting Mailwizz application
Do the domains resolve to your ip, and is the webroot correct?
 
Why use webmin for that? Just login via ssh, do

Code:
sudo apt install certbot

and then run certbot with both www and non www versions of the domain. It's pretty easy.
Edit:
the command for generating certificate might look something like this:
Code:
certbot run  -d www.example.com -d example.com


@Gogol BAM! Success! Thank you so much, this lead me to a tutorial to help. You've turned me into a L33T H4x0r now! :anyway: :D:D:anyway:

You're welcome..

Problem solved! Thank you for the assistance @dogstyle007
 
@Gogol BAM! Success! Thank you so much, this lead me to a tutorial to help. You've turned me into a L33T H4x0r now! :anyway: :D:D:anyway:
See? Told you so, it's just two lines of command. I dunno why people are so scared to touch servers. :p
 
My concern was that I'm worried about screwing up my mailwizz set up and not knowing how to fix a mistake I made. Thankfully, we're all good again!
 
Sorry about the attitude in my msg, I assumed that you know what's going on, not that you need help with basics!

Glad to see that you resolved it tho <3
 
Sorry about the attitude in my msg, I assumed that you know what's going on, not that you need help with basics!

Glad to see that you resolved it tho <3
It's all good man!
 
My concern was that I'm worried about screwing up my mailwizz set up and not knowing how to fix a mistake I made. Thankfully, we're all good again!
I get it. :D
As a tip: Never delete a certificate, or try to change a certificate for a domain that you already are certified for; unless ofcourse; you know what you are doing. That could end up fcking the setup up. If you add certificates to new domain, it will not affect anything most of the time; unless something goes wrong in the apache/nginx virtual host settings (this is one other aspect of multiple website hosting on a single server that you want to study a bit.). If you want to be 100% sure, always backup the settings by typing
Code:
cp /folder/whereyour/setting/is.conf /folder/whereyour/setting/backup.conf
 
@Gogol, you're a wealth of knowledge and help! I wanted to ask you something in the thread of the go that bought a new laptop, then I closed the window... Oh well. I'll find it again.

Thanks again!
 
Back
Top