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 35 matches
- Sat Dec 09, 2017 5:28 pm
- Forum: Mail Server
- Topic: Problems with allot of spam!
- Replies: 6
- Views: 4089
Re: Problems with allot of spam!
a spam score of 50 is very high. I assume vesta puts it this high to prevent false positives by default and requiring the user to manually change it. The recommended default value of spamassassin is 5. you might want to keep an eye on your logging after changing it though, just to be on the safe sid...
- Sat Dec 09, 2017 5:11 pm
- Forum: Mail Server
- Topic: Problems with allot of spam!
- Replies: 6
- Views: 4089
Re: Problems with allot of spam!
Hi,
Can you show your exim config, please? It's possible that the minimum rating to be marked as spam is just set very high.
Can you show your exim config, please? It's possible that the minimum rating to be marked as spam is just set very high.
- Sat Dec 09, 2017 1:24 am
- Forum: Modification & Patches
- Topic: [Howto] site and mysql failover using VRRP
- Replies: 0
- Views: 7994
[Howto] site and mysql failover using VRRP
Hi, I found the need for some redundancy for the websites hosted on vesta. The idea is a failover for only the web content and the underlying databases. On the backup host, the vesta panel will be disabled to prevent any changes being done to DNS when in failover mode. This is what I thought to be t...
- Sat Dec 09, 2017 12:22 am
- Forum: Web Server
- Topic: 111: connection refused while connecting to upstream [Solved]
- Replies: 3
- Views: 8249
Re: 111: connection refused while connecting to upstream
Found the issue:
/etc/apache2/conf.d/yy.yy.yy.yy.conf did not contain "listen yy.yy.yy.yy:8080"
/etc/apache2/conf.d/yy.yy.yy.yy.conf did not contain "listen yy.yy.yy.yy:8080"
- Fri Dec 08, 2017 4:02 pm
- Forum: Web Server
- Topic: 111: connection refused while connecting to upstream [Solved]
- Replies: 3
- Views: 8249
111: connection refused while connecting to upstream [Solved]
Hi, when browsing to any client domain (vestacp interface works fine), i receive a 500 internal server error. From /var/log/apache/domain/xxx.error.log, i get this: 2017/12/08 16:44:04 [error] 1651#1651: *38 connect() failed (111: Connection refused) while connecting to upstream, c lient: xx.xx.xx.x...