Skip to content

Error connecting to the SQL Server #55

Description

@asins

Veloxdb connecting error:
MSSQL TDS handshake failed: An error occured during the
attempt of performing I/0: No more packets in the wire
Check host,port, database name, user, password,and
network access, then try again.

❯ openssl s_client -connect 192.168.3.3:1433
Connecting to 192.168.3.3
CONNECTED(00000003)
C062B7FD01000000:error:0A000126:SSL routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:703:
---
no peer certificate available
---
No client certificate CA names sent
Negotiated TLS1.3 group: <NULL>
---
SSL handshake has read 0 bytes and written 1529 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Protocol: TLSv1.3
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
C062B7FD01000000:error:0A000197:SSL routines:SSL_shutdown:shutdown while in init:ssl/ssl_lib.c:2804:

During connection, the SSL mode is already set to connection.disable.

However, I can connect properly using SQLPro Studio. This is likely related to the connection protocol used. After making some queries, it seems that setting forceencryption = 0 can be used to force an unencrypted connection method to access the service (of course, this applies in a private network environment). Is it possible for the software to allow such a setting directly?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions