BlueEther

joined 2 years ago
[–] BlueEther@lemmy.nz 4 points 1 day ago

as someone with their heavy goods, 10 ton behind a pickup is terrifying

[–] BlueEther@lemmy.nz 12 points 2 days ago

If you have DB access, the values are in the local_site_rate_limit table. You’ll probably have to restart Lemmy’s API container to pick up any changes if you edit the values in the DB.

100 per second is what I had in my configuration, but you may bump that up to 250 or more if your instance is larger.

Fixed:

UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1;

[–] BlueEther@lemmy.nz 3 points 2 days ago

local_site_rate_limit

Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1;

[–] BlueEther@lemmy.nz 2 points 2 days ago (5 children)

Hi I think I set the messages too low as well and now no.lastname.nz is down, pointers on how to fix with no frontend?

[–] BlueEther@lemmy.nz 3 points 2 days ago

how did you fix?

[–] BlueEther@lemmy.nz 11 points 2 days ago (1 children)

ok, I fucked up and now my instance is erroring :(