Skip to content
This repository has been archived by the owner on Jul 1, 2023. It is now read-only.

portal sections DB, DNS, WEB do not appear #97

Closed
mikeleord opened this issue Aug 4, 2019 · 8 comments
Closed

portal sections DB, DNS, WEB do not appear #97

mikeleord opened this issue Aug 4, 2019 · 8 comments

Comments

@mikeleord
Copy link

mikeleord commented Aug 4, 2019

Server Environment
Run the command php -v && lsb_release -a && /usr/local/vesta/bin/v-list-sys-config and put the output below

PHP 7.3.8 (cli) (built: Jul 30 2019 09:26:16) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.8, Copyright (c) 1998-2018 Zend Technologies
-bash: lsb_release: command not found

Client Environment
If the error occurred within the Vesta Web Interface control panel, what was the client environment.

Operating System: centos 7.6
Web Browser: all
Device: PC

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
vesta2

@cdgco
Copy link
Owner

cdgco commented Aug 4, 2019

@mikeleord Hello, could you try running the command /usr/local/vesta/bin/v-list-sys-config and send the results, it seems the output is missing from your post. Could you also try visiting http://10.29.22.212/list/web.php and seeing what happens?

@mikeleord
Copy link
Author

Hello sorry the delay, on /list/web.php gives me error 403 forbidden.
here is the excuse command I had not attached:

WEB Server: httpd:8080 (apache)
SSL Support: mod_ssl:8443
Proxy Server: nginx:80
Proxy SSL: nginx:443
Web Stats: webalizer, awstats
FTP Server: proftpd
Mail Server: exim + dovecot + clamav + spamassassin
Database: mysql
DNS server: named (cluster)
CRON: crond
Firewall: iptables+ fail2ban
Backups: local
Disk Quota: yes
Softaculous: yes
Version: 0.9.8

@cdgco
Copy link
Owner

cdgco commented Aug 5, 2019

@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:

<?php

require("includes/includes.php");

$vcpservices = curl_init();

curl_setopt($vcpservices, CURLOPT_URL, $vst_url);
curl_setopt($vcpservices, CURLOPT_RETURNTRANSFER,true);
curl_setopt($vcpservices, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($vcpservices, CURLOPT_SSL_VERIFYHOST, false);
curl_setopt($vcpservices, CURLOPT_POST, true);
curl_setopt($vcpservices, CURLOPT_POSTFIELDS, http_build_query(array('hash' => $vst_apikey, 'user' => $vst_username,'password' => $vst_password,'cmd' => 'v-list-sys-services', 'arg1' => 'json')));
$servicedata = curl_exec($vcpservices);

print_r($servicedata);

function checkServicex($requestedService) {
    global $servicedata;
    if($requestedService[0] == '/') {return preg_match($requestedService, $servicedata);}
    if( strpos($servicedata, $requestedService) !== false ) { return true; }
    else { return false; }

}
print_r("\n\nApache2 Check: " . checkServicex('apache2'));

@mikeleord
Copy link
Author

hi,
thanks for the help, here is the result:

{ "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:

@cdgco
Copy link
Owner

cdgco commented Aug 5, 2019

@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 includes/includes.php file with the new version from https://raw.githubusercontent.com/cdgco/VestaWebInterface/master/includes/includes.php and let me know if it fixes the problems.

@mikeleord
Copy link
Author

oohh yes!
solved everything!
Thank you!!!

vesta ok

@cdgco
Copy link
Owner

cdgco commented Aug 5, 2019

@mikeleord Great! Let me know if there is anything else you need help with.

@cdgco cdgco closed this as completed Aug 5, 2019
@mikeleord
Copy link
Author

Ok thanks a lot in the meantime!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants