- Newest
- Most votes
- Most comments
Based on the error you're encountering, there are a few potential causes to investigate:
Network and Connectivity Issues: The "Failed to contact the origin" error suggests a connectivity problem between your client and the WorkSpaces registration service. Even though you've tested from multiple browsers and networks, this type of error typically indicates that the client cannot reach the necessary AWS services.
The WorkSpaces Advisor finding about "No internet route configured in VPC subnet" is worth investigating further. While the advisor notes this doesn't affect streaming or connection brokering, it could potentially impact the initial registration and authentication process if the WorkSpace or related services need to communicate outbound.
Registration Service Connectivity: When the WorkSpaces client application cannot reach the registration service, you may see connection errors. This could manifest as failures when trying to access invitation URLs or complete the registration process. Ensure that:
- Your network allows outbound HTTPS connections to AWS services
- There are no firewall rules or security groups blocking access to the awsapps.com domain
- DNS resolution is working correctly for AWS endpoints
Recommended Troubleshooting Steps:
- Verify that your VPC subnets have proper internet connectivity through either an Internet Gateway or NAT Gateway
- Check security group rules and network ACLs to ensure they're not blocking required traffic
- Confirm that the directory is properly registered and the WorkSpace is fully provisioned
- Try accessing the WorkSpaces client application directly rather than the web portal to see if you can complete registration through the native client
Since you're working in a newer region (ap-southeast-5), I'd recommend contacting your WorkSpaces administrator or reaching out through the AWS Support Center at https://console.aws.amazon.com/support/ to verify that all regional services are properly configured and there are no region-specific considerations for the Malaysia region.
Sources
Troubleshoot WorkSpaces client issues - Amazon WorkSpaces
Thank you. I have already verified the suggested items:
Tested from multiple browsers and networks Re-sent the invitation multiple times Directory is Active WorkSpace is Available Web Access is enabled
The issue persists. The invitation URL still returns:
Failed to contact the origin
Also, accessing:
https://<directory>.awsapps.com
returns:
NoSuchWebsiteConfiguration
Could an AWS engineer verify whether this is a backend issue or a region-specific issue in ap-southeast-5?
answered 2 months ago
Relevant content
asked a year ago
asked 2 years ago
