Could not setup Ezeelogin Web SSH service
Error: "Could not setup Ezeelogin Web SSH service"
Overview: This article describes troubleshooting steps for resolving the error "Could not setup Ezeelogin Web SSH service," including disabling SELinux, installing SSL certificates, configuring Node.js, and managing Node modules.
- Web ssh server provides you with a service to manage your servers through a standard browser. When encountering the error "Could not setup Ezeelogin Web SSH service" while setting up the Ezeelogin Web SSH service, follow these steps to troubleshoot and resolve the issue:
Step 1. Disable SELinux.
- Make sure that "SELinux" is disabled.
- Check the status by the following command getenforce/sestatus
- If it is enabled, then change the config file in the /etc/selinux/config to SELINUX=disabled
- Reboot your server and confirm by checking the status as disabled.
Step 2. Install SSL Certificate.
- Make sure that you have installed an SSL cert for web SSH.
- To ensure SSL for the browser tab that opens up the web SSH console, generate a self-signed cert:
:~# openssl req -new -days 365 -x509 -nodes -newkey rsa:2048 -out /usr/local/etc/ezlogin/tls_cert.pem -keyout /usr/local/etc/ezlogin/tls_key.pem
- You can put a valid ca, cert and key in the files: /usr/local/etc/ezlogin/tls_ca.pem, /usr/local/etc/ezlogin/tls_cert.pem & /usr/local/etc/ezlogin/tls_key.pem respectively. You can rename your current .crt / .key file to .pem file.
Step 3. Install Node.js
- Make sure nodejs is installed on the jump server. Refer to this article to set up a web SSH console in Ezeelogin and SSH via a standard browser.
Step 4. Install Node Modules.
- After nodejs installation, Ensure that you have also installed node modules for web SSH by running the following command:
:~DEBUG=* CLIENT_DEBUG=* PORT=52222 node /var/www/ezlogin/application/external/webssh/index.js
root@localhost:~cd /var/www/ezlogin/application/external/webssh/ && npm install
Note
- If you have received the following ERROR: Segmentation fault (core dumped), make sure to delete the node modules in the webSSH application directory and re-update them again using the following commands:
Related Articles:
Blank page error in web ssh console.