True… I could access hex docs (which was also not working before), so I prematurely assumed the issue was resolved. I guess the hex docs have different certificates than hex.pm… So, hex.pm still on-going.
mindreframer
sodapopcan
mindreframer
yep, it’s a pain. I’ll go to sleep now (EU timezone), hopefully this will be resolved soon. And yes, the EU-located Elixir team members will be up in the morning and this should take couple hours to be fix then. My guess is in the next 3-6 hours.
Good night!
1
AstonJ
Sometimes scripts fail too - on most of the servers I manage we use HAProxy so whenever letsencrypt renews a cert it has to be copied over to HAProxy and then restart it, on occasion this has failed, and of course it doesn’t get run again as letsencrypt thinks you have a valid cert as it only checks its own files.
A cool Elixir app/script idea if anyone wants it: make a program that checks your favourite sites every day and then get it to alert you if the cert will expire in less than a week - if you get any alerts you can let the administrator know! 
1
dkarter
arcanemachine
You inspired me to cobble something together (it’s in Bash, sorry).
It’s a script that checks the certificate expiration date for a bunch of domains, then uses notify-send to send a notification for each domain that has a certificate that expires in 3 days or less. Then I made it run in a cronjob once per hour.
/home/user/scripts/network/cert-checker.sh
#!/bin/bash
# List of domains to check
DOMAINS="forum.elixirforum.com erlangforums.com hex.pm hexdocs.pm"
# # Log file (optional, for debugging)
# LOG_FILE="/tmp/cert_check.log"
for domain in $DOMAINS; do
exp_date=$(echo | openssl s_client -connect $domain:443 -servername $domain 2>/dev/null | openssl x509 -noout -enddate | cut -d= -f2)
# Check if we got a valid date
if [ -n "$exp_date" ]; then
exp_time=$(date -d "$exp_date" +%s) &&
current_time=$(date +%s) &&
diff_seconds=$((exp_time - current_time)) &&
diff_days=$((diff_seconds / 86400)) &&
diff_hours=$(((diff_seconds % 86400) / 3600)) &&
if [ $diff_days -le 3 ] && [ $diff_days -ge 0 ]; then
notify-send "Certificate Alert" "$domain expires in $diff_days days and $diff_hours hours"
# # Optional: log to file
# echo "$(date): $domain expires in $diff_days days and $diff_hours hours" >> $LOG_FILE
fi
fi
done
Make it executable with chmod +x /path/to/script, then add it to a cronjob to check the certs once per hour:
0 * * * * DISPLAY=:0 /home/user/scripts/network/cert-checker.sh
Seems to be working so far.
I put this together with a lot of help from the new Qwen3-Coder model.
4
dimitarvp
That’s what I get for recommending temporary measures like disabling strict HTTPS – 3x “
” reactions in the GitHub issue. But hey, at least I got 8x “
” as well.
Our rolling production deployment failed and that’s how I got aware of it. We’re still keeping an eye and it’s still not fixed.
1
wojtekmach
Hex Core Team
dimitarvp
Zurga
There are deployment options where you don’t have to manually renew the certs or create a cron job. If you deploy it within NixOS, all this is setup automatically.
0