Skip to content
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

Closed
harrysarson opened this issue Mar 26, 2018 · 14 comments
Closed

Website is down. #186

harrysarson opened this issue Mar 26, 2018 · 14 comments

Comments

@harrysarson
Copy link

harrysarson commented Mar 26, 2018

https://wzrd.in/ seems to be down.

I am getting a 502 Bad Gateway when I try and navigate there.

@colinmegill
Copy link

Same, still:

image

@jfhbrook
Copy link
Collaborator

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!

@mpj
Copy link

mpj commented Mar 28, 2018

For the future, some step-by-step directions on how to self-host this would be nice.

@jfhbrook
Copy link
Collaborator

@mpj I gotcha https://github.com/browserify/wzrd.in#installationoperation devops not included

@goto-bus-stop
Copy link
Member

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?

@jfhbrook
Copy link
Collaborator

@goto-bus-stop yes, I just need an ssh pubkey.

@goto-bus-stop
Copy link
Member

@jfhbrook

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDIcqLr2k2uUw7VwPIiG0J/iHolQoIA4F+Dv9BVZdvzhWrwj3v2rVYi7SCPi2Ffe4A46xWsUXIwnKcVWET3ck3GyC95TnR4YW/fU6imabIm2V1xmhOo79cartT+bbcsXaTMpDAWpuKl6J6S9TpF07+wLJmmePBrZ2nZRHOUT+2+t1OFzFmFmC071G+nztu4+KZirgAEDLsXPBnRj2DGz+NNyJoBgqRlbsrrkzjwZHaYSK5tLDRP8OYqwgghyl3BzFncqFYgjaNa2mz5EGiwXHy8rVzlVnu2ImcmF7xvRF3IGukgdE0ryw2cC5fI+WdEcNscBNs8c/1EV44ci+gaopY1 renee@kooi.me

@jfhbrook
Copy link
Collaborator

@goto-bus-stop ok cool, you're added. admin@wzrd.in go to town! I'm camping the #browserify irc if you have questions.

@goto-bus-stop
Copy link
Member

Thanks! I just did mongroup restart and it looks like it's back up for now.

@jfhbrook
Copy link
Collaborator

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!

@jfhbrook
Copy link
Collaborator

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.

@b0o
Copy link

b0o commented May 7, 2018

@jfhbrook @goto-bus-stop Website is down again 😞
Seems the SSL cert expired?

@goto-bus-stop
Copy link
Member

goto-bus-stop commented May 7, 2018 via email

@jfhbrook
Copy link
Collaborator

jfhbrook commented May 7, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants