SP

PostsComments

RRailway

•Created by SP on 10/30/2023 in #✋｜help

Configured new domain, stuck at "Issuing TLS certificate "

@Brody Thanks for the help. It is fixed now.

13 replies

RRailway

•Created by SP on 10/30/2023 in #✋｜help

Configured new domain, stuck at "Issuing TLS certificate "

Sure. Thanks

13 replies

RRailway

•Created by SP on 10/30/2023 in #✋｜help

Configured new domain, stuck at "Issuing TLS certificate "

I think it's been 3-4 hours.

13 replies

RRailway

•Created by SP on 10/30/2023 in #✋｜help

Configured new domain, stuck at "Issuing TLS certificate "

13 replies

RRailway

•Created by SP on 10/30/2023 in #✋｜help

Configured new domain, stuck at "Issuing TLS certificate "

Project id: "4b49be5c-8a2a-44f2-90e8-28a9de6c457f"

13 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Ok. We faced this issue, I cannot share more details about my services here. Is there anything I can do to get more information(will sending emails to support email address help)?

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Thanks for your help

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Explaining this again: The old service never crashed, We catch all the errors to make sure that a running service won't stop.

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Sorry. Let's also not forget that there can be issues in the platform. I have posted this message since we faced "503" error. The error was gone after redeployment. I still got 503 errors after successfully deploying(healthcheck passed) for few more mins.

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

This is the complete healthcheck log

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Path: /health Retry window: 5m0s Attempt #1 failed with service unavailable. Continuing to retry for 4m59s Attempt #2 failed with service unavailable. Continuing to retry for 4m58s Attempt #3 failed with service unavailable. Continuing to retry for 4m56s Attempt #4 failed with service unavailable. Continuing to retry for 4m52s Attempt #5 failed with service unavailable. Continuing to retry for 4m44s Attempt #6 failed with service unavailable. Continuing to retry for 4m28s Attempt #7 failed with service unavailable. Continuing to retry for 3m58s Attempt #8 failed with service unavailable. Continuing to retry for 3m28s Attempt #9 failed with service unavailable. Continuing to retry for 2m58s Attempt #10 failed with service unavailable. Continuing to retry for 2m28s Attempt #11 failed with service unavailable. Continuing to retry for 1m58s Attempt #12 failed with service unavailable. Continuing to retry for 1m28s Attempt #13 failed with service unavailable. Continuing to retry for 58s Attempt #14 failed with service unavailable. Continuing to retry for 28s 1/1 replicas never became healthy! Healthcheck failed!

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

did the build fail, or did the build succeed and the healthcheck fail? Build was successful, healthcheck failed.

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

The US-West region (i think that is the default one)

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

The UI was not able to access this service. My expectation was the old service deployment(healthy) will be available. But that was not the case

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Please understand that we have healthchecks and the deployment failed: This means the new service didn't start. The healthchecks failed with message: 1/1 replicas never became healthy! Healthcheck failed!

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

I hope you will have access to some logs to see what went wrong.

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

The deployment was failed because one of the script were broken. Our expectation was that the old container will be up incase if the deployment fails. Later after 10-10:30 CET we foud the gateway timeout errors.

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

We use volume in only one service. I understand that volume currently results in a small downtime. This is ok for us for now. But all other services does not have volume.

30 replies

RRailway

•Created by SP on 9/28/2023 in #✋｜help

Services weren't reachable when the deployment failed

Thanks for the response Brody. We implemented that long back and healthcheck is there.

30 replies