After #250, mssql's driver connects to its server on 127.0.0.1. On the live machines, Node 25 refuses an IP address as the TLS server name, so every connection failed:
Failed to connect to 127.0.0.1:4848 - The property 'options.servername' Setting the TLS ServerName to an IP address is not permitted
When the host is an address, the driver now names localhost for TLS. The certificate is trusted explicitly, as before, so the name only has to be one TLS accepts. The module typechecks and its tests pass, 4 of 4.
After #250, mssql's driver connects to its server on 127.0.0.1. On the live machines, Node 25 refuses an IP address as the TLS server name, so every connection failed:
```
Failed to connect to 127.0.0.1:4848 - The property 'options.servername' Setting the TLS ServerName to an IP address is not permitted
```
When the host is an address, the driver now names `localhost` for TLS. The certificate is trusted explicitly, as before, so the name only has to be one TLS accepts. The module typechecks and its tests pass, 4 of 4.
Node 25 refuses an IP address as the TLS server name, and the module reaches its server on
loopback, so every connection failed on the live machines. The certificate is trusted either way.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After #250, mssql's driver connects to its server on 127.0.0.1. On the live machines, Node 25 refuses an IP address as the TLS server name, so every connection failed:
When the host is an address, the driver now names
localhostfor TLS. The certificate is trusted explicitly, as before, so the name only has to be one TLS accepts. The module typechecks and its tests pass, 4 of 4.