-
Notifications
You must be signed in to change notification settings - Fork 95
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
Cannot connect to MSSQL server #676
Comments
Interesting. Can you please send the full verbose logs here? You can collect logs by launching SQLPage from your terminal with
Can you also check the encryption setting of your database server and return the logs from the server from the time of the error of you have them? |
@lovasoa Logs (please help me check for any sensitive information):
|
Thank you. Maybe the database does not support encrypted connections? Can you try connecting with encryption disabled, and report the same logs? You can disable encryption by adding |
@lovasoa Yes, you are right. It works fine after adding I couldn't find this option in the configuration.md. Can we include it? |
Yes, I'll add a reference to supported connection string parameters. Even better, we should be able to make it just work by default. We currently support both fully encrypted and fully cleartext connections, but I suspect your database expects sql server's third mode, that is partially encrypted connections where only the password is encrypted. We should add support for that too. |
Alright, we can give it a try. |
Hello, I cannot connect to the MSSQL server in the production environment (previously I was connecting to the local server).
database_url:
mssql://user:password@ip:1433/DB
Error:
[2024-11-07T03:43:56.138Z WARN sqlpage::webserver::database::connect] Failed to connect to the database: error communicating with database: tls handshake eof. Retrying in 5 seconds.
Could this be an issue with the SSL certificate?
Version information
windows 10 Simplified Chinese zh-CN
MSSQL 2012
sqlpage 0.30.1
The text was updated successfully, but these errors were encountered: