Issue With FTP account change and DNS Records

[DamonNomadJr]

Server Environment

PHP 7.2.24-0ubuntu0.18.04.1 (cli) (built: Oct 28 2019 12:07:07) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.24-0ubuntu0.18.04.1, Copyright (c) 1999-2018, by Zend Technologies
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.3 LTS
Release:        18.04
Codename:       bionic
WEB Server:     apache2:8080 (www-data)
SSL Support:    mod_ssl:8443
Proxy Server:   nginx:80
Proxy SSL:      nginx:443
Web Stats:      webalizer, awstats
FTP Server:     vsftpd
Database:       pgsql, mysql
DNS server:     bind9
CRON:           cron
Firewall:       iptables+ fail2ban
Backups:        local
Disk Quota:     yes
Vesta SSL:      admin:panel.zinnercloud.com
Version:        0.9.8
NAME        STATE    CPU  MEM   UPTIME
----        -----    ---  ---   ------
apache2     running  3.9  364   4
nginx       running  0    8     4
bind9       running  0    36    4
postgresql  running  0    14    4
mysql       running  7.9  1377  4
vsftpd      running  0    0     4
cron        running  0    0     4
iptables    stopped  0    0     0
fail2ban    running  0.5  84    4

Client Environment

Operating System: Ubuntu 18.04
Web Browser: Chrome
Device: Linux

Describe the bug
The issue that we have is the problem with changing FTP account information and updating DNS records.

Issue 1 FTP: Arises when I try updating an FTP account, and I get internal server error code 500 across all my websites (Currently hosting 6) and all of them shut down. Here is a screenshot for example:

1. Go on Web
2. Edit a website info
3. On an already created FTP account update the password

Images

1. 
2. 
3. 

Issue 2 DNS: Arises when I updating DNS records, it comes back as an error.

1. Go to DNS
2. Click to view records
3. Edit a sample text record and update
4. Fails to update

Images

1. 
2. 
3. 
4. 

Note For FTP I checked my server, and Apache fails to load as the result. I didn't capture them in time before the server was up again.

[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.