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 34 matches
- Wed Nov 16, 2016 8:05 pm
- Forum: Mail Server
- Topic: Webmail 404 not found
- Replies: 3
- Views: 3637
Re: Webmail 404 not found
Have you checked that RoundCube is running? Checked RoundCube's logs?
- Wed Nov 16, 2016 8:04 pm
- Forum: Mail Server
- Topic: What kind of SSL
- Replies: 3
- Views: 3120
Re: What kind of SSL
What do you mean clients? Are these people who will have their own domain or are you selling people e-mail on a common domain? If the goal is just to make the self-signed certificate warning go away then any SSL will do. I'd generally recommend buying it from SSLS.com and just get the cheap $5 a yea...
- Sat Nov 12, 2016 2:13 pm
- Forum: General Discussion
- Topic: How to login using domain.com:8083
- Replies: 3
- Views: 4674
Re: How to login using domain.com:8083
you need to setup an A record for that IP in your domain's DNS then Goto VestaCP->>IP and put the domain name under the IP I understand the A record part but not sure what the second step is -- as far as I can tell all you need is the A record. What I'm trying to figure out is the best way to not h...
- Sat Nov 12, 2016 3:57 am
- Forum: General Discussion
- Topic: Fail2Ban -- not banning?
- Replies: 4
- Views: 5243
Fail2Ban -- not banning?
I've been intentionally logging in with the wrong password to the panel.
/var/log/vesta/auth.log shows the failed attempts
but when I check fail2ban-client status vesta-iptables there are no failed and no banned ips
/var/log/vesta/auth.log shows the failed attempts
but when I check fail2ban-client status vesta-iptables there are no failed and no banned ips
- Sat Nov 12, 2016 2:24 am
- Forum: General Discussion
- Topic: SSL for panel
- Replies: 3
- Views: 3617
Re: SSL for panel
Thank you. Worked perfectly
- Fri Nov 11, 2016 9:16 pm
- Forum: General Discussion
- Topic: SSL for panel
- Replies: 3
- Views: 3617
SSL for panel
I've bought and added SSL for example.com -- works fine. I access my panel using example.com:8083 and I get that it is an invalid certificate. I'm working my way though previous posts on this but topics seem to contradict each other so figured I'd ask on the off chance someone responds with an answe...
- Fri Nov 11, 2016 8:20 pm
- Forum: Web Server
- Topic: [ TUTORIAL ] How to change the default /phpmyadmin alias url
- Replies: 11
- Views: 72729
Re: [ TUTORIAL ] How to change the default /phpmyadmin alias url
Late but might be useful for someone elseWAS wrote:I've edited both template files but Vesta CP still links to phpmyadmin folder, any ideas?
Code: Select all
$db_myadmin_link = "http://".$http_host."phpmyadmin/";
- Fri Nov 11, 2016 3:20 pm
- Forum: Mail Server
- Topic: ClamAV + CentOS 7.2 Issue
- Replies: 2
- Views: 4255
Re: ClamAV + CentOS 7.2 Issue
I ended up figuring it out. I found this post here: https://forum.vestacp.com/viewtopic.php?t=10730#p40115 It involves making two changes to clamd.conf and one change to exim.conf and problem was solved. I obviously appreciate the work that the VestaCP team has put in for a program that is free but ...
- Thu Nov 10, 2016 3:00 pm
- Forum: Mail Server
- Topic: ClamAV + CentOS 7.2 Issue
- Replies: 2
- Views: 4255
ClamAV + CentOS 7.2 Issue
Has anyone solved this? What is funny is that I don't even expect a response. The lack of any kind of activity / support makes me think I should just dump the panel and do everything using command line. Anyway on the off chance someone does actually come along. VestaCP + CentOS 7.2 Everything worked...
- Mon Nov 07, 2016 6:20 pm
- Forum: Mail Server
- Topic: 451 Temporary local problem - please try later
- Replies: 12
- Views: 39501
Re: 451 Temporary local problem - please try later
If restart clamav-daemon.service comes back with that error and you have a clamd.conf file then your services is probably called something different. I got the same message when I tried restarting the daemon so the fast and easy solution was just to reboot by machine and then the new config file wou...