Vesta Control Panel - Forum

The "error 3" is linked to the domain's DNS configuration.

[root@bridgeconsulting vesta]# tail -f error.log

2022-06-17 18:22:19 v-change-web-domain-name 'bridge' 'teste.domain-teste.com' 'domain-teste.com' [Error 3]
2022-06-17 18:23:18 v-list-dns-domain 'teste' 'domain-teste.com' [Error 3 ...

I had this problem after installing and renewing SSL.

I managed to solve it by removing the code in the template itself.

Now I expect NGINX to restart normally after an SSL install and renewal.

Here is the link to my solution, hope it helps: https://forum.vestacp.com/viewtopic.php?f=11&t=20899 ...

I had this problem after installing and renewing SSL.

I managed to solve it by removing the code in the template itself.

Now I expect NGINX to restart normally after an SSL install and renewal.

Here is the link to my solution, hope it helps: https://forum.vestacp.com/viewtopic.php?f=11&t=20899 ...

Hey guys!

I had a recurring and serious problem that I hope I have resolved and I will share it with you now.

The problem happens when installing and renew SSL .
Cannot restart NGINX due to missing "domain.auth" file in NGINX.

This is the problem:

nginx: [emerg] open() "/home/USER/conf/web ...

Always on SSL renewal the same problem occurs...
It will try to restart NGINX and fail.

To solve this I removed the line there in the template like this:

sed -i '/%domain%.auth/g' /usr/local/vesta/data/templates/web/nginx/php-fpm/*

Now, I hope this solves the problem for good.

Hope my tip ...

I solved the problem using yum update said by the colleague above.

vesta x86_64 1.0.0-5 vesta 5.7 M
vesta-ioncube x86_64 1.0.0-1 vesta 3.8 M
vesta-nginx x86_64 1.0.0-1 vesta 314 k
vesta-php x86_64 1.0.0-1 vesta 12 M

The issue was resolved with SSL.

--
André Bastos
Hospedagem de site

Hello!

I noticed that the user itself can activate SSH access.

I guess this should not happen.
I can not remember before the update.

Can anyone help correct and say if it's a bug or is it on purpose?



Thank you.

Hello,

I had the same problem and I have CSF enabled.
I managed to solve it by doing this:

- I added the ports "49152:65534" in TCP_IN in CSF;
- I enabled iptables (it was disabled);

I hope my information can help.

--
André Bastos
Webhosting
Hospedagem de Sites

Hello!

The problem is in setting the LOAD limit to generate the backup (file -> /usr/local/vesta/func/main.sh).

grep BACKUP_LA_LIMIT /usr/local/vesta/func/main.sh
BACKUP_LA_LIMIT=5

It can be solved by changing the limit:

replace 'BACKUP_LA_LIMIT=5' 'BACKUP_LA_LIMIT=20' -- /usr/local/vesta ...