[DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066 #1237

Activity

1. IanChokS commented on Mar 15, 2021

   

   IanChokS

   on Mar 15, 2021

   Member

   More actions

   Is it possible to update to the latest tedious version 11.0.6?
2. pawelusfr commented on Mar 22, 2021

   

   pawelusfr

   on Mar 22, 2021

   Last edited by pawelusfr

   More actions

   @IanChokS I'm getting the same warning on 11.0.6
3. pawelusfr commented on Mar 22, 2021

   

   pawelusfr

   on Mar 22, 2021

   More actions

   Looks like servername is being set when calling tls.connect even though I've set an IP address as server address.
4. IanChokS commented on Mar 23, 2021

   

   IanChokS

   on Mar 23, 2021

   Last edited by IanChokS

   Member

   More actions

   I think the same issue has risen on the mssql library which uses tedious under the hood. According to the last comment, it could be "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."

   Edit:

   • Can you try to use the Host name instead of the IP Address name? (stackoverflow source)
   • Another potential work around to silence those messages for now is to run NODE_OPTIONS="--no-warnings" node <...file...> (source)

   Also I think this is because TLS/SSL doesn't verify IP address, but by DNS domain names. In this case, I guess you need to use a host server name.
5. IanChokS commented on Mar 23, 2021

   

   IanChokS

   on Mar 23, 2021

   Last edited by IanChokS

   Member

   More actions

   I think I found the official explanation from RFC 6066, which states:

   Currently, the only server names supported are DNS hostnames;
   ...
   Literal IPv4 and IPv6 addresses are not permitted in "HostName".
   
     It is RECOMMENDED that clients include an extension of type
      "server_name" in the client hello whenever they locate a server by a
      supported name type.
   
      A server that receives a client hello containing the "server_name"
      extension MAY use the information contained in the extension to guide
      its selection of an appropriate certificate to return to the client,
      and/or other aspects of security policy.
   

   Sorry you're running into this issue, but I don't think this is an error in tedious driver as I've also seen other people post this same error warning when connecting to other databases like MongoDB. I'm not sure how to solve this issue, but I hope I provided some helpful links for further guidance.

   Closing this for now!
6. IanChokS

   closed this as completedon Mar 23, 2021
7. fullmooooon commented on Oct 29, 2021

   

   fullmooooon

   on Oct 29, 2021

   More actions

   Change

   Encrypt=true
   

   to

   Encrypt=false
   

   in your code

   for example

   sql.connect('Server=localhost,1433;Database=database;User Id=username;Password=password;Encrypt=false')
   

   👍React with 👍3Reacted by Jackson Felipe Magnabosco, Andres Felipe Olaya Cadena and Mert Şişmanoğlu
8. lpinca

   added a commit that references this issue on Mar 26, 2026

   fix: omit SNI for IP-based hostnames

   ...

   19afe9a
9. arthurschreiber

   added a commit that references this issue on Jul 17, 2026

   fix: omit SNI for IP-based hostnames (#1728)

   ...

   bf871bf