Endpoint disconnect ("We've been having trouble communicating with Cloud Foundry")
See original GitHub issueIssue Description
Frontent Deployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, using docker compose
- Docker, single container deploying all components
- npm run start
- Other (please specify below)
Backend (portal-proxy) Deployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, using docker compose
- Docker, single container deploying all components
- Other (please specify below)
Stratos 2.0.0-rc1 with pre SCF-2.11.0-rc1 on CaaSPv3-GM
Expected behaviour
The UI should either keep the session active until the user logs out, or redirect to the login page after a default session timeout.
Actual behaviour
When the UI isn’t touched for a while the following error will be shown:
“We’ve been having trouble communicating with Cloud Foundry - You may be seeing out-of-date information”
Steps to reproduce the behavior
Log in to Stratos as admin, and leave the browser window open (idle) for a while (~10 min.). Then try to reuse the UI.
Log output covering before error and any error statements
"We've been having trouble communicating with Cloud Foundry - You may be seeing out-of-date information"
When I “Logout” and “Login” it works again, but will also loose communication after a while again.
Looks like the session times out by default, but the user isn’t redirected to the login page. Instead the error message is shown.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Endpoint disconnect ("We've been having trouble ... - GitHub
When I "Logout" and "Login" it works again, but will also loose communication after a while again. Looks like the session times out...
Read more >Troubleshooting App Deployment and Health
This topic describes how to diagnose and resolve common issues when you deploy and run apps on Cloud Foundry.
Read more >Troubleshooting response errors - OpenAPI - Google Cloud
This page describes how to troubleshoot errors that you receive in a response from a request to your API. BAD_GATEWAY. If you receive...
Read more >Cloud Foundry Networking: Enabling Direct Communication ...
Have you ever wondered how your microservices communicate with one another on Cloud Foundry ? Until recently, all traffic between ...
Read more >Troubleshooting Kubernetes Networking Issues - Teleport
Sometimes this setting could be reset by a security team running periodic security scans/enforcements on the fleet, or have not been configured ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Like mentioned in a comment before already the relation to session timeouts was wrong. I reproduced it with 2.0.0-rc2 as well, and even when it’s disconnected, the session will time out and redirect as expected.
So the issue is about loosing communication to cloud foundry under UI usage - the proxy container logs “Couldn’t refresh token for CNSI”.
Some more detail from @svollath