Regarding the "no healthy upstream" issue in container services

Viewed 308

After configuring the custom domain name and certificate, it can be used, but it cannot be used after a day

My container logs

INFO[2025-08-07 11:59:29] reading config file: /opt/openlist/data/config.json
INFO[2025-08-07 11:59:29] load config from env with prefix:
INFO[2025-08-07 11:59:29] init logrus...
start HTTP server @ 0.0.0.0:5244

2 Answers

You just have to wait until the service provider fixes it. Maybe 2-4 days. I'm experiencing the same thing now. It was the same before.

I'm facing the same problem after deploy n8n to clawcloudrun. I'm waiting few hours now, but no hope.

I just created a new clawcloudrun account using my other Github account, then deploy another n8n in this account, however, right after i deploy the n8n, it's facing the same issue.