Failed to renew certificate bayareapublicschool.org with error: Some challenges have failed.
Failed to renew certificate every.cat with error: Some challenges have failed.
Failed to renew certificate stuff.sudoroom.org with error: Some challenges have failed.
Failed to renew certificate sudoroom.org with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/bayareapublicschool.org/fullchain.pem (failure)
/etc/letsencrypt/live/every.cat/fullchain.pem (failure)
/etc/letsencrypt/live/stuff.sudoroom.org/fullchain.pem (failure)
/etc/letsencrypt/live/sudoroom.org/fullchain.pem (failure)
4 renew failure(s), 0 parse failure(s)
Failed to renew certificate bayareapublicschool.org with error: Some challenges have failed.
Failed to renew certificate every.cat with error: Some challenges have failed.
Failed to renew certificate stuff.sudoroom.org with error: Some challenges have failed.
Failed to renew certificate sudoroom.org with error: urn:ietf:params:acme:error:serverInternal :: The server experienced an internal error :: Unable to update challenge
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/bayareapublicschool.org/fullchain.pem (failure)
/etc/letsencrypt/live/every.cat/fullchain.pem (failure)
/etc/letsencrypt/live/stuff.sudoroom.org/fullchain.pem (failure)
/etc/letsencrypt/live/sudoroom.org/fullchain.pem (failure)
4 renew failure(s), 0 parse failure(s)
Failed to renew certificate bayareapublicschool.org with error: Some challenges have failed.
Failed to renew certificate every.cat with error: Some challenges have failed.
Failed to renew certificate stuff.sudoroom.org with error: Some challenges have failed.
Failed to renew certificate sudoroom.org with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/bayareapublicschool.org/fullchain.pem (failure)
/etc/letsencrypt/live/every.cat/fullchain.pem (failure)
/etc/letsencrypt/live/stuff.sudoroom.org/fullchain.pem (failure)
/etc/letsencrypt/live/sudoroom.org/fullchain.pem (failure)
4 renew failure(s), 0 parse failure(s)
StatusCake Alert -- statuscake.com
Website Monitoring
Your website sudo humans has recovered.
Total downtime: 00:10:12
To view more details about why your test went down, log into your account: https://app.statuscake.com/
StatusCake Alert -- statuscake.com
Website Monitoring
Your website sudo humans has encountered an error.
Reason: Timeout / Connection Refused
To view more details about this error, log into your account now: https://app.statuscake.com/
can we figure out why messages are coming through twice on the keys list?
The following message arrived yesterday, I dealt with it and responded, and
then it came through today again. This has happened before and it's very
confusing.
Two copies of the email can be seen in the archives; the second one was sent
before 7:53PM and needless to say the was not another card swipe event to go
with it, this is some sort of bug that is happening.
here are links to the two instances of this message in the archives:
https://omnicommons.org/lists/private/keys/2023-February/000870.htmlhttps://omnicommons.org/lists/private/keys/2023-February/000872.html
I would like for us to fix this because I take these messages very seriously
and respond to them, and it's a burden when another one comes through and I
have to figure out whether I dealt with it already or not. A day later?
-jake
---------- Forwarded message ----------
Date: Mon, 20 Feb 2023 08:59:55 -0800 (PST)
From: keys(a)omnicommons.org
Reply-To: Brian Houstle <bahoustle(a)gmail.com>
To: keys(a)omnicommons.org
Subject: [omni-keys] KEY CARD REQUEST: Brian Houstle
Name: Brian Houstle
Pseudonym: Brian
Relation to omni: CCL Member
Working groups: CCL
I need a key because: Access to ccl lab
Email: bahoustle(a)gmail.com
Contact info: 3013568987
Swipe time: 7:53 pm
This email was generated by the form at: https://omnicommons.org/keys/
_______________________________________________
keys mailing list
keys(a)lists.omnicommons.org
https://omnicommons.org/lists/listinfo/keys
StatusCake Alert -- statuscake.com
Website Monitoring
Your website sudo humans has recovered.
Total downtime: 00:06:23
To view more details about why your test went down, log into your account: https://app.statuscake.com/
StatusCake Alert -- statuscake.com
Website Monitoring
Your website sudo humans has encountered an error.
Reason: String Match Failed. String Not Found
To view more details about this error, log into your account now: https://app.statuscake.com/
Looks like Jake did it. Any current bureaucrat who knows your username
can promote you at https://sudoroom.org/wiki/Special:UserRights
Also FYI I noticed this automated email was going to
"Array(a)sudoroom.org" because we had:
$wgConfirmAccountContact = array('sudo-sys(a)lists.sudoroom.org',
'juul(a)labitat.dk');
which is not a supported syntax! They only allow one email as a
string. I removed Marc's email but also set this, so that all
bureaucrats will get notified anyway:
$wgGroupPermissions['bureaucrat']['confirmaccount-notify'] = true;
It seems like we've had this bug since at least 2015. Amazing none of
us had caught it before.
On Mon, Feb 6, 2023 at 9:29 AM Andrew R Gross <arg5029(a)gmail.com> wrote:
>
> I got this email, but when I tried to complete the request the wiki gave me this error:
>
> "
>
> Permission error
>
> Jump to navigationJump to search
>
> You do not have permission to review and accept accounts, for the following reason:
>
> The action you have requested is limited to users in the group: Bureaucrats."
>
>
> Who is in the group Bureaucrats?
>
>
> Andrew R Gross, (he/him)
> 412.657.5332 - shrad.org
>
>
> On Mon, Feb 6, 2023 at 9:20 AM Sudo Room <apache(a)sudoroom.org> wrote:
>>
>> Rajah has requested an account and is waiting for confirmation.
>> The email address has been confirmed. You can confirm the request here:
>>
>> https://sudoroom.org/wiki/Special:ConfirmAccounts
>>
>>
>> NOTE: emails to the Info list were sent to an individual email address (such as info(a)sudoroom.org) with the PRESUMPTION OF PRIVACY. They may include personal information which the sender would not have sent to a public list (such as sudo-discuss). If you must forward messages to a public list, please take great care to REMOVE SENSITIVE INFORMATION!
>>
>> _______________________________________________
>> Info mailing list -- info(a)sudoroom.org
>> To unsubscribe send an email to info-leave(a)sudoroom.org
>
>
> NOTE: emails to the Info list were sent to an individual email address (such as info(a)sudoroom.org) with the PRESUMPTION OF PRIVACY. They may include personal information which the sender would not have sent to a public list (such as sudo-discuss). If you must forward messages to a public list, please take great care to REMOVE SENSITIVE INFORMATION!
>
> _______________________________________________
> Info mailing list -- info(a)sudoroom.org
> To unsubscribe send an email to info-leave(a)sudoroom.org
