Connection FAQ

Updated at:
Copy as MD

This topic answers common questions about connecting to an individual edition cloud computer.

Contents

Before you connect

Cloud computer not displayed after client logon

Possible causes and solutions include:

  • You logged on to the individual edition client with a different account than the one used to purchase the individual edition cloud computer. Ensure you use the same account.

  • Your individual edition client is not updated to the latest version. This can prevent some cloud computer cards from displaying correctly. Upgrade the client to the latest version. For details, see Upgrade Client.

Cannot connect using Safari on macOS

Symptom

When you use the Safari browser to log on to the web client and attempt to connect to a cloud computer, a message appears stating that a pop-up window cannot be opened.

Cause

This issue is caused by the default preferences in the Safari browser.

Solution

Modify the preferences in Safari. Follow these steps:

  1. In the Safari browser, open the Web Client Login Page.

  2. From the top menu bar, choose .

  3. In the left navigation pane of the Preferences window, click Pop-up Windows, and then select wuying.aliyun.com in the right pane.

  4. Click the drop-down list to the right of wuying.aliyun.com and select Allow.

  5. Refresh the page and then connect to the cloud computer.

For more information about pop-up window settings in Safari, see Allow or block pop-ups in Safari on Mac.

During connection

Cannot connect after enabling the firewall

A firewall can block ports required for connection. If you enable a firewall, you must open the required ports for your services to function correctly. For more information, see Port requirements for EDS.

Error: Cannot connect to server '127.0.0.1'

Symptom

When you try to connect to the cloud computer, the error message Cannot connect to server '127.0.0.1' appears.

Cause

This issue might be caused by a network proxy or a VPN configured on your local computer.

Solution

Disable the network proxy or VPN and try again. If the issue persists, restart your local computer and try again.

Cannot connect to a cloud computer over SSH after adding the local IP address to the security group or whitelist

Symptom

The SSH connection fails when you run ssh root@<Public-IP-address> -p <Port>, even though you added the IP address of your local computer to the security group or whitelist of the cloud computer.

Cause

When your local computer accesses the Internet through a router, optical modem, enterprise gateway, or carrier-grade NAT, the actual public egress IP address may differ from the private IP address displayed by ipconfig or System Settings. If the whitelist contains a private IP address or an outdated public IP address, the SSH connection is blocked.

Solution

  1. On your local computer, open https://ip.tag.gg in a browser to obtain the current public egress IP address.

  2. Add the IP address to the security group or access whitelist of the cloud computer. If your network uses a dynamic public egress IP address, obtain and add the new IP address whenever it changes.

  3. After the whitelist is updated, run the SSH command again to test the connection.

Additional information

  • Addresses in the 192.168.x.x, 10.x.x.x, and 172.16.x.x ranges are private IP addresses and cannot be added directly to a cloud-side whitelist.

  • Public egress IP addresses used by home broadband, 4G/5G networks, and some enterprise networks may change periodically. If the connection fails, first check whether the current public egress IP address has changed.

  • If an enterprise network uses a fixed public egress CIDR block, contact your network administrator to confirm the CIDR block and add the entire block to the whitelist.

After you connect

Session unexpectedly quits on the macOS client

This issue typically occurs on Mac computers that run macOS 12 or later. You must manually install the Workspace plug-in by performing the following steps:

  1. Download the Workspace installation package.

  2. Reinstall the Workspace plug-in.