i2pd warn - Destination: Publish confirmation was not received in 1800 milliseconds. Should I be concerned?
Hi @dxione, that warning is normal i2pd chatter. i2pd logs a lot of this kind of retry/timing noise even though it’s routine network variance, not an error.
I’d only worry if the service behind that destination is actually unreachable, or if you’re seeing this on basically every publish cycle rather than occasionally. Is that the case?