Vesta Control Panel - Forum

1. When Update from 0.9.8 to 1.0.0 automatic. SSL is not save on Vestacp website.
2. Account root has been disable
Please tell me How to fix my problem? I from Vietnam can you show me step by step. Thanks All
https://files.fm/f/rv4xwgab8 => after update lost ssl key and CA, I copied and save to see this image
https://drive.google.com/file/d/1uCuCjP ... sp=sharing => import SSL has been error

refresh the vestacp page, and open wedomain settings again. Check sertificate

imperio wrote: ↑

Wed Nov 17, 2021 9:37 am

refresh the vestacp page, and open wedomain settings again. Check sertificate

No no , I did any more, It's not working

send me result of this command

Is it any way to roll back from 1.0??? Something wrong happening. It is luck I've made changes on not important domain... I've tried to enable SSL on some domain amd this is the "results":

- no SSL added.
- aliases was deleted.
- deleted proxy support
- deleted some recorrd in DNS....

What's wrong?

19 Nov 2021
21:05:42
disabled proxy support for szablondeko.pl
19 Nov 2021
21:05:42
deleted dns record 10 on szablondeko.pl
19 Nov 2021
21:05:41
deleted alias www.szablondeko.pl on szablondeko.pl

An I've reviving now warnings daily:

Cron <admin@vmi178294> sudo /usr/local/vesta/bin/v-update-sys-vesta-all
/usr/local/vesta/bin/v-update-sys-vesta: line 41: syntax error near unexpected token `fi'
/usr/local/vesta/bin/v-update-sys-vesta: line 41: `fi [ "$package" = "vesta-ioncube" ]; then '
/usr/local/vesta/bin/v-update-sys-vesta: line 41: syntax error near unexpected token `fi'
/usr/local/vesta/bin/v-update-sys-vesta: line 41: `fi [ "$package" = "vesta-ioncube" ]; then '
/usr/local/vesta/bin/v-update-sys-vesta: line 41: syntax error near unexpected token `fi'
/usr/local/vesta/bin/v-update-sys-vesta: line 41: `fi [ "$package" = "vesta-ioncube" ]; then '
/usr/local/vesta/bin/v-update-sys-vesta: line 41: syntax error near unexpected token `fi'
/usr/local/vesta/bin/v-update-sys-vesta: line 41: `fi [ "$package" = "vesta-ioncube" ]; then '
/usr/local/vesta/bin/v-update-sys-vesta: line 41: syntax error near unexpected token `fi'
/usr/local/vesta/bin/v-update-sys-vesta: line 41: `fi [ "$package" = "vesta-ioncube" ]; then '

/usr/local/vesta/bin/v-update-sys-vesta
replace to online 41
and try again

Much better! At least when EDIT some WEB domain it's old settings remains. But after edit


EDITING DOMAIN
Error: nginx restart failed

the WEB domain property lost return to blank settings...

Return to ADMIN goes to blank page - refresh helps - and process list shows that NGINX was restarted.

Checking again the property for domain in question shows that everything fine - aliases and SSL and proxy are enabled...

Trouble!!!

SSL now not working at ALL MY SITES!!!

So ALL my sites now down at https - at http works.

2021/11/20 07:54:48 [warn] 8845#8845: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/admin/conf/web/stencil-library.ru.nginx.ssl.conf:5
2021/11/20 07:55:01 [warn] 9020#9020: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/admin/conf/web/stencil-library.ru.nginx.ssl.conf:5
2021/11/20 07:55:17 [warn] 9656#9656: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/admin/conf/web/stencil-library.ru.nginx.ssl.conf:5
2021/11/20 07:55:17 [emerg] 9656#9656: a duplicate default server for 173.249.39.218:443 in /home/simple/conf/web/szablondeko.pl.nginx.ssl.conf:2
2021/11/20 07:55:17 [warn] 9682#9682: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/admin/conf/web/stencil-library.ru.nginx.ssl.conf:5
2021/11/20 07:55:17 [emerg] 9682#9682: a duplicate default server for 173.249.39.218:443 in /home/simple/conf/web/szablondeko.pl.nginx.ssl.conf:2
2021/11/20 08:01:16 [warn] 11748#11748: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/admin/conf/web/stencil-library.ru.nginx.ssl.conf:5
2021/11/20 08:01:16 [emerg] 11748#11748: a duplicate default server for 173.249.39.218:443 in /home/simple/conf/web/szablondeko.pl.nginx.ssl.conf:2
2021/11/20 07:02:55 [warn] 1031#1031: the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/admin/conf/web/stencil-library.ru.nginx.ssl.conf:5
2021/11/20 07:02:55 [emerg] 1031#1031: a duplicate default server for 173.249.39.218:443 in /home/simple/conf/web/szablondeko.pl.nginx.ssl.conf:2

Became alive after altering

listen 173.249.39.218:443 ssl default_server http2;

to

listen 173.249.39.218:443 ssl http2;

But it would be great to know what happens... I think that

It seems that now the editing of settings of WEB domain adds default_server to the NGINX config while if users are many or sites are many and default_server was already assigned to somewhere drops an error and NGINX is failed to start... Why default_server is added without checking of existing settings? AFAIK if no default_server mentioned in any conf the NGINX choose it by it's own... May be exclude this setting from the list? Or check the presence first?

OK, it seems to be my mistake... Seems I've edit

/usr/local/vesta/data/templates/web/nginx/default.stpl that way

server {
listen %ip%:%proxy_ssl_port% ssl default_server http2;
access_log off;
server_name %domain_idn% %alias_idn%;

So after updates any domain will get default_server.