1 Answer
- Newest
- Most votes
- Most comments
0
Hi.
Is the 403 error after you have authenticated?
If so then it due to the credentials you are providing, verify the credentials and ensure that the link between Client VPN is still valid.
if using SAML, make sure the role and permissions have not changed.
If the 403 is just when entering the custom url check what happens if you go to the main self service portal and enter your VPN Endpoint.
Also, verify that the VPN has not been re-provisioned.
If the VPN gets recreated, and there are lots of parameters that force rebuild, then it will have a new Client VPN ID and Self-Service Portal URL.
Hope this helps.
answered a year ago
Relevant content
- asked 2 years ago
- asked a year ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
Hi Robin,
Thank you for your reply. It is the latter of the two. When going to self-service portal and entering the VPN Endpoint ID like you suggested we receive this error. Also when using the URL provided in the AWS Console for the Endpoint we receive the same.
What's odd is this was working just fine for about a week, and then it stopped.
Just to note, we use manually created accounts & SAML auth for the VPN but I see nowhere that suggests access limitation for access to the endpoint portal.
Users have no issues connecting to the apps portal.