this post was submitted on 03 Apr 2025
10 points (100.0% liked)
Aotearoa / New Zealand
1790 readers
36 users here now
Kia ora and welcome to !newzealand, a place to share and discuss anything about Aotearoa in general
- For politics , please use [email protected]
- Shitposts, circlejerks, memes, and non-NZ topics belong in [email protected]
- If you need help using Lemmy.nz, go to [email protected]
- NZ regional and special interest communities
Rules:
FAQ ~ NZ Community List ~ Join Matrix chatroom
Banner image by Bernard Spragg
Got an idea for next month's banner?
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Also, I have deployed a second lemmy-ui container. We've had some previous discussion about how often the Lemmy.nz website will freeze or stop working while apps and alternate frontends work fine. The second container is load balanced with the first and so the theory is that if Lemmy-ui is being weird you should get directed to the alternate one and so not be impacted too long (there can still be a few seconds if you're being redirected from one to the other, while the server works out if it's down or not).
Also, the Mlmym frontend (old.lemmy.nz) seems to be a prime target for web/AI scrapers, it's responsible for 50% of our traffic and I doubt that's an accurate representation. I have a bunch of rules to block known web scrapers but I have now added a blanket Cloudflare challenge to anyone accessing old.lemmy.nz from outside the country. You should only see it once and then be fine from there. If you're accessing from within NZ you shouldn't see it.
As always, happy to answer any questions 🙂
Is that why every now and then I get random errors or just not loading when I'm browsing on desktop? I've noticed it happening more often lately.
I think it is, and I've also seen it happen more lately as well. Though I feel like it might be that previously the UI would freeze where as after a recent update it seems to go to an error page more often.
I know other instances have the issue (and have had the issue for a while as well), and have reduced the problem by deploying multiple containers for the UI. Hence why I've done it, hopefully it will help 🙂