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 63 matches
- Sun Jul 09, 2017 11:45 am
- Forum: Web Server
- Topic: Opcache config using per user file config
- Replies: 0
- Views: 1418
Opcache config using per user file config
I've been diving into opcache config the last few days as Im spinning up a new VM that will host multiple clients. According to this link its fairly trivial to read other users files when using a shared memory config. https://web.archive.org/web/20150905223439/ikanobori.jp/php55-opcache-shared-hosti...
- Sun Jul 09, 2017 6:51 am
- Forum: Web Server
- Topic: How to get visitor ip in ubuntu 16.04 ?
- Replies: 11
- Views: 8013
Re: How to get visitor ip in ubuntu 16.04 ?
From memory you have to create a mail domain for the domain your hosting, possibly also comment a line out in Exim config.
- Sun Jul 09, 2017 6:47 am
- Forum: General Discussion
- Topic: Remote Backup Zero Size
- Replies: 2
- Views: 3434
Re: Remote Backup Zero Size
I use duplicity for this - its been ultra reliable.
Currently backing up to S3 with it.
Currently backing up to S3 with it.
- Sun Jul 09, 2017 6:40 am
- Forum: General Discussion
- Topic: [bug] Vesta adds a random } when changing domain back-end templates
- Replies: 1
- Views: 1926
Re: [bug] Vesta adds a random } when changing domain back-end templates
If editing/adding templates you have to make sure a new line exists at the end, at least that is what solved this exact issue for me.
- Fri Jun 23, 2017 7:38 am
- Forum: Web Server
- Topic: LetsEncrypt renewal killed nginx config
- Replies: 4
- Views: 4894
Re: LetsEncrypt renewal killed nginx config
Having a new line at the end of every template file helped resolve this for me.
I had been adding a number of new templates to support http2 etc.
I had been adding a number of new templates to support http2 etc.
- Sat Jun 10, 2017 11:16 pm
- Forum: Web Server
- Topic: LetsEncrypt renewal killed nginx config
- Replies: 4
- Views: 4894
Re: LetsEncrypt renewal killed nginx config
Ok, this happened again.
It was an extra closing brace "}" last time, this time a brace was missing.
Doing a web rebuild for this user fixes the issue until a LE renewal takes place.
It was an extra closing brace "}" last time, this time a brace was missing.
Doing a web rebuild for this user fixes the issue until a LE renewal takes place.
- Tue Jun 06, 2017 1:31 am
- Forum: Web Server
- Topic: LetsEncrypt renewal killed nginx config
- Replies: 4
- Views: 4894
LetsEncrypt renewal killed nginx config
I had a site do an automatic renewal at 3AM this morning, what was unexpected was when it updated the nginx config for that domain it added an extra "}" effectively blocking the nginx process from starting.
Anyone else having this issue?
Anyone else having this issue?
- Wed May 31, 2017 11:50 pm
- Forum: General Discussion
- Topic: Best Practice for Blocking Countries?
- Replies: 2
- Views: 5214
Re: Best Practice for Blocking Countries?
Look into ipset for doing this at the iptables level as its very efficient.
While your there - also block the emerging threat list.
http://rules.emergingthreats.net/fwrule ... ck-IPs.txt
While your there - also block the emerging threat list.
http://rules.emergingthreats.net/fwrule ... ck-IPs.txt
- Tue Apr 11, 2017 6:31 am
- Forum: Web Server
- Topic: Let's Encrypt create/renew with force-https template
- Replies: 18
- Views: 23574
Re: Let's Encrypt create/renew with force-https template
That change seemed to work for me - certs renewed.
- Tue Apr 11, 2017 4:52 am
- Forum: Web Server
- Topic: Let's Encrypt create/renew with force-https template
- Replies: 18
- Views: 23574
Re: Let's Encrypt create/renew with force-https template
Is it OK to include both so the LE .conf gets included?
Code: Select all
include %home%/%user%/conf/web/s%proxy_system%.%domain%.conf*;
include %home%/%user%/conf/web/%proxy_system%.%domain%.conf*;