We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Search found 50 matches
- Sat Sep 23, 2017 2:49 pm
- Forum: General Discussion
- Topic: v-backup-users not working
- Replies: 9
- Views: 8871
Re: v-backup-users not working
Yep. Found that.
But what does it mean? How do I fix it?
But what does it mean? How do I fix it?
- Sat Sep 23, 2017 1:55 pm
- Forum: General Discussion
- Topic: v-backup-users not working
- Replies: 9
- Views: 8871
v-backup-users not working
Hi,
My VestaCP has not been backing up correctly for a month.
Running "v-backup-users" from the command line takes a while, and then finishes, but there is no backup file shown in the backup folder (/backup).
The error log shows:
v-backup-user 'admin' [Error 15]
Any thoughts?
Thanks,
MM
My VestaCP has not been backing up correctly for a month.
Running "v-backup-users" from the command line takes a while, and then finishes, but there is no backup file shown in the backup folder (/backup).
The error log shows:
v-backup-user 'admin' [Error 15]
Any thoughts?
Thanks,
MM
- Sat Jan 21, 2017 11:22 am
- Forum: General Discussion
- Topic: cron auto-update failing
- Replies: 1
- Views: 1912
cron auto-update failing
Hi, My cron job to auto-update vesta (through ticking to auto-update option on the admin page) is failing with the following errors: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable) E: Unable to lock directory /var/lib/apt/lists/ Error: vesta update failed ...
- Tue Jan 03, 2017 10:28 am
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
I have, however your solution appears to simply copy the letsencrypt SSL certs from one place to another daily, and change their permissions. Is there no way of simply referring to the certificates in their original locations? Your way has the potential of a few hours black-out every time the letsen...
- Tue Jan 03, 2017 10:20 am
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
Thanks for letting me know. How did you fix it?
- Tue Jan 03, 2017 10:01 am
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
If this helps anyone, please let me know by replying to this thread. Thanks.
MM
MM
- Mon Jan 02, 2017 7:28 pm
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
Already sorted. Thanks.
- Mon Jan 02, 2017 3:26 pm
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
So, a little bit more research ... let's encrypt creates and stores its SSL certs in: /home/username/conf/web and lists them as: ssl.website.crt ssl.website.key whereas the vesta control panel stores its SSL certs in: /usr/local/vesta/ssl and lists them as: certificate.crt certificate.key so I renam...
- Mon Jan 02, 2017 1:45 pm
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
I've also tried renaming the certificate files in:
/usr/local/vesta/ssl
but that just resulted in the 8083 admin area being inaccessible.
If I have a letsencrypt SSL cert configured for admin.mainsite.com, is that not able to be used by admin.mainsite.com:8083?
/usr/local/vesta/ssl
but that just resulted in the 8083 admin area being inaccessible.
If I have a letsencrypt SSL cert configured for admin.mainsite.com, is that not able to be used by admin.mainsite.com:8083?
- Mon Jan 02, 2017 12:36 pm
- Forum: Web Server
- Topic: HTTPS on main site, but not port 8083
- Replies: 18
- Views: 14403
Re: HTTPS on main site, but not port 8083
Ok, so a little research and I found that the server settings have an old SSL certificate that is out of date installed. How do I delete this? I've tried deleting the text and saving the settings, but it doesn't remove it.