ran the push refresh job and got the following:
PuSH re-subscribing to squirrel@computerfairi.es
[httplog] POST http://computerfairi.es/api/push completed with status code 301 in 0.17319225700339302 seconds
PuSH subscription request for squirrel@computerfairi.es failed: <html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.10.0 (Ubuntu)</center>
</body>
</html>
@squirrelbutt @squirrel yeah that's what the 301 is but it looks like the worker that deals with the subscription does not follow the redirect, and it's weird because it shouldn't be trying an http endpoint in the first place
@squirrelbutt @squirrel @bea first instance we ran had https issues. we fixed them, pushes were still wonky and we tried clearing db and starting over, that proved to be a mistake because now instances aren't getting the new versions of @squirrel and @pal
