-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Remove sqlx features due to a bug in rustls/webpki failing to resolve IP addresses #2391
Comments
Here is a simple fix to resolve this issue #2392 |
i got this error error occurred while attempting to establish a TLS connection: InvalidDNSNameError . it worked fine on my main machine . i tried to remove the features sqlx runtime i get another error |
You need to specify a runtime, you can use the |
I'm considering this an upstream isusue: #2392 (comment). |
Yeah, I read that comment, I think that may be a suitable idea. |
Looks like the new rustls release fixes this! Shall we update dependencies and see if that's so? |
I updated rustls in Rocket in fbb0ace. I also sent a PR to sqlx to update rustls there as well (launchbadge/sqlx#2440). Since there's no issue on Rocket's end, and everything we could do from our side is now complete, I'm closing this out. |
That's great! So once sqlx updates rustls on their end, everything should be good to go right? |
Yup! It should just work if you |
Description
Currently
sqlx
indb_pools
usesruntime-tokio-rustls
as its feature. This has a bug which results in aInvalidDNSNameError
for raw IP addresses as a part of the url. This is being fixed, however, it would be nice to let the user choose their TLS back-end.To Reproduce
Setting the database url to a raw IP address as follows:
Expected Behavior
The IP shouldn't need any DNS resolution.
Environment:
Additional Context
A simple fix is to remove the feature from sqlx, and let the user choose the backend.
The text was updated successfully, but these errors were encountered: