Issue With FTP account change and DNS Records

[DamonNomadJr]

Issue With FTP account change and DNS Records

[cdgco]

@DamonNomadJr This is likely a problem with VestaCP as VWI has no access to your websites directly. Most likely there is a corrupt configuration somewhere or services are failing to restart after updates. First attempt updating your FTP or DNS records in the old VestaCP control panel to see if you are receiving the same errors, if so, check the following logs: /usr/local/vesta/log/error.log and /usr/local/vesta/log/system.log. Also run the command service --status-all and see if any VestaCP related services have stopped including nginx, apache, vestacp, vsftpd / proftpd, etc.

[DamonNomadJr]

Hello @cdgco, by my previous observation it has failed to properly update the records for FTP through vestaCP, as I did not have this issue by doing it directly through VestaCP itself.

I have checked the services and nginx and apache2 both refuse to run as there is a corrupt file somewhere within the system after I make the changes through VWI. Yet no changes through VCP causes this issue.

[DamonNomadJr]

Hi there to follow up again about changing the DNS records, I have taken the opportunity to create a whole new ecosystem (new server, new Vesta installation with apache and nginx, and vwi) and the editing DNS still gives me issues. "Not enough arguments provided." is the error I still get. Would someone please look into this issue and see if I am the only one who is getting it?

Simply add a new DNS site, and then try to edit the IP of a record and hit save. I get the error.