Hayden Pearce
Hayden Pearce
I had thought for a while there that I could trigger it with service restarts, but apparently that was just a string of flukes on my end. I can however...
Not personally, no. All my upstreams are local Do53.
Thank you for your time. Long time listener, first time caller, as it were. I'm a big fan of the project. I'm not yet anywhere near as familiar with Go...
I just ended up hard-coding the value at 1232 in my builds (which it looks like potter may have also done in the linked duplicate). There doesn't appear to be...
Hello, and thank you for the report. I think I have a hunch as to what's happening here. Where was your port modification to the lighttpd configuration made? If it...
This one is puzzling me. There's so vanishingly few mentions of this error, and almost zero that involve nginx or lighttpd in any way. Just to be certain, is the...
To be clear the particular example here is router/192.168.1.1, which AGH maintains has a grand total of 5 queries, whereas the query log lists several thousand. This isn't the only...
If you expand this outside of HTTPS, and also look towards TLS and QUIC (and H3?), the same problems are realised without the (IMO flawed) argument of "well ahhckshully …you're...
And as I attempted to point out, the web interface would still be accessible via QUIC, so it's mostly a moot point I think.
Sharing ports isn't ultimately the issue I don't think. The issue is resolution capabilities and web administration interface listening address/interface not being able to be decoupled, _and/or_ the lack of...