I have no plan currently active. There's no option to delete the Default (and only) card I have on file. I was planning on replacing the payment method with a virtual card to avoid any potential accidental billing problems but I ran into the issue mentioned above. Let me know what type of information you need for debugging.
Am I missing something? It looks like you can't remove all the payment methods, you need at least one on file. And you can't add a new payment method without paying it looks like. It takes me to the initial billing screen. Clicking on one of the plans then takes me back to the credit card screen with the plan active.
Both issues should be fixed now. Let me know if it's still a problem.
One argument against not allowing removing of a payment method is accidental billing, which is why https://privacy.com/ exists. Some people use disposable prepaid (or virtual) cards. This might be OK for those users since they can change the info for new payments, but for people like me who have already used their real cards the ability to remove that info without making a new payment would be nice.
Also, I'm no expert on 2FA security, but I would imagine that the last 4 digits of a CC is semi easily obtainable since that info is not kept secret. Maybe an alternative idea would be to require they send a PGP encrypted e-mail using a key uploaded to the site or to implement TOTP backup codes.
This patch addresses the concern of a 500 occurring when a user attempts to delete a PGP key which is in use,
There is a separate patch for that (posted above) I posted a while ago but it hasn't been merged. The problem is that when you try to delete the key used to encrypt an e-mail there is a foreign key constraint. So displaying the error message but not allowing deletion is an alternative solution.
As an aside, however, this patch does not address the second and related part, which displays None in the table if a duplicate key is uploaded by a user.
@bearbin has already identified the problem for that. I will take a look at that assuming they don't get their dev environment setup.
I have a patch here: https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/7706 Please take a look and add feedback.
This is a duplicate of https://todo.sr.ht/~sircmpwn/meta.sr.ht/96
Here is a patch I made a while ago, but it hasn't been looked at in a while: https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/3380
@xaffe Thanks for the suggestion. In addition with that, I needed
sudo service cgroups start.
Are these instructions up-to-date? I added the
dockerdinvocation but run into the same issue: https://builds.sr.ht/~remyabel/job/80651 But maybe I missed something obvious.