I never know how Slack login really works.
Do you have a different email registered at https://www.drupal.org/u/willhallonline / are you logged in on drupal.org?
The current URL https://app.slack.com/client/T06GX3JTS/C06AP6GE05P didn't work for me either, when I tried to click it in my browser the first time. But now I try it a second time, it works. I'm not an expert, but docs say this should be the correct format.
Does this one work?
https://drupal.slack.com/archives/C06AP6GE05P
Wasn't 100% sure if I should be in "Current security release members" or "Current general project members". Either works.
My activity will likely reflect the second
But I was already added as owner of the gitlab group so I guess my status reflects the first? (And I am pingable for anything, even though not proactive. Had enough interaction with drupal.org security issues to not feel totally out of place.)
So this PR adds to "Security release members".
Roderik Muit (cb8f29c2) at 04 Feb 14:09
Add roderik to d7security-members.md
Gitlab pipeline was already run and directory is created.
Roderik Muit (cbcb4ef6) at 04 Feb 13:50
Add samlauth to supported_projects.txt
This is not a complaint / request for change, but an attempt at providing additional documentation.
Bacme has helped me in moving away from complicated setups / dependency issues of the standard cert renewal, and not knowing how the process really works (because the bacme script is readable). Which is great.
But there's one thing where it can run into rate limits of the Let's Encrypt servers: they only allow 10 accounts to be created per 3 hours from the same IP address. (bacme is effectively spamming the servers' account system by creating a new account for every single cert request.) So you have more than 10 domains to set up / renew, you'll get blocked.
Once I ran into that, I switched to the 'dehydrated' script, which keeps a config file with account data - which it uses for all cert renewals.