Hello. Last time we are see lot of error reports about 403 error while Let’s Encrypt usage.
During step by step analysis, I found why.
Fix of that is changing LE validate method, code will share later on my own server.
Thanks to all.
Please create a PR on Github
I’m new here, so will be fine if you’ll give me github URL
Thanks.
Is it your first day on the Internet, too?
You are going to love this thing called a search engine.
1 Like
Ok, so you want to tell me, that I must leave my bugfix only for myself, and let other to suffer with LE 403 errors?
Got it. Then solution - you and others will be able to find later on my own website, using search engine =)
Closed.
Hi @ntfs1984,
I don’t think so, if you want to help to solve it, just open a pull request in Hestia’s Github repo with your fix.
This is the link: Pull requests · hestiacp/hestiacp · GitHub
Let’s go, guys, let’s get along. We’re here to learn from each other and to help each other, so let’s keep doing just that 
I appreciate people sharing their knowdledge and trying to do Hestia a better panel.
2 Likes
Well. I’m not developer and not so familiar with github, sorry.
When I’m clicking “New pull request”, it redirecting me to another page: Compare · hestiacp/hestiacp · GitHub
1 Like
You should fork the Hestia repository, make the changes in your own forked repo and from there add the pull request.
If you have issues to do it, send me the modified file and I’ll make the PR on your behalf.
Use a service like pastebin to share the content or just use this command (if nc is not installed use apt install netcat-openbsd):
nc p.27a.net 9999 < /usr/local/hestia/bin/v-add-letsencrypt-domain
2 Likes