-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update Issue - Failed to load version/info Error: Unsuccessful HTTP response
#10477
Comments
hey guys, any update about my question? |
Hey @paologodinho. Thanks for reporting the issue - is the issue that you are being forced to login/authenticate after upgrading? Additionally, can you fix the formatting in your post above? It makes it hard to read and figure out what's going on |
Also, can you post the YAML configuration for the deployment of your Argo Server and Workflow controller. Specifically, we're looking for the arguments used to init the server and see what cc @juliev0 |
Hey @JPZ13 yes, after the update it's happen. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity and needs more information. It will be closed if no further activity occurs. |
This issue has been closed due to inactivity and lack of information. If you still encounter this issue, please add the requested information and re-open. |
Failed to load version/info Error: Unsuccessful HTTP response
Pre-requisites
:latest
What happened/what you expected to happen?
After I update for any version above V3.0.2 I lost the access to my application and I'm receiving one issue:
When my system call the internal API from argo-workflow I tracked the follow error:
My API: https://argo-xxx.int.xxx.eu/api/v1/info
Request URL: https://argo-yyyy.int.yyyy.eu/api/v1/info
Request Method: GET
Status Code: 401
Remote Address: 34.240.226.59:443
Referrer Policy: strict-origin-when-cross-origin
The text was updated successfully, but these errors were encountered: