Get Virtualizor

Panel is offline

Virtualizor Service

If you are un-able to load panel then make sure virtualizor service is running which can be checked using :

systemctl status virtualizor

If it is stopped then you will need to start the service.
If you use service virtualizor restart command then virtualizor will ping 4.2.2.1 . So if ping is disabled on your server then you can try starting php, nginx and mysql service separately :

/usr/local/emps/bin/fpmctl start
/usr/local/emps/bin/nginxctl start
/usr/local/emps/bin/mysqlctl start

Firewall

Virtualizor uses ports from 4081 - 4085. If there is any firewall restricting this, you will need to allow these ports.

For RHEL & CentOS < 7

iptables -I INPUT 1 -p tcp -m tcp --dport 4081:4085 -j ACCEPT
iptables -I INPUT 2 -p tcp -m tcp --dport 5900:6000 -j ACCEPT

For RHEL & CentOS 7+

firewall-cmd --zone=public --permanent --add-port=4081-4085/tcp
firewall-cmd --zone=public --permanent --add-port=5900-6000/tcp

Mysql error

If you get this error while starting the service
'Starting MySQL.. ERROR! The server quit without updating PID file (/usr/local/emps/var/mysql/mysqld.pid). '
then make sure you have space on '/' partition.
You can check it using df -h command.

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/md2   96G  96G  0G    100% /

If the space on '/' partition is 100% full then you will need to make space on that partition. Usually /var/virtualizor/ directory uses more space .

Logs

If the space is not full and you still receive the error message then you can check in logs stored under /usr/local/emps/var/log/ directory.
You can find logs for php, nginx and mysql under that directory.

Connection refused

If showing "ERR_CONNECTION_REFUSED," check if port 80 is in use on the server.
If port is occupied by ngnix or other service you can check it using lsof -i:80 or netstat -tuln | grep ':80'  command.

If found any haproxy process, check for the presence of the port-80.conf file in "/usr/local/emps/etc/nginx". If it exists, delete the file, stop HAProxy with "service haproxy stop" restart the Virtualizor service systemctl restart virtualizor, and then start HAProxy again "service haproxy start".

1. Check which process is using port 80 you can check it using lsof -i:80 or netstat -tuln | grep ':80'  command :


#  lsof -i:80
OUTPUT


COMMAND   PID    USER      FD   TYPE   DEVICE  SIZE/OFF  NODE    NAME
nginx     1235   www-dat   6u   IPv4   12346    0t0      TCP     *:http (LISTEN)
# netstat -tuln | grep ':80'
OUTPUT


tcp   LISTEN   0  128 0.0.0.0:80  0.0.0.0:*   users:(("haproxy",pid=1234,fd=5))

2. Check if port-80.conf file is present  :


#  ls /usr/local/emps/etc/nginx | grep port-80.conf
Output

port-80.conf

3. If present, delete it  :


#  rm -rf  /usr/local/emps/etc/nginx/port-80.conf

4.  Stop Haproxy service :


#  service haproxy stop

5.  Restart virtualizor service :

#  systemctl restart virtualizor

6.  Verify if virtualizor service is started properly using command  :

#  systemctl status virtualizor

7.  Start Haproxy service :


#  service haproxy start

8.  Also verify if port 80 is not in use by emps or nginx again  :


#  lsof -i:80

Server offline

If you receive server is offline message on Master panel for any of your slave panel, then make sure that slave panel is working.
If there is firewall on slave then make sure you have added Master ip and allowed ports 4081-4085.
If that is not enough , you will need to cross-check Master ip and key on Master and Slave panel.

    Was this page helpful?
    Newsletter Subscription
    Subscribing you to the mailing list