Share
Report
8All of a sudden my BC Docker containers stopped working. All of them, just don't respond anymore. Chrome dev tools show no response at all coming from the containers. Still the containers are active and perfectly responsive, except the on the http port.
I can download symbols in VS Code and publish packages - no problem. I can start a PowerShell session with "Enter-BCContainer" or "Open-BCContainer", also works. All BC endpoins are active, Invoke-WebRequest works perfectly when I send a request to the BC service in a container session. For example "http://localhost:7049/dev/packages", "http://localhost:7049/devhealth", or "http://localhost:7046/bc/client/health" - all works.
"Invoke-WebRequest http://localhost/bc" - no response.
The same client/health endpoint is also unreachable if the request goes via IIS: "Invoke-WebRequest http://localhost/bc/client/health" - no response.
Web site on IIS is running, application pool is active, I could not find anything wrong with the web server configuration. Default web site on port 8080 also responds without any issues, so I suppose this must be something with the BC web client, but I'm out of ideas. I suspect a recently installed Windows security update could cause this, but reverting the updates did not solve the problem. And of course I tried to delete and recreate the container - still the same result. After spending a weekend trying to pinpoint the issue, I still have no idea where the problem is.
Has anyone seen something similar? Any ideas what else I can try?
Categories:
All responses (
Answers (
