- Newest
- Most votes
- Most comments
The fact that both Android and Web fail is the useful clue — that rules out anything Android-specific and points at something shared.
Most likely: Web Access isn't enabled, and the protocol matters
Two things to check in order.
Web Access must be explicitly enabled by the administrator. It's not on by default. In the WorkSpaces console, open the directory → Actions → Update Details → Access Control Options, and confirm Web Access is allowed. Android is a separate toggle in the same place — if both were left at restrictive defaults, that alone explains both failures.
Which protocol is the WorkSpace using? This is now a hard constraint rather than a preference:
As of November 7, 2025, Amazon WorkSpaces PCoIP Web Access is no longer open to new customers. Existing users can continue, but new users will not be able to connect to their PCoIP WorkSpaces using Web Access.
A newly created WorkSpace on PCoIP therefore cannot use Web Access at all, regardless of configuration. If that's the case, the options are to migrate to DCV — which requires a rebuild — or use the desktop client applications.
For DCV, Web Access is supported on Windows and Linux WorkSpaces, and on Android tablets it works through Chrome or Safari on the latest three browser versions.
Then: ports
If protocol and access control check out, the next candidate is the streaming port. Authentication runs over 443, streaming over 4172 (PCoIP) or 4195 (DCV), TCP and UDP.
A very common signature is that login succeeds and then the session fails — that means 443 is fine but the streaming port is blocked by a local firewall, proxy, or mobile carrier. On Android this is easy to test: try the same client on a different network (mobile data versus Wi-Fi). If one works and the other doesn't, it's egress filtering.
Also worth confirming
- WorkSpace status is AVAILABLE, not still provisioning or Unhealthy
- The bundle supports what you're attempting — GPU-enabled WorkSpaces aren't supported for PCoIP Web Access
- Region — PCoIP Web Access is unsupported in GovCloud (US), Mumbai, Cape Town, Tel Aviv, and Paris
The missing piece
The exact error text matters a lot here, because the causes diverge sharply:
- "This device is not authorized to access the WorkSpace" → Access Control Options blocking the platform
- "No network. Network connection lost." → port 4195 blocked on a DCV WorkSpace
- Grey "Loading…" then back to login → authenticated on 443 but streaming port unreachable
- "An error occurred while launching your WorkSpace" → agent service not running on the host
Each maps to a different fix. If you can get the verbatim message from the client, that will narrow this to one candidate immediately.
If you're unable to connect to your Amazon WorkSpace using the Android or Web client, there are several potential causes and solutions to consider. First, verify that your WorkSpace is in a healthy state and that you have the correct registration code. Network connectivity issues are a common cause of connection problems - ensure your Android device has a stable internet connection and that any firewalls or security software aren't blocking the required ports for WorkSpaces.
Since you mentioned the WorkSpace is newly created, confirm with your WorkSpaces administrator that the WorkSpace has been fully provisioned and is ready for use. If you're experiencing a 'No network' error or the connection fails repeatedly, try waiting a few minutes and attempting to connect again, as there may be temporary network issues.
If the problem persists, consider trying to connect from a different network or device to help isolate whether the issue is specific to your Android device or network environment. You may also want to verify that your Android client application is fully up to date. If none of these steps resolve the issue, contact your Amazon WorkSpaces administrator, as they can check the WorkSpace status, verify network configurations, and rebuild the WorkSpace if necessary.
Sources
Troubleshoot WorkSpaces client issues - Amazon WorkSpaces
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
