from my perspective its just some worry that your fork might also be abandoned after a while and i'd then need to notice this somehow and look for a different fork - as cold as this may sound, with so many deployments i have to take care of, this can become some amount of risk^^
mmh did some more tuning on the database this morning as the cache hit ratio was a bit low, i hope the calculations for available memory prove to be correct :)
Thats about a (potentially) unrelated issue with the web application. I am lucky that i checked as i first discarded the problem due to similar symptoms until somebody told me things are still slow.
At least for this time, it appears some child wrote a bad crawling bot, heavily hammering the instance with requests for posts, comments and stuff - and i think they knew as they hide behind a vpn. For now things should be better as i did some short term measures and i am trying to better prevent such actions better.. hoping for the best.
Its people like this who should donate lol.
I kinda lost track on my Anubis deployments, it appears here i only have a useragent blacklist so its time to give it prio for lemmy as well. However i worry whether that is sufficient.
(while things are much healthier again, i acknowledge that at least in the webui, its not as fast as it should be)
oh, sometimes lemmy-ui needs a restart, usually the first 504 from the monitoring would be the signal for me but i didn’t notice this in a while - i was actually just wondering about it. will check on it asap, matrix is unrelated
edit: restarted. and indeed here and there i am already deploying anubises - just not too happy to seemingly have to do one instance per domain - even if i can update them using watchtower and have them share a configuration file... even lost track a little about where i have put them already lol
i have added some headers (most interesting perhaps slice) - however arte currently times out when testing, aeharding does not seem to present opengraph stuff to test, peertube seemed to work normally before my adjustments
playing back an uploaded video didnt look like it was sliced however it played without showing any obvious errors anywhere
i have added proxy_hide_header Access-Control-Allow-Origin; which seems to help with that reflected origin
sorry, i had noticed that the monitoring was triggered a little while ago which indicates that its time to restart the frontend to mitigate this issue, but i forgot
will look into an alternative frontend but not sure if that would see much use
i try to investigate but its a bit tricky - could you confirm that this does not happen in apps? from my tests it looks like its actually a problem with the lemmy-ui itself. not lemmy or another component, as when moments where i cannot curl the ui on server level, i still can curl the lemmy server for example
i sadly struggle gathering helpful logs but i am confident the cause will be found
🚀 A big thank you to you kind donors. Last month all records were broken in a big spike of not only incoming donations by person count, but also with the total amount. Approximated 281 people decided to donate vs 199 the month before. While some of you went with mindblowing one-time or yearly donations (hey, i was asking for monthly micro!-donations xD), it would be amazing if this actually results in more average monthly donors.
Looking at those numbers actually leaves me a bit speechless... just.. wow. Thanks a ton!
Thank you! I was actually quite insecure about the effect such a detailed page could have, but it didn't actually seem to make any negative impact, which is awesome. It's fun to figure out how to to generate the stuff on there automated. :)
meine jüngsten fahrten und läufe ins gewitter hatte ich allerdings vorher regenradar geschaut :/
from my perspective its just some worry that your fork might also be abandoned after a while and i'd then need to notice this somehow and look for a different fork - as cold as this may sound, with so many deployments i have to take care of, this can become some amount of risk^^
i notice thats a fork of a fork, whats going on there?
mmh did some more tuning on the database this morning as the cache hit ratio was a bit low, i hope the calculations for available memory prove to be correct :)
thank you for the info but no, there was no helpful identification, the useragent was pretty generic
Thats about a (potentially) unrelated issue with the web application. I am lucky that i checked as i first discarded the problem due to similar symptoms until somebody told me things are still slow.
At least for this time, it appears some child wrote a bad crawling bot, heavily hammering the instance with requests for posts, comments and stuff - and i think they knew as they hide behind a vpn. For now things should be better as i did some short term measures and i am trying to better prevent such actions better.. hoping for the best.
Its people like this who should donate lol.
I kinda lost track on my Anubis deployments, it appears here i only have a useragent blacklist so its time to give it prio for lemmy as well. However i worry whether that is sufficient.
(while things are much healthier again, i acknowledge that at least in the webui, its not as fast as it should be)
sorry about that, have not noticed this in monitoring, nor in browser, otherwise i would have restarted lemmy-ui. i have done so now.
Sorry should be better now.
oh, sometimes lemmy-ui needs a restart, usually the first 504 from the monitoring would be the signal for me but i didn’t notice this in a while - i was actually just wondering about it. will check on it asap, matrix is unrelated
edit: restarted. and indeed here and there i am already deploying anubises - just not too happy to seemingly have to do one instance per domain - even if i can update them using watchtower and have them share a configuration file... even lost track a little about where i have put them already lol
i have added some headers (most interesting perhaps slice) - however arte currently times out when testing, aeharding does not seem to present opengraph stuff to test, peertube seemed to work normally before my adjustments
playing back an uploaded video didnt look like it was sliced however it played without showing any obvious errors anywhere
i have added
proxy_hide_header Access-Control-Allow-Origin;which seems to help with that reflected originsorry, i had noticed that the monitoring was triggered a little while ago which indicates that its time to restart the frontend to mitigate this issue, but i forgot
will look into an alternative frontend but not sure if that would see much use
i try to investigate but its a bit tricky - could you confirm that this does not happen in apps? from my tests it looks like its actually a problem with the lemmy-ui itself. not lemmy or another component, as when moments where i cannot curl the ui on server level, i still can curl the lemmy server for example
i sadly struggle gathering helpful logs but i am confident the cause will be found
interesting i primarely use an app and everything seems responsive. will try to investigate
🚀 A big thank you to you kind donors. Last month all records were broken in a big spike of not only incoming donations by person count, but also with the total amount. Approximated 281 people decided to donate vs 199 the month before. While some of you went with mindblowing one-time or yearly donations (hey, i was asking for monthly micro!-donations xD), it would be amazing if this actually results in more average monthly donors.
Looking at those numbers actually leaves me a bit speechless... just.. wow. Thanks a ton!
first fork i noticed and following with careful amount of hope: https://github.com/we-promise/sure
Thank you very much! Don't overdo it ;)
Thanks for your support and kind words!
Thank you!
Thank you! I was actually quite insecure about the effect such a detailed page could have, but it didn't actually seem to make any negative impact, which is awesome. It's fun to figure out how to to generate the stuff on there automated. :)