Edit: check pinned comment

cross-posted from: https://hexbear.net/post/8510194

Hi, its me. robot_dog_with_gun made a good point mentioning the main post this is crossposted from is on the hexbear only channel, so I’m rolling the post up, finding a bottle to stuff it in, and throwing it into the dead sea of souls that is the internet hoping some other lost bears come across it.

So I’m up front about this, I am not a tech nerd. I really don’t know what goes on in the programing side of things or how to really troubleshoot things. Hell, me figuring out how to make a bridge in my overstuffed panting local disk C: file to another SSD so I can keep my PC alive was a miracle that took over a month of fooling around to get it to work. (please tech people don’t grill me about this I don’t know why or how it worked, it just does lol) So I’m gonna say, if you have any questions, all i can do is forward them and wait for a response. In other words I’m a messenger pidgeon.

anyways, the current game plan for people that can’t get into the bear site according to the techies is as follows:

"For anyone still having issues please try hexbear.net/login "

or

" try refreshing the page (or closing your browser app entirely and reloading) if it doesn’t go away on its own. This may just be a problem from during the outage that your browser has cached. "

Thats all from me.

Good luck and semper post

Hello Bearsite afficionados

As you’ve probably noticed, the site has been struggling for the last little bit and has been almost entirely down today. We are dealing with a flood of traffic resembling a DDoS (although the scale is not huge), which knocks over the weakest link in the system, the lemmy-ui container.

Mitigation efforts are under way and the site will hopefully be fully back soon. For the moment, logged in users and app users should be able to use the site, but it may be up and down as mitigations are put in place.

Thanks for your understanding stalin-heart

EDIT 01:22 Moscow Time:

We appear to be stable with the new mitigations in place. You may (or may not) see an anubis browser challenge during initial pageload. I’ve tried to make it relatively unobtrusive. If you have a use case that anubis breaks or feel it is misconfigured, let myself or CARCOSA know.

  • BoarAvoir [they/them]@hexbear.netEnglish
    11·
    5 days ago

    Update as of 05/20/2026 22:52 MSK:

    My apologies for the lingering broken-ness. There was a hard to troubleshoot performance issue with anubis that resulted in timeouts while trying to issue challenges to logged-out users. This seems to be resolved now with a switch to an in-memory storage backend for anubis.

    Sharing disk i/o with the image backend and lots of other site traffic caused anubis to slow to a crawl under the weight of requests coming in.

    Any further issues you notice please continue to reach out! User reports are often very helpful in troubleshooting site issues heart-sickle

  • bigpharmasutra [he/him]@hexbear.netEnglish
    9·
    6 days ago

    Also having the 504 Gateway Time-out issue on both ios and osx in Firefox, Safari, and ungoogled chromium. Cache and cookie cleaning make no difference. /login works to get to the site if I hit the HEXBEAR banner in the top left corner.

  • hellinkilla [they/them, they/them]@hexbear.netEnglish
    6·
    7 days ago

    I get this when loading hexbear.net (not logged in) in firefox (having restarted computer recently):

    I can get to /login … here I am.

    This might not be useful:

    nerd shit

    from terminal on same computer,

    $ wget -v --output-document=hb.html https://hexbear.net/
--2026-05-19 07:22:52--  https://hexbear.net/
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving hexbear.net (hexbear.net)... 37.187.73.130
Connecting to hexbear.net (hexbear.net)|37.187.73.130|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2079485 (2.0M) [text/html]
Saving to: ‘hb.html’

hb                    100%[=========================>]   1.98M  11.6KB/s    in 1m 46s

    In other words it takes almost 2 mins (1m 46s) to download the index.html… could be the reason for “timeout”?

    In the browser, loading the main page is slow after logging in (which is normal) but opening the /login page initially takes a lot longer than expected so maybe it is caching a lot of resources used by the page? Which distributes the times to lower than whatever the threshold is.

    I don’t encounter the anime girls today; did see them yesterday or previous.

    Sorry I am having a long day.

      • hellinkilla [they/them, they/them]@hexbear.netEnglish
        3·
        6 days ago

        Hi I cleared the cache, cookies. I also tried using a totally different web browser. Same. Can only load /login. Not even /signup, direct post links or anything.

        I will also note that I am having a lot of general problems loading and connecting and such with the internet these days. Not only this website. Although this is the only website with a workaround. I wonder if other people who can’t get hexbear are also faced with this. A while ago I made a post about others having issues with archive.is, which got little response, but I just today saw yet another person saying they can’t use it.

        Guessing AI is somehow to blame for this but not sure what is the mechanism.