Repository navigation
DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. #884
Description
If set
options: { encrypt: true }
And send large data (83kb) to MS SQL then
at Socket.emit (events.js:205:15) at errorOrDestroy (internal/streams/destroy.js:107:12) at onwriteError (_stream_writable.js:438:5) at onwrite (_stream_writable.js:459:5) at internal/streams/destroy.js:49:7 at Socket._destroy (net.js:593:3) at Socket.destroy (internal/streams/destroy.js:37:8) at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:84:12) { code: 'EREQUEST', number: undefined, lineNumber: undefined, state: undefined, class: undefined, serverName: undefined, procName: undefined, originalError: Error: Connection lost - write EPIPE code: 'EREQUEST', number: undefined, lineNumber: undefined, state: undefined, class: undefined, serverName: undefined, procName: undefined, originalError: Error: Connection lost - write EPIPE
Software versions
- NodeJS: 12.4.0
- node-mssql: 5.1.0
- SQL Server: 2016
Activity
dhensby commentedon Jul 2, 2019
This is most likely a problem with the underlying driver, then. You haven't completed the issue template in full so I can't provide any further help
arkasaha2 commentedon Oct 30, 2019
I also faced the same issue. But it was resolved when I downgraded my node version to 10 and my same code started working. There has to be some issue with mssql with node 12.
Vizzr commentedon Mar 6, 2020
Same issue here.
Node : 13.8.0
Mssql : 6.1.0
We connect to the database using an IP address.
Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
dhensby commentedon Mar 6, 2020
@Vizzr set
encrypt: false, maybe?willmorgan commentedon Mar 6, 2020
This is a universal issue with cloud DB service providers with SSL connections, and not a problem with this library.
Would recommend investigating configuration options on the cloud DB service provider.