-
Notifications
You must be signed in to change notification settings - Fork 49
portal sections DB, DNS, WEB do not appear #97
Comments
@mikeleord Hello, could you try running the command |
Hello sorry the delay, on /list/web.php gives me error 403 forbidden. WEB Server: httpd:8080 (apache) |
@mikeleord Alright, thank you. VWI seems to be failing to identify apache2, bind9, or mysql. Please create a new file in the base directory of your VWI installation (the same directory as the index.php file) called test.php with the following contents, then visit http://10.29.22.212/test.php and send the results:
|
hi, { "httpd": { "SYSTEM": "web server", "STATE": "running", "CPU": "0", "MEM": "497", "RTIME": "102" }, "nginx": { "SYSTEM": "reverse proxy", "STATE": "running", "CPU": "0", "MEM": "39", "RTIME": "102" }, "named": { "SYSTEM": "dns server", "STATE": "running", "CPU": "0.5", "MEM": "1486", "RTIME": "102" }, "exim": { "SYSTEM": "mail server", "STATE": "running", "CPU": "0", "MEM": "1", "RTIME": "102" }, "dovecot": { "SYSTEM": "pop/imap server", "STATE": "running", "CPU": "0", "MEM": "0", "RTIME": "102" }, "clamd": { "SYSTEM": "email antivirus", "STATE": "running", "CPU": "0.7", "MEM": "819", "RTIME": "102" }, "spamassassin": { "SYSTEM": "email antispam", "STATE": "running", "CPU": "1.3", "MEM": "6748", "RTIME": "102" }, "mariadb": { "SYSTEM": "database server", "STATE": "running", "CPU": "0", "MEM": "1830", "RTIME": "102" }, "proftpd": { "SYSTEM": "ftp server", "STATE": "running", "CPU": "0", "MEM": "1", "RTIME": "102" }, "crond": { "SYSTEM": "job scheduler", "STATE": "running", "CPU": "0", "MEM": "1", "RTIME": "102" }, "iptables": { "SYSTEM": "firewall", "STATE": "running", "CPU": "0", "MEM": "0", "RTIME": "0" }, "fail2ban": { "SYSTEM": "brute-force monitor", "STATE": "running", "CPU": "0.1", "MEM": "583", "RTIME": "102" } } Apache2 Check: |
@mikeleord It seems that either VestaCP has changed their naming conventions or CentOS uses different naming than Ubuntu and Debian. Regardless, I just updated the software so that it should fix this error with CentOS. Please replace your |
@mikeleord Great! Let me know if there is anything else you need help with. |
Ok thanks a lot in the meantime! |
Server Environment
Run the command
php -v && lsb_release -a && /usr/local/vesta/bin/v-list-sys-config
and put the output belowClient Environment
If the error occurred within the Vesta Web Interface control panel, what was the client environment.
Describe the bug
Hello
I installed version 1, in the portal sections DB, DNS, WEB do not appear, I manually entered the url but by error 404.
How could I solve it?
thank you so much
Screenshots
![vesta](https://user-images.githubusercontent.com/42770845/62429686-5be0c280-b71a-11e9-9ad7-0888f682605a.png)
![vesta2](https://user-images.githubusercontent.com/42770845/62429710-dc9fbe80-b71a-11e9-9b9a-521a3bf32495.png)
The text was updated successfully, but these errors were encountered: