New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Website is down. #186
Comments
if anyone in the @browserify/owners org wants ssh access to peep this, I can facilitate. Too busy to dig into it myself otherwise--sorry! |
For the future, some step-by-step directions on how to self-host this would be nice. |
@mpj I gotcha https://github.com/browserify/wzrd.in#installationoperation devops not included |
I dont have time anymore today but I can check tomorrow or if something like this happens again in the future. Do you just need an SSH pubkey? |
@goto-bus-stop yes, I just need an ssh pubkey. |
|
@goto-bus-stop ok cool, you're added. |
Thanks! I just did |
gg. Most of the issues I've ran into have been related either to the cache getting too big, the logs not getting rotated properly, a combination of those two, or the letsencrypt cron job quietly breaking. :) I think I fixed the cron job finally and I haven't had logs issues lately, so I think we're actually ok! |
I think the biggest challenge ops-wise is that it's just a single machine that max is paying for afaik and no configuration mgmt/etc, so doing architectural changes can be a bit of a thing. I was always a fan of using load balancers to shift traffic onto new instances, which is a strategy that won't work here, barring somebody setting up a shared account being paid for by donations or something. Still, if left alone, minus hiccups like this it should keep trucking as always. |
@jfhbrook @goto-bus-stop Website is down again 😞 |
Thanks for the ping; the letsencrypt SSL certificate expired, just
renewed it!
|
LE should auto-renew, I think the permissions on the files the cron job is trying to write to are fucky. I was just never able to properly test it, is all. |
https://wzrd.in/ seems to be down.
I am getting a 502 Bad Gateway when I try and navigate there.
The text was updated successfully, but these errors were encountered: