Open Kangie opened 1 year ago
Confirmed to be a bug gated by ratelimiting envvar
Seems like we're assuming that we'll always get a port and sometimes we get an IP with no port and splitting the port fails.
Thanks for chasing this down, @Kangie!
Isn't that a bug on traefik's side? How can the client not have a TCP port number?
Isn't that a bug on traefik's side? How can the client not have a TCP port number?
Not sure tbh, but even if it is a bug on the traefik side this information is also not something that logpaste needs to function work outside of this single line in the ratelimiting code.
It'd probably be worth raising upstream but if we don't actually need the information, working around it here will be by far the fastest way to get the code working as intended!
I'm not a golang person, and I'm still recovering from RSI so I can't dig into the code yet, but I'm hoping that maybe next month I have time for 'fun' computing, not just essential :)
Enabling
PER_MINUTE_LIMIT
seems to result in (some) failed uploads (HTTP 500s returned to clients) and associatedError retrieving user IP ... missing port in address
entries in the logs.I can't confirm that this envvar/option is the cause of the issue, but it seems to have stopped happening when not trying to rate limit.
Deployment details:
Docker container behind traefik, configured as follows: