Kasper
Error when trying to switch to Hobby plan
It does show that I still have my purchased credits. But the subscription type changed from "credits" to "usage based subscription", and on the billing page it says that montly usage will be billed to my creditcard.
So before, if I would run out of credits, my services would be shut down. But now it seems I would have limitless credit (which I would like to avoid)
Should I raise this as a separate issue?
29 replies
DB backups with new egress tax
Not sure I agree with that reasoning. Sure, if the egress cost is something they cannot lower that would be the case, but since they initially charged nothing thats unlikely. The argument for the new egress tax (torrenting and stuff) wouldnt need to apply to db backups.
With 30 bucks a month for backups, that I would also need to set up myself via s3, it would be a much worse deal than something managed like neon or planetscale. So I fear it would effectively make Railway db hosting non competitive for going into production.
Conversely, a simple to use native backup solution with competitive costs would make Railway a viable option for more (and more serious aka willing-to-pay) users
11 replies
Error when trying to switch to Hobby plan
Thanks for the quick reply.
Clearing browser data didnt work. Also tried other browser (chrome and firefox).
Perhaps relevant for identifying the issue:
- login with github and 2fa
- eligible for waiving subscription fee
- error comes from the graphql post to customerMigrateToHobbyPlan
29 replies
samesite cookies; public suffix
The public suffix list is how browsers know at which level of a domain new domains can be registered. Its how it knows that me.com and you.com are not the same domain. If services allow people to register new domains withing their domain (like me.up.railway.app and you.up.railway.app), they can register themselves on the public suffix list so that the browser sees these as different domains.
This is among other things relevant for cookies. It's not as dangerous as I feared because cookies are by default set on the most specific domain. But I think it might be possible for me to set cookies at *.up.railway.app that every (non custom) domain would receive. Not super dangerous, but could be used maliciously. Another benefit of the public suffix list is that it can be used by browsers to improve the user experience, by knowing which urls to treat as different domains.
Anyway, my problem was already 'solved', but it might be usefull for railway to register their suffix. I rhink most hosting platforms (heroku, netlify, etc) are on there as well.
8 replies