▲ 171 ▼ [PSA] Admins: Watch for the antiyanks troll and consider adjusting your rate limits (lemmy.world) submitted 1 year ago by admiralpatrick@lemmy.world to c/fediverse@lemmy.world 47 comments fedilink hide all child comments
[+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (13 children) [deleted] permalink fedilink source parent hideshow 13 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (12 children) Yes, I see this there. Most of the nginx config is from the 'default' nginx config in the Lemmy repo from a few years ago. My understanding is somewhat superficial - I don't actually know where the variable '$proxy_add_x_forwarded_for' gets populated, for example. I did not know that this contained the client's IP. # backend location ~ ^/(api|pictrs|feeds|nodeinfo|.well-known) { proxy_pass http://0.0.0.0:8536/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; # Rate limit limit_req zone=mander_ratelimit burst=30000 nodelay; # Add IP forwarding headers proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } I need to do some reading 😁 permalink fedilink source parent hideshow 12 child comments replies: [+] admiralpatrick@lemmy.world [S] 1 point 1 year ago (11 children) [deleted] permalink fedilink source parent hideshow 11 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (10 children) Thanks! I was able to crash the instance for a few minutes, but I think I have a better idea of where the problem is. Ths $emote_addr variable seems to work just the same. In the rate limit options there is a limit for ''Message''. Common sense tells me that this means 'direct message', but setting this to a low number is quite bad. While testing I eventually set it to '1 per minute' and the instance became unresponsive until I modified the settings in the database manually. If I give a high number to this setting then I can adjust the other settings without problem. permalink fedilink source parent hideshow 10 child comments replies: [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago (9 children) [deleted] permalink fedilink source parent hideshow 9 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (8 children) So, ultimately my problem was that I was trying to set all of the limits to what I thought were "reasonable" values simultaneously, and misunderstood what 'Message' meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed 'Messages' refer to API calls and not direct messages, and that there is no 'Direct Message' rate limit. If I let 'Messages' stay high I can adjust the other values to reasonable values and everything works fine. Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁 permalink fedilink source parent hideshow 8 child comments replies: [–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent
[–] Sal@mander.xyz 4 points 1 year ago (12 children) Yes, I see this there. Most of the nginx config is from the 'default' nginx config in the Lemmy repo from a few years ago. My understanding is somewhat superficial - I don't actually know where the variable '$proxy_add_x_forwarded_for' gets populated, for example. I did not know that this contained the client's IP. # backend location ~ ^/(api|pictrs|feeds|nodeinfo|.well-known) { proxy_pass http://0.0.0.0:8536/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; # Rate limit limit_req zone=mander_ratelimit burst=30000 nodelay; # Add IP forwarding headers proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } I need to do some reading 😁 permalink fedilink source parent hideshow 12 child comments replies: [+] admiralpatrick@lemmy.world [S] 1 point 1 year ago (11 children) [deleted] permalink fedilink source parent hideshow 11 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (10 children) Thanks! I was able to crash the instance for a few minutes, but I think I have a better idea of where the problem is. Ths $emote_addr variable seems to work just the same. In the rate limit options there is a limit for ''Message''. Common sense tells me that this means 'direct message', but setting this to a low number is quite bad. While testing I eventually set it to '1 per minute' and the instance became unresponsive until I modified the settings in the database manually. If I give a high number to this setting then I can adjust the other settings without problem. permalink fedilink source parent hideshow 10 child comments replies: [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago (9 children) [deleted] permalink fedilink source parent hideshow 9 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (8 children) So, ultimately my problem was that I was trying to set all of the limits to what I thought were "reasonable" values simultaneously, and misunderstood what 'Message' meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed 'Messages' refer to API calls and not direct messages, and that there is no 'Direct Message' rate limit. If I let 'Messages' stay high I can adjust the other values to reasonable values and everything works fine. Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁 permalink fedilink source parent hideshow 8 child comments replies: [–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent
[+] admiralpatrick@lemmy.world [S] 1 point 1 year ago (11 children) [deleted] permalink fedilink source parent hideshow 11 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (10 children) Thanks! I was able to crash the instance for a few minutes, but I think I have a better idea of where the problem is. Ths $emote_addr variable seems to work just the same. In the rate limit options there is a limit for ''Message''. Common sense tells me that this means 'direct message', but setting this to a low number is quite bad. While testing I eventually set it to '1 per minute' and the instance became unresponsive until I modified the settings in the database manually. If I give a high number to this setting then I can adjust the other settings without problem. permalink fedilink source parent hideshow 10 child comments replies: [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago (9 children) [deleted] permalink fedilink source parent hideshow 9 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (8 children) So, ultimately my problem was that I was trying to set all of the limits to what I thought were "reasonable" values simultaneously, and misunderstood what 'Message' meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed 'Messages' refer to API calls and not direct messages, and that there is no 'Direct Message' rate limit. If I let 'Messages' stay high I can adjust the other values to reasonable values and everything works fine. Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁 permalink fedilink source parent hideshow 8 child comments replies: [–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent
[–] Sal@mander.xyz 4 points 1 year ago (10 children) Thanks! I was able to crash the instance for a few minutes, but I think I have a better idea of where the problem is. Ths $emote_addr variable seems to work just the same. In the rate limit options there is a limit for ''Message''. Common sense tells me that this means 'direct message', but setting this to a low number is quite bad. While testing I eventually set it to '1 per minute' and the instance became unresponsive until I modified the settings in the database manually. If I give a high number to this setting then I can adjust the other settings without problem. permalink fedilink source parent hideshow 10 child comments replies: [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago (9 children) [deleted] permalink fedilink source parent hideshow 9 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (8 children) So, ultimately my problem was that I was trying to set all of the limits to what I thought were "reasonable" values simultaneously, and misunderstood what 'Message' meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed 'Messages' refer to API calls and not direct messages, and that there is no 'Direct Message' rate limit. If I let 'Messages' stay high I can adjust the other values to reasonable values and everything works fine. Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁 permalink fedilink source parent hideshow 8 child comments replies: [–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent
[+] admiralpatrick@lemmy.world [S] 0 points 1 year ago (9 children) [deleted] permalink fedilink source parent hideshow 9 child comments replies: [–] Sal@mander.xyz 4 points 1 year ago (8 children) So, ultimately my problem was that I was trying to set all of the limits to what I thought were "reasonable" values simultaneously, and misunderstood what 'Message' meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed 'Messages' refer to API calls and not direct messages, and that there is no 'Direct Message' rate limit. If I let 'Messages' stay high I can adjust the other values to reasonable values and everything works fine. Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁 permalink fedilink source parent hideshow 8 child comments replies: [–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent
[–] Sal@mander.xyz 4 points 1 year ago (8 children) So, ultimately my problem was that I was trying to set all of the limits to what I thought were "reasonable" values simultaneously, and misunderstood what 'Message' meant, and so I ended up breaking things with my changes without the reason being obvious to me. I looked into the source code and I can see now that indeed 'Messages' refer to API calls and not direct messages, and that there is no 'Direct Message' rate limit. If I let 'Messages' stay high I can adjust the other values to reasonable values and everything works fine. Thanks a lot for your help!! I am surprised and happy it actually worked out and I understand a little more 😁 permalink fedilink source parent hideshow 8 child comments replies: [–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent
[–] BlueEther@lemmy.nz 1 point 1 year 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? permalink fedilink source parent hideshow 5 child comments replies: [–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent [+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent
[–] Sal@mander.xyz 1 point 1 year ago (2 children) Sorry, I went to sleep. Glad you were able to sort it out 😄 permalink fedilink source parent hideshow 2 child comments replies: [–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent
[–] BlueEther@no.lastname.nz 2 points 1 year ago (1 child) All good, taught me again not to rely on chatGPT. I even said I needed to find the right BD table and field and it lead me down a rabbit hole of editing config/env files Fuck AI permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent
[–] Sal@mander.xyz 1 point 1 year ago Haha, yeah, trusting ChatGPT with how to manipulate the database and change config files is a risky move 😆 I did use it myself to remind me of the postgresql syntax to find and alter the field. permalink fedilink source parent
[+] admiralpatrick@lemmy.world [S] 0 points 1 year ago* (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent
[–] BlueEther@lemmy.nz 3 points 1 year ago local_site_rate_limit Thanks: UPDATE local_site_rate_limit SET message = 999, message_per_second = 999 WHERE local_site_id = 1; permalink fedilink source parent
[+] admiralpatrick@lemmy.world [S] -1 points 1 year ago (1 child) [deleted] permalink fedilink source parent hideshow 1 child comment replies: [–] Sal@mander.xyz 3 points 1 year ago 😁 👍 permalink fedilink source parent