Live data from Hacker News

We are going to start charging for dedicated IPv4 in January 1st

community.fly.io

21–28 of 28 posts

Re: We are going to start charging for dedicated IPv4 in January 1st

#21

No email sent out and charged on first of January for a mere 2$. If there's a way to upset your customer base, that's one. I had already switched off them my paid apps because of poor reliability and just had one internal app. Shame because I love the workflow and the fact it's using firecracker. This is the last fly.io sees of me.

What are you switching to?

Re: We are going to start charging for dedicated IPv4 in January 1st

#22

No email sent out and charged on first of January for a mere 2$. If there's a way to upset your customer base, that's one. I had already switched off them my paid apps because of poor reliability and just had one internal app. Shame because I love the workflow and the fact it's using firecracker. This is the last fly.io sees of me.

What are you switching to?

IPv6 is the real answer

Re: We are going to start charging for dedicated IPv4 in January 1st

#23

No email sent out and charged on first of January for a mere 2$. If there's a way to upset your customer base, that's one. I had already switched off them my paid apps because of poor reliability and just had one internal app. Shame because I love the workflow and the fact it's using firecracker. This is the last fly.io sees of me.

What are you switching to?

I moved to digital ocean and hetzner

I get some downtime from digital ocean too but I like to have a backup plan in case hetzner has issues (which didn't happen yet)

Re: We are going to start charging for dedicated IPv4 in January 1st

#24
I also fell into this new trap:

    flyctl ips list

    flyctl ips release 168.220.XXX.XXX

    flyctl ips allocate-v4 --shared
Error: Your account has overdue invoices. Please update your payment information: https://fly.io/dashboard/myname/billing

Ok, so now they got my credit card info, because I had to pay 2$.

    flyctl ips allocate-v4 --shared
Error: cannot use a shared ipv4 with wildcard hostnames, please remove those before allocating a shared IP: .XXX

    flyctl certs list
    flyctl certs remove *.XXX
    flyctl ips allocate-v4 --shared
Now it works. Just have to fix my DNS records now. ipv6 or CNAME to the app.fly.dev domain preferred.

I don't like fly too much, because this is the first free hoster, which I have to constantly check for downtimes and restart the app then. Need a 10m cronjob now.

    cd ~/MyAppPath
    if timeout 5 flyctl logs -a myapp | grep -e "Health check on port 8080 has failed|connection error:"
    then
       flyctl apps restart myapp
    fi

Re: We are going to start charging for dedicated IPv4 in January 1st

#25
post #4

I just came to HN to see if there was something about this here. I just got my first charge out of nowhere. I’ve had an account there for a couple years and tried it out a long time back but wasn’t actively using it. I like fly as a service, and I have no problem with them charging, but coming out of nowhere with no prior notice is definitely frustrating and unexpected.

We agree. Presumably by now you got the email we sent out to everyone about reversing the charges. This was a bug.

Re: We are going to start charging for dedicated IPv4 in January 1st

#26
All: this was a bug. We're reversing the charges. Everyone affected got an email. The tl;dr:

* The advance notice of the billing change (we announced in October, but only on our community site) slipped, but the billing change didn't. That's not OK! We agree: you get notified before we bill new things to you.

* Ordinarily, we waive invoices less than $5. Our billing code had a bug that let these charges slip through. D'oh.

Re: We are going to start charging for dedicated IPv4 in January 1st

#27
post #14
post #9

Earlier quoted context omitted.

The notice was posted by Fly on October 18th.

Posting a notice isn’t exactly the same as communicating with accounts that will be affected by the change. I hadn’t seen anything about it so it was a surprise to me. Would have appreciated a simple heads up - “hey, we’re going to start billing for this”

You're right to be surprised, we share your expectations.

Re: We are going to start charging for dedicated IPv4 in January 1st

#28
post #25
post #4

I just came to HN to see if there was something about this here. I just got my first charge out of nowhere. I’ve had an account there for a couple years and tried it out a long time back but wasn’t actively using it. I like fly as a service, and I have no problem with them charging, but coming out of nowhere with no prior notice is definitely frustrating and unexpected.

We agree. Presumably by now you got the email we sent out to everyone about reversing the charges. This was a bug.

Thank you for making this right! I didn’t think there was any malice in it and it’s nice to know it was a simple mistake.

I’ve also already unassigned my unneeded address and I’m still interested in using fly for some things in the future.

Post reply on HN