Hello. Very often, an error (Slow down, too Many Requests from this IP Address) started to appear when surfing the site. Also, periodically the Discourse cannot load some script, I assume that this is a consequence of the same problem
Disabled all plugins - the error does not disappear. This situation is from a home computer and a work computer, the ip is respectively different. Tell me what could be the problem.
Discourse v 2.6.0.beta2
Logs:
Uncaught Error: Too Many Requests
Url: /assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js
Line: 1
Column: 268124
Backtrace
Error: Too Many Requests
at /assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:267890
at /assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:267993
at o (/assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:268074)
at Object.trigger (/assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:545343)
at /assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:550189
at t.invoke (/assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:490190)
at e.t.flush (/assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:489198)
at e.t.flush (/assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:491205)
at e.t._end (/assets/ember_jquery-1ed3f3559e6f967733b4088aa729ff7039dff2c09c5a5f787a214b016f58aabc.js:1:496596)
Env
That’s likely the issue then. You might be able to get the two ip of the proxy passes a proxy header. Otherwise you’ll need to disable (or modify) the rate limiting template and how you don’t get slammed.
If it’s your at home that’s getting this (on your own ip) then perhaps you have some theme component that’s reloading a bunch of data
You need to know which problem it is before you know how and where to fix it.
Try disabling all third-party code and let us know if the problem persists. You can do this easily by creating a new theme with no theme components and using that.
I’ve taken a look at @varhall’s site and it is behind some kind of reverse proxy.
@Varhall - your server admin needs to take a look at this topic, particularly the Create an NGINX ‘site’ for the outer nginx section. They aren’t currently passing the client IP address to the proxied Discourse instance. Discourse currently sees all traffic as originating from the same computer, which is why you see that error.