suddenly always returns "no healthy upstream"

Viewed 18

my service is running several days nomally, but suddenly this morning it always returns "no healthy upstream", logs cannot fetch with error:

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Get "https://172.20.0.169:10250/containerLogs/ns-0lsucc8b/cap-test-0/cap-test?follow=true\u0026tailLines=1000": net/http: TLS handshake timeout","code":500}

I have enouth credits left, but my server cannot access, could someone help?

Credits Available
Gift

$5

Plan Included

$4.86

1 Answers

I have hobby plan, and I have enouth credits left, could someone help?