5 ms·

I saved about 25% from Heroku, but fly is much less reliable. I've had TLS certs expire without warning and redis has timeouts

by itake 4y ago

biorach 4y ago
> redis has timeouts I see closed connections on low traffic redis connections - for now a dumb catch-and-reconnect is doing ok
- itake 4y ago
  This was the problem I was experiencing: https://community.fly.io/t/redis-socketclosedunexpectedlyerror-socket-closed-unexpectedly/5897 https://community.fly.io/t/redis-socketclosedunexpectedlyerr... Taking this thread's advice, I started self-hosting on flyio and have only seen 1 timeout in ~2 months.
mrkurt 4y ago
Did we diagnose the TLS certs expiring? This is most often something like a CAA record that fails invisibly. We're not very good at notifying you of these kinds of issues, but certs should always renew when the config remains good. People who proxy through cloudflare hit this a lot, unfortunately.
- itake 4y ago
  CF is my DNS. Not sure if I had the proxy enabled. I was able to re-configure everything and it started working. I made a reminder to check around the 65 day mark to see if it successfully renews. I suspect what may have caused the issue is I have multiple fly hosts on subdomains, but each subdomain had a wildcard certificate against the root (*.example.com).
jjtheblunt 4y ago
do they claim to warn about TLS certs and pending expiration? (i haven't found that in docs anyway)
- itake 4y ago
  With Heroku, I never had to think about expiring certificates. With FlyIO, my app was down for 4 hours and I only new about it because of 3rd party uptime monitoring. Here are a few support issues with this problem: https://community.fly.io/t/ssl-certificate-did-not-renew-automatically/4924 https://community.fly.io/t/ssl-certificate-did-not-renew-aut... https://community.fly.io/t/certificate-expired/9143 https://community.fly.io/t/certificate-expired/9143 https://community.fly.io/t/ssl-cert-expired-and-did-not-renew/2136 https://community.fly.io/t/ssl-cert-expired-and-did-not-rene...
Existenceblinks 4y ago
I tested websocket on fly about 2 years ago, it seemed to have kinda weird characteristic. It's hard to explain because I can't dig it. It's like throttle + batch scheduling somehow (I don't know what it actually does though) I tested Fly, DO app platform, Render. Ended up with DO (but it's meh, can't mount disk volume, can't deploy to a specific sha code git) I'm going to [stress]test their wss:// again this year, I'm thinking to finally move a commercial one to fly (already have hobby apps there)

I saved about 25% from Heroku, but fly is much less reliable. I've had TLS certs expire without warning and redis has timeouts

by itake 4y ago

I saved about 25% from Heroku, but fly is much less reliable. I've had TLS certs expire without warning and redis has timeouts

biorach 4y ago

> redis has timeouts I see closed connections on low traffic redis connections - for now a dumb catch-and-reconnect is doing ok

itake 4y ago
This was the problem I was experiencing: https://community.fly.io/t/redis-socketclosedunexpectedlyerror-socket-closed-unexpectedly/5897 https://community.fly.io/t/redis-socketclosedunexpectedlyerr... Taking this thread's advice, I started self-hosting on flyio and have only seen 1 timeout in ~2 months.

mrkurt 4y ago

Did we diagnose the TLS certs expiring? This is most often something like a CAA record that fails invisibly. We're not very good at notifying you of these kinds of issues, but certs should always renew when the config remains good. People who proxy through cloudflare hit this a lot, unfortunately.

itake 4y ago
CF is my DNS. Not sure if I had the proxy enabled. I was able to re-configure everything and it started working. I made a reminder to check around the 65 day mark to see if it successfully renews. I suspect what may have caused the issue is I have multiple fly hosts on subdomains, but each subdomain had a wildcard certificate against the root (*.example.com).

jjtheblunt 4y ago

do they claim to warn about TLS certs and pending expiration? (i haven't found that in docs anyway)

itake 4y ago
With Heroku, I never had to think about expiring certificates. With FlyIO, my app was down for 4 hours and I only new about it because of 3rd party uptime monitoring. Here are a few support issues with this problem: https://community.fly.io/t/ssl-certificate-did-not-renew-automatically/4924 https://community.fly.io/t/ssl-certificate-did-not-renew-aut... https://community.fly.io/t/certificate-expired/9143 https://community.fly.io/t/certificate-expired/9143 https://community.fly.io/t/ssl-cert-expired-and-did-not-renew/2136 https://community.fly.io/t/ssl-cert-expired-and-did-not-rene...

Existenceblinks 4y ago

I tested websocket on fly about 2 years ago, it seemed to have kinda weird characteristic. It's hard to explain because I can't dig it. It's like throttle + batch scheduling somehow (I don't know what it actually does though) I tested Fly, DO app platform, Render. Ended up with DO (but it's meh, can't mount disk volume, can't deploy to a specific sha code git) I'm going to [stress]test their wss:// again this year, I'm thinking to finally move a commercial one to fly (already have hobby apps there)