Cloudron subscription credit card expired

[ekevu123]

@subven "blocks the server" means in this case: I couldn't access any installed application nor the my subdomain to administrate cloudron. I could do it again after making the payment.

Good to hear that this might be a bug, not policy, then hopefully, the team will pick it up.

[nebulon]

@ekevu123 actually not sure what happened there, but at least from our side there is nothing implemented which would cause what you have seen on your Cloudron. If a subscription charge fails, then stripe our payment provider will retry for a week and will send reminders.

After that, the subscription goes into unpaid state if charge fails for a week, at which point the only limitation you will face is the inability to install new apps or update existing ones.

[girish]

@ekevu123 said in Cloudron subscription credit card expired:

@subven "blocks the server" means in this case: I couldn't access any installed application nor the my subdomain to administrate cloudron. I could do it again after making the payment.

Not sure what happened here but we have no code to block apps or bring down the server. In fact, you can run Cloudron with an expired license forever (you just don't get updates).

[girish]

This is documented here - https://docs.cloudron.io/billing/#canceling-subscription

[scooke]

It'd be nice if OP would return with some answers or explanations. Something happened, but it wasn't Cloudron who blocked things. They may never return to clarify, but it would be nice so that others looking up Cloudron won't stumble upon a post like this and conclude erroneously that it isn't trustworthy.

[BrutalBirdie]

@scooke I feel what you mean, but when all staff members declare there is nothing like that implemented
Also you can always just dig threw the code: https://git.cloudron.io/dashboard/groups

I mean, my first answer is, please reach out to the support since there is nothing like this implemented.

Like @girish pointed out this is what officially happens and can be verified by any other cloudron subscriber.
https://docs.cloudron.io/billing/#canceling-subscription

[scooke]

@BrutalBirdie I think my meaning wasn't clear. Obviously it wasn't Cloudron, so, it would be nice to hear back from the OP about what did happen, if they figure it out. E.G., another coworker who had access to the server did something, or there was a firewall change they didn't know about, some Cloudflare change they didn't know about, or they had Cloudron installed on a non-fresh server that somehow still managed to work, or some other error on their side. And thus, once they've realized and understand what did go wrong on their end, they can 'retract" their blame of Cloudron.

Cloudron support is incredible, but does this extend to troubleshooting someone else's server, particularly when they don't seem to know what's going on on it?

Since this all seems so unlikely, could this be a case of some other company trying to smear Cloudron? Just conjecture on my part.

[ekevu123]

@scooke That's a bit far-fetched. I am a happy customer of Cloudron and trust the support team providing clear evidence that nothing serious happened. Since everything is working fine again, there is not necessarily a need for me to work on this further as the problem has been solved. I was only bringing an issue to the attention of the support that looked suspicious and then we clarified it thanks to this forum.

Don't forget that all of this could still be a bug of some sort, so it has nothing to do with smearing Cloudron and I still feel it was the right thing to bring this forward. Also, it has nothing to do with not understanding with what happens on the server, I explained the chain of events clearly above what failed when and got resolved after which actions.

[girish]

@ekevu123 fwiw, I am happy you reported it and we have this clarification here!

[scooke]

@ekevu123 I hear you... it's working now, so let's get on with work! I'd personally be still very concerned to figure out what happened. You wrote, Cloudron blocks the server running the license immediately including all 8 applications for our company when all code points to that NOT being the cause of not accessing the server apps. "Something caused our sites to be unaccessible" is basically what happened, and you still don't know what that something was.

As for my last struck-out line, I was just thinking out loud, not trying to level accusations. I've read many support requests that end up being something wrong on the server, not Cloudron, so insisting it had to be Cloudron seems odd.

Happy new year!