-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network Error When Using VPN with Amplify Cognito #14220
Comments
Hi @Ammar-Raneez, thanks for raising the issue
|
@Ammar-Raneez, can you also clarify if the |
Hi @ashwinkumar6, Yes that seems to be the exact case here. Other network calls do go ahead as I have a regular Rest API that works without issues. However, the issue seems to be sporadic, making it kinda difficult to provide a complete diagnosis. |
Hi @cwomack, Nope, the middleware is only calling the |
Thanks for the additional information @Ammar-Raneez. When you encounter the network timeout are you able to ping the Cognito endpoint from outside your application and receive a response? |
It has been working now for some reason. I did not make any changes. Probably an actual network issue? |
Hey @Ammar-Raneez, glad everything is working. It does sound like it could have been a transient issue with the VPN. I will close this issue for now. Please feel to reopen or create a new issue if you encounter any more problems! |
Before opening, please confirm:
JavaScript Framework
Next.js
Amplify APIs
Authentication
Amplify Version
v6
Amplify Categories
auth
Backend
CDK
Environment information
Describe the bug
Cognito authentication seems to be failing when connected to a VPN.
Specifically, the error is being thrown from
middleware.ts
(where I do an auth guard check).Expected behavior
Everything works fine if my VPN is turned off. Are there any additional configuration that must be set for VPNs?
I need the VPN turned on because I send requests to an external API that works only if connected to the VPN.
Reproduction steps
Code Snippet
The guard check
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: