Difference between revisions of "ProxCP Web and ProxCP Daemon Error Troubleshooting"

From ProxCP Documentation
 
Line 21: Line 21:
 
* '''ERROR:''' EADDRINUSE
 
* '''ERROR:''' EADDRINUSE
 
** You have another process already using the same port as the ProxCP Daemon (port 8000 by default). Be sure you are only running 1 instance of the Daemon and no other program is using the same port.
 
** You have another process already using the same port as the ProxCP Daemon (port 8000 by default). Be sure you are only running 1 instance of the Daemon and no other program is using the same port.
 +
 +
== ProxCP NAT ==
 +
 +
* '''ERROR:''' NAT interface fails to start with "RTNETLINK answers: File exists" for vmbr10 interface
 +
<code>[sudo] ip addr flush dev vmbr10</code>

Latest revision as of 17:41, 22 July 2020

ProxCP Web

  • ERROR: Blank/white page when adding a new Proxmox node (ADMIN > Settings > Manage Nodes)
    • PHP 7.2 mcrypt might not be installed. To install it on cPanel, issue the following commands in SSH:

yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
yum install libmcrypt
yum install libmcrypt-devel
/opt/cpanel/ea-php72/root/usr/bin/pecl install channel://pecl.php.net/mcrypt-1.0.1

    • Restart httpd and PHP-FPM (if enabled)
  • ERROR: "license check failed error: install is only allowed on a real working domain"
    • ProxCP Web can only be installed on a domain name, not an IP address. ProxCP checks the installation location based on the actual URL. The URL must be a domain or sub-domain, not an IP address.
  • ERROR: redirected back to a form with no displayed or logged errors
    • The form's CSRF prevention token check may have failed. In your php.ini file, ensure session.save_path has a valid directory value and your web server user (i.e. www-data, apache, etc.) has permissions to it.

ProxCP Daemon

  • ERROR: NPM error when installing forever on a cPanel server

npm config set strict-ssl false

  • ERROR: EADDRINUSE
    • You have another process already using the same port as the ProxCP Daemon (port 8000 by default). Be sure you are only running 1 instance of the Daemon and no other program is using the same port.

ProxCP NAT

  • ERROR: NAT interface fails to start with "RTNETLINK answers: File exists" for vmbr10 interface

[sudo] ip addr flush dev vmbr10

Retrieved from "https://docs.proxcp.com/index.php?title=ProxCP_Web_and_ProxCP_Daemon_Error_Troubleshooting&oldid=225"