Page 1 of 1

Error 400 and 15 trying to enable let’s encrypt

Posted: Sun Oct 20, 2019 1:57 pm
by ikk157
Hello,

I’ve been trying to enable Let’s encrypt on my domain through the vesta web gui. However, it kept throwing error 400. Later on, it’s now throwing error 15. Looking those up wasn’t of much help as all the solutions in the very limited number of posts on these errors didn’t help at all.

I’ve already tried tried to reinstall vesta, to no avail. Checking for updates also is of no use as it shows that it’s up to date.

I’m running this on a VPS with CentOS 7.

Let me know if you need any more information than what I’ve already provided, along with how i can obtain it (Since I’m not very familiar with centos)

Thanks

Re: Error 400 and 15 trying to enable let’s encrypt

Posted: Tue Oct 22, 2019 10:20 am
by gastonmaster
It was solved for me when I added a valid domain.

Re: Error 400 and 15 trying to enable let’s encrypt

Posted: Tue Oct 22, 2019 11:38 am
by ikk157
I already have a valid domain added. For a matter of fact, I visit vestacp from that domain instead of the server’s ip.

Re: Error 400 and 15 trying to enable let’s encrypt

Posted: Tue Oct 22, 2019 11:40 am
by ikk157
gastonmaster wrote:
Tue Oct 22, 2019 10:20 am
It was solved for me when I added a valid domain.
The post above is a reply to this. Sorry, i just figured out how to quote posts.

Re: Error 400 and 15 trying to enable let’s encrypt

Posted: Tue Oct 22, 2019 1:23 pm
by ikk157
Update:

I’ve tried adding a new domain and the same issue occurs.

I’ve also tried making a new vesta user and the same issue occurs.

I noticed something interesting, when running the vesta ssl command through ssh, it says the user “admin” doesn’t exist. Even though that’s the user I’ve been using to log into vesta. Maybe this could be related to the issue?

Re: Error 400 and 15 trying to enable let’s encrypt

Posted: Fri Oct 25, 2019 1:02 pm
by ikk157
Update:

I got rid of centos and installed ubuntu server. I then installed vesta and ssl now works without any errors! Guess it was a centos issue afterall.

Anyways for some weird reason, the ssl certificate isn’t applied on the vesta port. For example: https://example.com shows as secure. But https://example.com:8083 shows as unsecured.