-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sprintaddr:getnameinfo: Temporary failure in name resolution #426
Comments
On Thu, Feb 08, 2024 at 12:07:58PM -0800, Joshua Pettus wrote:
One issue I have been having since the very beginning is I keep getting
"sprintaddr:getnameinfo: Temporary failure in name resolution" errors in the log.
Can you run `sslh` under strace and see if something fails
upon resolution?
|
I tried running it under strace. It launches though strace quits once it does. Don't know if this is the output you are looking for I forgot to mention the issue always seemed benign, which is why I took forever reporting it. It just seems odd. strace output
|
ah yes, strace is losing sslh when it forks to detach and create a new session. Can you retry with |
That makes sense! Good to know. I got it to go through the error a few times. Here is the output strace output
Not sure what it means by
That file most certianly exists though it is a simlink to /run/systemd/resolve/resolv.conf as part of systemd's resolver. Could it be taking issue with that? |
It's also failing to find |
I have the same problem, and willing to help the issue results in very slow tls connections to my websites. im also runnung 1.20 |
As a follow up i think it is possible this new behavior was introduced by a system update ( i recently upgraded my ubuntu 20.04 VPS zu 24.04, however prior to upgrading the release i had to upgrade all packages. i think the sslh package is also been upgraded (still on 20.04) and results in this behavior. I currently runn apache2 and added another port not multiplexed by sslh to the configuration. directly connecting to that ports results in fast tls handshake /connection. going over default 443 (and thus multiplexed by sslh) results in um to 20 seconds wait for sucessfull handshake. Observing the sslh logs all slow connections result in a Any way i could provide more useful feedback? Thank you in advance!
vs
|
Hi I'm using sslh-ev 2.0.1. ( I don't think the flavor of sslh is the problem but do let me know and I can give another a try)
One issue I have been having since the very beginning is I keep getting
"sprintaddr:getnameinfo: Temporary failure in name resolution" errors in the log. Which is weird as DNS works just fine for the rest of the machine. It's only sslh complaining.
{edit} the other stuff I was noticing was unrelated
The text was updated successfully, but these errors were encountered: