SSL Connection Issues after a deployment

Hello Fly Friends,

I’m experiencing what looks like SSL errors on some of my key services. I did just do a deployment, but I don’t see how a bug in my code would cause this. I also don’t see any indications in my logs. Any ideas?

I’m about to try a new deployment to see if that does anything.

A URL to try:
The service: nikola-receipt-receiver

Thank you!

This started when you did a deployment?

I think so, yes. Within a few mins at least. Looking up timestamps now.

Ok I’m looking at it, give me a few minutes.

1 Like reported downtime started at at 21:13 UTC for most services and 21:14 for one. Fly UI reports the deployment of nikola-receipt-receiver v256 happened about 24 mins ago, which puts it at about 21:12 UTC, so yeah that looks like a likely proximate cause.

v257 and v258 appear not to have fixed the issue.

Somehow your deploy cleared the services on the app. Can you paste the [[services]] section of your fly.toml?

1 Like

Having trouble with the formatting, but this is it:

app = "nikola-receipt-receiver"

  internal_port = 8080
  protocol = "tcp"

    hard_limit = 25
    soft_limit = 20

    handlers = ["http"]
    port = "80"

    handlers = ["tls", "http"]
    port = "443"

    interval = 10000
    timeout = 2000

Updown is starting to show services coming up.

I just reapplied your services block to your app. I don’t understand where it went, though, we’re still investigating.

1 Like

okay thank you!!! It appears I’m back up, so the fire has been extinguished. I’ll hold off on deployments for a bit until I hear back.

Actually, @kurt is it cool if I do another deployment? I’m mid development on something and wanted to land another change.

Yeah go ahead, I’ll watch and make sure it gets the right service setting.

1 Like

Deployed again and it looks like it’s down again.

Are you running latest flyctl? Also, will you share your whole fly.toml?

You can wrap it in this to format it.


I updated the above to have the latest full receiptreceiver.toml. It was just missing the top line basically.

Update available 0.0.189 → 0.0.207

Updating now

Updated to the latest. Should I run another deployment?

No let us try and reproduce first!

1 Like

sounds good. Also, my service is back up once again. :+1:

Checking in here, I’m getting close to wanting to do another deployment, but I can wait if needed.

I was just DM’ing you an update