Toby Chui
Toby Chui
@zen8841 Maybe if you can take a look at this and see if you got any interest in working on this?
@pkirsche That is the uptime monitor. I think you have an upstream mis-configed. Try uncheck the "Require TLS" in the upstream options. Btw, talking about the random port, it is...
@pkirsche No. it was from the dpcore and it is considered as important log (which means there is setup that goes wrong somewhere, maybe in your upstream?). If everything is...
@klisza1993 Interestingly though, there are no changes in the code regarding ACME and certificate auto-update process except of the early renew date is now user config-able via start parameters. So...
Hey @marchein > If my client has the ip 10.0.11.123, I would expect the proxied host to receive the request from 10.0.11.123, not 10.0.11.6. Showing the request coming from Zoraxy...
@marchein Wait, that doesn't sounds right. As stated [here](https://serverfault.com/questions/846489/can-x-forwarded-for-contain-multiple-ips) and [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For#examples) , the correct sequence for appending to `X-Forwarded-For` is `X-Forwarded-For: , , ` Zoraxy is the last proxy in...
@marchein Because by default nginx will not proxy anything unless you add it to config, while Zoraxy by default is add all the common sets of required headers to the...
It seems like someone is trying to break into your server. By default Zoraxy don't use that port, but since the ACME module will automatically find a spare port to...
@AndyRap I don't see any problem in the log. I see the log is printed by [router:blacklist] which means the request has been handled by access list handler.
> Are you saying that these two are entirely coincidental, not related at all and therefore there is zero possible issue? Yes, these are two different issues. As I have...