sudo-sys August 2022

sudo-sys@sudoroom.org

4 participants
4 discussions

Re: We couldn't process your DigitalOcean payment for team team sudoroom

by Charley Sheets

Apparently when I made a donation/payment back in November, I accidentally became sudoroom's backup payment method, so it turns out I've made some additional involuntary contributions since I guess the primary payment method must not have been working. Since my mastercard happens to be maxed out at the moment, we've gotten this payment failure message. The payment will succeed when it's reattempted, but do I need to be the payment method for sudoroom infrastructure? (I wouldn't say I'm unwilling, and I'm sorry I've been so out of touch for so long, but is there no money to pay for it or has getting the bill paid simply been a task that's gone undone?) No stress from me in any case. Peace! <3 -- Charley ------- Original Message ------- On Monday, August 1st, 2022 at 3:57 AM, DigitalOcean Support <no-reply(a)digitalocean.com> wrote: > https://u14181064.ct.sendgrid.net/ls/click?upn=RQwP9VGJQTRpRJ1vrwwvTETNBoEJ… > > Failed to Process Credit Card > > Team: team sudoroom > > We have been unable to charge the credit card on your account, resulting in an overdue balance of $43.90. > > At this time, we are restricting your ability to create new DigitalOcean resources by placing your account on hold. Once your outstanding balance is paid, the hold will be removed immediately. > > We will automatically attempt to charge your credit card again within 24 to 48 hours. However, you may wish to review your existing card details or add a different credit card to your [Billing Settings page](https://u14181064.ct.sendgrid.net/ls/click?upn=RQwP9VGJQTRpRJ1vrwwvTF… > > Note: This invoice reflects our updated pricing as of July 1, 2022. See our website for more details: [New DigitalOcean Pricing](https://u14181064.ct.sendgrid.net/ls/click?upn=RQwP9VGJQTRpRJ1vrww… > > Summary for team sudoroom > > Usage charges for 2022-08-01 43.90 > Amount past due $43.90 > [View Invoice](https://u14181064.ct.sendgrid.net/ls/click?upn=RQwP9VGJQTRpRJ1vrww… > > Have questions? > > You can check out our [FAQ](https://u14181064.ct.sendgrid.net/ls/click?upn=RQwP9VGJQTRpRJ1vrwwvTET… or our [support page](https://u14181064.ct.sendgrid.net/ls/click?upn=RQwP9VGJQTRpRJ1vrwwvTG… for more information > Earn $25 credit when you [refer a friend to DigitalOcean](https://u14181064.ct.sendgrid.net/ls/click?upn=SzZLdz04LgQViZ…

2 years, 2 months

Let's Encrypt Subscriber Agreement Update

by noreply＠letsencrypt.org

Dear Let's Encrypt Subscriber: We've updated our Subscriber Agreement, effective September 21, 2022. This is the agreement that governs the relationship between you and ISRG with regards to your acquisition and use of SSL/TLS digital certificates issued by ISRG (via Let's Encrypt). You don't need to take any action to continue to use the Let's Encrypt service but we encourage you to review the new agreement. The main updates are: we now link to instructions on choosing a revocation reason if you revoke a certificate. This is a requirement for Subscriber Agreements from all Certificate Authorities as of this year. Also, we've removed unneeded capitalization, removed a section that is redundant with our Certificate Policy (CP), and tweaked the wording of the requirement to "assure" control of your private key so it matches the Baseline Requirements (BRs). You can find the updated agreement (v1.3), along with a document that shows the differences between the previous and current agreement and the full text of the previous agreement here: https://letsencrypt.org/repository/ If you have any questions about the new agreement, please ask on our community forums: https://community.letsencrypt.org/ Let's Encrypt is a free service because we want to make the Web more secure and privacy-respecting for everyone. We're able to operate as a nonprofit thanks to corporate sponsorships and donations. Please consider joining our sponsorship program: https://www.abetterinternet.org/sponsor/ Or donate now during our summer fundraising campaign to support this service (and get neat Let's Encrypt apparel!). https://letsencrypt.org/donate/ Thank you, The Let's Encrypt Team

2 years, 2 months

Let's Encrypt Subscriber Agreement Update

by noreply＠letsencrypt.org

2 years, 2 months

Cron <www-data@sudoroom> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly

by root＠sudoroom.org

ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/usr/lib/python3/dist-packages/hyperkitty/lib/utils.py", line 181, in run_with_lock log.exception("Failed to update the fulltext index: %s", e) File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 447, in __exit__ self.unlock() File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 398, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

2 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

sudo-sys August 2022