Vesta Control Panel - Forum

I think there has to be more information about the problem than this to help you with a suggestion. Take a look at the error log file to start with nano /var/log/vesta/error.log Or, if you want to see it live, run this command, then try to add the website again to see the error live tail -f /var/log...

I kinda "solved" this myself after a few days. Run v-add-remote-dns-host ns2.domainname.yyy 8083 dns-cluster password After this, changing this file /usr/local/vesta/conf/dns-cluster.conf Changing this (the user from dns-cluster to admin, leave your password and other details) HOST='ns2.domain.yyy' ...

Either through the control panel or command line (cli?) or both, what are the procedures to add or remove an IP address in the firewall. Also to review what's currently there (as root) The default behavior seems to be to block an IP after several attempts then you have to wait an hour or so for it ...

htaccess is probably the easiest solution - just add the IP;s you want to have access and create a custom 403 error page to show for users who are locked out from accessing the site.
(either deny from all and allow ip;s, or allow from all and deny ip;s, either way works)

Use a script for imap-sync to move the emails between old and new mail server.
If you are new to servers and scripts, there is online-services (free) to do it for you. This one as one example: https://imapsync.lamiral.info/X/

Well, nothing new, still the same issues. Re-installed two new VPS machines, one master and one slave. Just a plain installation, no tricks of fixes at all. (similar errors found when trying to create letsencrypt ssl´s) Still get "not found" on the scripts, i have browsed through the forums all day ...

Running the command without the "sh -x", i get this root@hsxxx:~# v-add-remote-dns-host ns2.domain.yyy 8083 admin unkWDcaP1f /usr/local/vesta/func/remote.sh: line 26: return: Error:: numeric argument required Error: api connection to ns2.domain.yyy failed Looks like its the sending of the API-comman...

Try to export PATH=$PATH:/usr/local/vesta/bin/ No difference, same errors again. Ok, try export VESTA=/usr/local/vesta/ before v-add-remote-dns-host Nope Tried the same thing on the slave machine, it gets the same errors on Debian 9.7 But on my other machines, Debian 9.5 it works perfect.

grayfolk wrote: ↑

Fri Sep 27, 2019 10:31 pm

Try to

Code: Select all

 export PATH=$PATH:/usr/local/vesta/bin/

No difference, same errors again.

Running Debian 9.7 on both main and slave machine. I have tried looking in the forums for similar errors but cannot find any solutions. Anyone encountered this before? I have tried using ip instead of host, same error. Firewall open User "dns-cluster" created and working on the slave server All othe...