Install QoderWake on Linux ECS and access the Web UI directly or through SSH port forwarding.
This section explains how to install and start QoderWake on Linux ECS, and how to access the QoderWake Web UI from your local computer. The overall process is: SSH login and complete the installation, select an access method to open the Web UI, then complete the Qoder login and enter the console.
Open a terminal on your local computer and use the actual username and server address to connect to ECS:
If you use password authentication, please enter the Linux account password as prompted; if a key has been configured, SSH may directly complete the authentication. After successful login, the command prompt switches to the user and hostname on ECS.
After logging in to ECS, execute the following command to install QoderWake:
The installer automatically detects the system platform and downloads the required components. Check the version after the installation is complete; the Qoder account completes the login after opening the Web UI. There is no need to perform account login on ECS first.
If you are prompted that 
This way QoderWake listens for
First stop the current QoderWake process. If the process is not running yet, a not-running prompt will not affect subsequent startups:
Then let QoderWake monitor all network cards of the server. After the command is executed, you will be prompted about network exposure risks. Please enter
Entering 
Open a browser on another machine that can access the ECS and visit:
This method does not require maintaining an additional SSH forwarding connection. After the page is opened, you can directly log in to Qoder without performing subsequent SSH forwarding operations.
Method 1 allows multiple computers or servers to access QoderWake through the same ECS address, but browser sign-in state is independent on each device and is not shared automatically.
This method allows QoderWake to only listen to the
First stop the current QoderWake process:
Then let QoderWake listen only to ECS local machine:
Open another terminal window on the local computer (do not execute in the ECS terminal) and run:
SSH may prompt for the account password, or it may directly use the configured key. Usually the output will not continue after the forwarding is established; please keep the terminal running and press 
With the SSH forwarding terminal running, visit the following address in your local browser. After the page opens, you can log in to Qoder:
After opening the QoderWake Web UI through any access method, even if the current browser has not logged in to Qoder, you can continue according to the following process:
After successfully logging in, follow the page prompts to enter the workspace. When the following content appears, the QoderWake Web UI is ready for normal use:
| Difference | Method 1: Direct access through server address | Method 2: Access through SSH port forwarding |
|---|---|---|
| QoderWake listening address | 0.0.0.0:19820, monitors all network cards of the server | 127.0.0.1:19820, only monitors the server itself |
| Browser address | http://<server-ip>:19820/ | http://127.0.0.1:19820/ |
| Do you need SSH forwarding | No | You need to maintain an SSH forwarding connection on the local computer |
| Network conditions | ECS firewall or cloud security group needs to allow TCP 19820 | The local computer can connect to ECS through SSH |
| Accessible scope | All devices that can access ECS port 19820 can open it; each device needs to log in separately and use the same Qoder account | The QoderWake port is not directly open to the outside world and is accessed through an SSH tunnel |
Replace
<username> and <server-ip> with the actual values. SSH can use either an account password or a configured key; credential setup is outside the scope of this guide.SSH login to ECS
Open a terminal on your local computer and use the actual username and server address to connect to ECS:
Install QoderWake
After logging in to ECS, execute the following command to install QoderWake:
QoderWake cannot be found, please exit and re-establish the SSH connection, or refresh the current shell environment as prompted by the installer. After confirming that the version is normal, choose one of the following two access methods to continue.
macOS Terminal Example 1: SSH login, installation and version check
The following examples show the SSH login, QoderWake installation, and version checking process.
Method 1: Direct access through server address
This way QoderWake listens for 0.0.0.0:19820. Devices on the network that can access ECS port 19820 can directly open the Web UI through the server address without establishing SSH forwarding.
Starting QoderWake on ECS
First stop the current QoderWake process. If the process is not running yet, a not-running prompt will not affect subsequent startups:
yes as prompted and press Enter to continue:
yes confirms that QoderWake will listen on every network interface. Any device allowed through the security group, firewall, and network path can reach port 19820. Restrict inbound access to trusted source IPs or networks. If you cannot verify the network boundary, use SSH port forwarding instead.
This method supports access from multiple devices, but each device must sign in through its own browser and use the same Qoder account associated with the QoderWake instance. Entering yes does not open a security group or firewall, and it does not configure HTTPS or an IP allowlist.
macOS Terminal Example 2: Direct access via server address
The following example shows the complete process of stopping QoderWake, starting direct access mode, and entering yes to confirm network exposure risk.
Confirm network conditions
- ECS security groups, server firewalls, and other upstream network policies need to allow TCP 19820 inbound access.
- This method will expose the QoderWake Web UI to devices that can access this port. Please only use it in a trusted network and set access control based on the actual environment.
Open in browser
Open a browser on another machine that can access the ECS and visit:
Multi-device access and account requirements
Method 1 allows multiple computers or servers to access QoderWake through the same ECS address, but browser sign-in state is independent on each device and is not shared automatically.
- Each device must complete Qoder sign-in in its own browser the first time it opens the QoderWake Web UI.
- Every device must use the same Qoder account associated with the QoderWake instance.
- Authentication with another account fails, so that account cannot enter the instance console.
Method 2: Access via SSH port forwarding
This method allows QoderWake to only listen to the 127.0.0.1:19820 of the ECS machine, and then forward the port to the local computer through SSH. The QoderWake port will not be opened directly to the outside world, nor does it need to open TCP 19820 in the security group.
Starting QoderWake on ECS
First stop the current QoderWake process:
Establish SSH forwarding on the local computer
Open another terminal window on the local computer (do not execute in the ECS terminal) and run:
Ctrl+C to end the forwarding.
macOS Terminal Example 3: Access via SSH port forwarding
Terminal A starts QoderWake on ECS, and Terminal B establishes SSH forwarding on the local computer; after the forwarding is established, Terminal B keeps running and usually no longer outputs.
Open in browser
With the SSH forwarding terminal running, visit the following address in your local browser. After the page opens, you can log in to Qoder:
Complete Qoder login
After opening the QoderWake Web UI through any access method, even if the current browser has not logged in to Qoder, you can continue according to the following process:
- Click "Login" on the QoderWake page. The original page will display "Waiting to log in" and a new Qoder page will be opened at the same time.
- If the new page displays the Qoder login page, complete the account login first; if the browser has already logged in to Qoder, you can directly enter the account confirmation page.
- Confirm the account on the "Continue to use this account?" page and click "Continue", then return to the original QoderWake page and wait for successful login.
https://qoder.com, and the ECS also needs to have outbound network capabilities to access the Qoder service. If no new page appears after clicking "Login", please allow the current site to open a pop-up window and try again; do not close the original QoderWake page before completing the authorization.
Enter QoderWake console
After successfully logging in, follow the page prompts to enter the workspace. When the following content appears, the QoderWake Web UI is ready for normal use:
- The page can load normally;
- Able to see "My Waker / My Wakers";
- Ability to create or open a Waker.