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 so an interesting thing is that with your alt this no longer happens because it is hitting an https endpoint from the start. only your original account and pal are in my subscriptions with http instead of https
@squirrelbutt @squirrel i don't think you can actually. i was talking to @datn and seems they have a similar issue there but with my user!
@bea @squirrelbutt @squirrel of note is that I have the same issue with your alt, @b . the HTTP/HTTPS thing is an interesting clue. I am going to start looking into what it is that instances with users I can't follow are showing over IPv6 as opposed to IPv4, at least to start.
@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
@bea @squirrel @squirrelbutt i'm using the standard nginx set up, that's what it's supposed to do i believe anyway? clue me in if you got any other ideas