2 Answers
- Newest
- Most votes
- Most comments
0
Is your EC2 instance URL is the "same" URL you use for logging in on the browser for the agent? Or is the EC2 URL sitting behind any cloudfront distro, for example? The EC2 URL you have added to the Approved Origins - is that a public URL?
Alternatively and curious to know, is there a reason why you are using an EC2 for the code instead on hosting this on an S3 bucket?
answered a year ago
0
I am using proxy server to make my ec2 URL as a secure URL, When we direct login using the EC2 instance public URL that we added in the amazon connect approved origin it redirect to the dashboard page but when we go through that proxy server it give me the above errors.
I have an angular application that's why i am using EC2 to host my application,
answered a year ago
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago