Edit 2: Looks like this migration is going to take some time, so images may be down for a while. Apologies, there are about 1.7 million pics for it to get through so it may take a little while.

The rest of the update is completed and it looks like everything went smoothly.

Edit: 0.19.2 update completed, pictrs in progress of migrating so images probably will be not working for a bit.

Original:

Hi all,

With the release of lemmy 0.19.2 I’ll update the site on Friday, along with the usual backend updates.

Downtime is expected to be very minimal, with any luck only a couple of seconds while the sever reboots.

I will also be updating Pictrs, the software that shows you images, so there will be a period of time where you can access Lemmy.zip but images might not load. It won’t affect the functionality of Lemmy.zip short of not being able to view or upload images during this period.

Thanks

Demigodrick

  • DemigodrickOPMAEnglish
    2·
    6 months ago

    So it looks like they’re pushing to us OK, but we’re struggling to push our stuff to them. I did just try to visit the site and got a 502 error so not sure if they’re having issues over there?

    This link shows a bit more detail and you can see hexbear under “failing instances”. Lemmy.ml and lemm.ee have the same issue as us, and I’m sure others will too. So either Hexbear’s incoming federation is broken or they’ve been offline enough for instances to automatically flag them as offline.

    Will see if there is an easy fix for this, but hopefully the federation fix in 0.19.2 will prevent this from happening in the future (if this is what it causing the issue and not a config issue hexbear side).

    Edit: feel like I need to expand in case anyone is curious. From what I can tell the issue doesn’t lie with lemmy.zip which I’ve determined two ways, one being that we are receiving stuff from them just fine and the second being that other servers appear to be having the same issue with flagging hexbear as failing. The next retry scheduled appears to be tomorrow (12th) some 24 hours after the last try the server made. If successful, I assume our server will then proceed to send all updates to hexbear as will the other servers, but this is the first time I’ve seen federation broken this way around so I can’t say for definite what will happen. I’ve reached out to a hexbear admin on matrix I’ve spoken to previously to see if they’re aware of this. I don’t really keep up with other server’s uptime so not sure if they’ve been offline a significant amount recently? This might cause all the servers to flag hexbear as failing. Otherwise I’m not sure the cause of it. But I’m pretty confident that federation on lemmy.zip is working fine and this is a hexbear issue.

    • sunaurus@lemm.eeEnglish
      2·
      6 months ago

      It’s definitely a configuration issue on their side, they are returning an incorrect inbox_url in their API at the moment.

    • treeEnglish
      2·
      6 months ago

      Thanks for looking into it, appreciate it!

      • DemigodrickOPMAEnglish
        2·
        6 months ago

        So after the upgrade we pushed all our stuff to them (I can see our posts on hexbear site directly now) so with any luck everything has been fixed :) let me know if you see anything else not right!

        • treeEnglish
          2·
          6 months ago

          ty I think it’s fixed.