diff options
| author |  tobi <31960611+tsmethurst@users.noreply.github.com> | 2025-01-23 14:48:09 +0000 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2025-01-23 15:48:09 +0100 |
| commit | b42cb7a802096762cbffb0fa1177c8355898cc1c (patch) | |
| tree | bdd88b6fe32ce32a8fe3b0773209dfb1d5a2df39 /docs/api/ratelimiting.md | |
| parent | [feature] Add `published` property to outgoing AP Actor representations (#3671) (diff) | |
| download | gotosocial-b42cb7a802096762cbffb0fa1177c8355898cc1c.tar.xz | |
[feature] Add warning about `trusted-proxies` to make config easier (#3675)
* [feature] Add warning about `trusted-proxies` to make config easier
* thank you linter, hugs and kisses to you
Diffstat (limited to 'docs/api/ratelimiting.md')
| -rw-r--r-- | docs/api/ratelimiting.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/api/ratelimiting.md b/docs/api/ratelimiting.md index d99f4d379..a3ee7baca 100644 --- a/docs/api/ratelimiting.md +++ b/docs/api/ratelimiting.md @@ -24,11 +24,11 @@ In case the rate limit is exceeded, an [HTTP 429 Too Many Requests](https://deve ### My rate limit keeps being exceeded! Why? -If you find that your rate limit is regularly being exceeded (both for yourself and other callers) during normal use of your instance, it may be that GoToSocial can't tell the clients apart by IP address. You can investigate this by viewing the logs of your instance. If (almost) all logged IP addresses appear to be the same IP address (something like `172.x.x.x`), then the rate limiting will cause problems. +If you find that your rate limit is regularly being exceeded (both for yourself and other callers) during normal use of your instance, it may be that GoToSocial can't tell the clients apart by IP address. You can investigate this by viewing the logs of your instance. If (almost) all logged client IP addresses appear to be the same IP address (something like `172.x.x.x`), then the rate limiting will cause problems. This happens when your server is running inside NAT (port forwarding), or behind an HTTP proxy without the correct configuration, causing your instance to see all incoming IP addresses as the same address: namely, the IP address of your reverse proxy or gateway. This means that all incoming requests are *sharing the same rate limit*, rather than being split correctly per IP. -If you are using an HTTP proxy then it's likely that your `trusted-proxies` is not correctly configured. If this is the case, try adding the IP address of your reverse proxy to the list of `trusted-proxies`, and restarting your instance. +If you are using an HTTP proxy then it's likely that your `trusted-proxies` is not correctly configured. See the [trusted-proxies](../configuration/trusted_proxies.md) documentation for more info on how to resolve this. If you don't have an HTTP proxy, then it's likely caused by NAT. In this case you should disable rate limiting altogether. |