Hello, everybody!
Sopuli was today down for at least an hour. I tried to enable Anubis, a web AI firewall utility that should take care of those pesky AI bots. It has gotten popular recently and many Lemmy instances have enabled it, so we had to do the same. Lots of tinkering with Docker containers and Nginx. If I had learned that the command “docker HYPHEN compose” is archaic and “docker SPACE compose” is used instead, Sopuli wouldn’t have been down. Regardless, we now have Anubis, enjoy!
EDIT:
If there is something that I have learned during the last four years of maintaining a Lemmy instance, it is not to get excited too early.
It appears that browsing Sopuli didn’t turn out to be a pleasant experience for many, as Anubis was applied at the Lemmy API instead of just the usual UI level. This meant that many users of alternative frontends or mobile apps couldn’t access Sopuli. A lot of tinkering had to be done to get Anubis working, and Sopuli was also down for several hours. Thanks to @MentalEdge@sopuli.xyz for help!
Hei kaikille!
Sopuli oli tänään alhaalla ainakin tunnin. Yritin ottaa käyttöön Anubista, web-pohjaista tekoälybottien estotyökalua, jonka pitäisi hoidella ärsyttävät tekoälybotit. Se on tullut viime aikoina suosituksi ja monet Lemmy-instanssit ovat ottaneet sen käyttöön, joten meidänkin piti tehdä samoin. Paljon piti tunkkailla Dockeria ja Nginxiä. Jos olisin oppinut, että komento “docker VÄLIVIIVA compose” on vanhanaikainen ja sen sijaan tulisi käyttää komentoa “docker VÄLILYÖNTI compose”, Sopuli ei olisi ollut alhaalla. Tästä huolimatta meillä on nyt Anubis, nauttikaa!
EDIT:
Jos on jotain, mitä olen oppinut viimeisen neljän vuoden aikana Lemmy-instanssin ylläpidosta, se on, ettei pidä innostua liian aikaisin.
Näyttää siltä, ettei Sopulin selaamisesta tullut monille mukavaa kokemusta, kun Anubis otettiin käyttöön Lemmyn sovellusrajapinnan tasolle pelkän käyttöliittymän sijaan. Monet vaihtoehtoisten käyttöliittymien tai mobiilisovellusten käyttäjät eivät voineet käyttää Sopulia. Paljon piti kikkailla jotta Anubis saatiin toimimaan, ja Sopuli oli myös alhaalla useamman tunnin. Kiitos @MentalEdge@sopuli.xyz avusta!
Voyager toimii taas. Hurraa! Kiitos korjauksesta ja kiva että opit seikkailusta :)
Thanks for the update and all the extra work getting us back up and running, we’re all very grateful!
docker SPACE compose
Been there.
applied at the Lemmy API
Yeah, I see how that happened. Because of the alt frontend, I was already mapping frontend and backend requests to different containers before installing Anubis. I don’t know what you did, but I just pretty much copied the setup from internal nginx conf to sort traffic.
We ended up with editing line 34 of the nginx config to route lemmy-ui traffic to the anubis container, and then pointed the anubis container at the lemmy-ui container.
Did not notice the downtime. Yeah docker SPACE compose is the way to go now. Anubis is amazing, well done.
Is there a reason you’re applying it to the API? Most only apply it to the UI.
When applied to the API, apps and clients that validate the instance by calling
/api/v3/sitewill fail.Thanks for the info, I’ll get to that later.
I think this change broke support for alexandrite.app. It gives “network error”.
voyager cannot connect either fwiw
I’m not sure if it was changed in the intervening time, but I’m writing this comment with Voyager.
Edit: Voyager stopped working after this comment.
Yeah. I can no longer use the instance on Summit now.
For anyone using Summit:
I read up on how Anubis works. As a workaround for now, I think you can get around Anubis by going to Settings > Misc > Client User-agent and choose Use test user-agent 2. Restart the app.
Thank you!!
Yeah, me too
Thought the whole day sopuli was down, until trying the web page
Eternity still works btw
Wouldn’t failing to add a proof-of-work hurdle to the API just be kicking the can down the road?
Ai agent generally only access clear-web pages. Anubis docs explicitly recommend creating exceptions for your api paths.
Possibly? But how are apps supposed to handle that when they expect an API response?
You can always learn something new everyday and I just learned something new about docker
In all fairness it’s so old news, nobody talks about it anymore lol
I think docker warns you if you use docker-compose instead of docker compose? But maybe it doesn’t anymore. I think 3 years ago it did, but now I haven’t used the hyphen version myself.
Would be nice to disable this for
/feeds/endpoints. Most feed readers cannot solve Anubis challenges.Relatable
