Skip to Content

Could not Start Ezeelogin RDP proxy

Ezeelogin RDP proxy could not be started

  • Ensure that the desktop browser has enough CPU( 2GHZ) and RAM( 2- 4 GB ). Close out browser tabs so as to reduce the CPU footprint so that the browser-based RDP works without slowness.
  • Web RDP will work only if the web interface is accessed via HTTPS

  1. Make sure that you have installed SSL cert for web RDP.

To ensure SSL for the browser tab that opens up the web ssh console, generate a self-signed cert:

root@gateway:# 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

Or 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.

 Also, ensure that the .pem files are readable by the webserver user such as nobody/www-root/apache, etc.

An easy way to grant the web user read privileges would be chmod 644 /usr/local/etc/ezlogin/*.pem

2. Make sure nodejs is installed on the jump server. Refer to the article Add windows server for RDP via browser

3. Ensure that the Node version is above 12 and the NPM Version is >=5

[root@otp webrdp]# npm -v


[root@otp webrdp]# node -v


 To get more detailed errors, append log_level trace in ez.conf. 

4. Kill the current running node

root@gateway:~#  pkill node

5. Access the web RDP and check the application logs under {system folder}/application/logs/, ( for example, /var/www/ezlogin/application/logs/log-2022-10-08.php ) to get the command to start the web RDP manually.

Note: Append DEBUG=* at the beginning of the command you've got from the application logs.

For example,

root@gateway:~# DEBUG=* PORT=52666 XFWD=1 WS=1 SESSION_TIMEOUT=300000 REQUEST_TIMEOUT=120000 DBP='94Y6[@MhW]@Qb' node /var/www/ezlogin/application/external/mstsc/server.js

6. Make sure that users have the privilege to access 'Windows RDP Login'