Closed vladikoff closed 5 years ago
I think you're seeing two errors here. They're merged because rust threading can do that.
We're doing GeoIP lookups, we check the reported Peer address to see if it's a known proxy (currently in 10.0.0.0/8
, 172.16.0.0/12
, & 192.168.0.0/16
, with more addresses available via config).
If it is, we skip it and look at the header candidates for proxy (X-Forwarded-For
, etc.) if all that fails, then we have no idea and consider there to be no remote IP address. That's what the
{"Logger":"channelserver-0.9.0","Type":"channelserver:log","Pid":...,"Severity":3,"Timestamp":...,"Fields":{"msg":"HandlerError { inner: \n\nBad remote address: \"No X-Forwarded-For found for proxied connection\" }","remote_ip":null}}
message is.
What's more concerning is the injected thread crash in the first line. I'm not quite sure I know what triggered that since it looks like a failed clone inside a thread. I'm unable to reproduce that particular example, and I've got a few test cases for the "No X-Forwarded-For found..." error.
not relevant for now , closing