### Author:  [@Nxito](https://discourse.nodered.org/u/Nxito)
#### Post date: [3 February 2021 15:51 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/1 "2021-02-03T15:51:08Z")
I have recently updated node-red to 1.2.7 and nodejs to 14.15.4, and while I was testing it I have seen that the sql nodes I use (node-red-contrib-mssql-plus) give me an error.
Not long ago I published if there could be problems when updating directly and I decided to try it on a Virtual Machine with linux.
I test to do the Telnet command and it works fine
However, I have run into an error and I would not know how to fix it even looking in google.
I will leave the error here and any link that I found:
>
>
> Hi, anyone,
> as title mentioned, the worked code with node 10, not work with node 12, it report:
> Connection lost - 3540:error:1425F102:SSL routines:ssl\_choose\_client\_version:unsupported...
maybe I should post this on github, but since I didn't find anything here, I thought about posting it here directly
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [3 February 2021 22:07 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/2 "2021-02-03T22:07:21Z")
Are you using the very latest version of mssql-plus? Look in the connection settings for "Trust Certificate" - is that checked? Try toggling it, then deploy.
Please let me know if this fixes your issue.
---
### Author:  [@Nxito](https://discourse.nodered.org/u/Nxito)
#### Post date: [4 February 2021 09:45 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/3 "2021-02-04T09:45:12Z")
sorry for taking a long time to respond, I've been running the tests today
The result according to me, is the version of node.js
I tried the version
- 10.15 from nodejs
- 1.0.0 node-red
- 0.4.4 node-red-contrib-mssql-plus
it worked
update node-red and node-red-contrib-mssql-plus to the version i use
- 10.15 from nodejs
- 1.2.7 node-red
- 0.6.4 node-red-contrib-mssql-plus
it worked
update nodejs to version 14.15.4
- 14.15.4 from nodejs
- 1.2.7 node-red
- 0.6.4 node-red-contrib-mssql-plus
The error appeared
I thought that it could be an error from my server or from the linux virtual machine, that's why I tried it again with windows 10 getting the same results
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [4 February 2021 09:50 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/4 "2021-02-04T09:50:54Z")
On the non working W10 machine, did you check and toggle "Trust Certificate" in the connection settings?
There was a recent change in underling `tedious` sql code that forces the default to NOT trust.
### TEST 1...
can you try toggle that new setting, deploy, test, toggle back, deploy, test.
* * *
### TEST 2...
Try adding `--tls-min-v1.0` to the `node` switches.
(typically on windows `node.red.cmd` is here `C:\Users\username\AppData\Roaming\npm\node-red.cmd` but you can find it by entering `where node-red` in a cmd window).
---
### Author:  [@Nxito](https://discourse.nodered.org/u/Nxito)
#### Post date: [4 February 2021 10:43 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/5 "2021-02-04T10:43:27Z")
> [@Steve-Mcl](#):
>
> --tls-min-v1.0
Finally that solved my problem
I was trying to run node red with that command, when I should have put it inside node-red.cmd
Even if it is a solution, I do not think it is the most reliable to configure the command every time you want to install a new instance
One last question, how do I incorporate this in linux, there is no node-red.cmd in my installation
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [4 February 2021 11:29 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/6 "2021-02-04T11:29:41Z")
> [@Nxito](#):
>
> how do I incorporate this in linux, there is no node-red.cmd in my installation
Enter `which node-red` in a terminal. What do you see? There is a batch/script file that launches node-red (can't check right now, someone else might pop in and provide an answer).
Long term, there may be a means of entering this in the connection settings in the MSSQL-plus node (unsure) but if I add it, are you in a position to test it & feedback?
---
### Author:  [@Nxito](https://discourse.nodered.org/u/Nxito)
#### Post date: [4 February 2021 11:40 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/7 "2021-02-04T11:40:01Z")
> [@Steve-Mcl](#):
>
> Enter `which node-red` in a terminal
/urs/bin/which: no node-red in (/usr/local/sbin:/usr/local/bin .......
i have installed node-red with npm in /apps/node-red. That's why I'm pretty sure about the node-red files I have
there is a node-red file but not the cmd
> [@Steve-Mcl](#):
>
> are you in a position to test it & feedback?
I can try something on the weekends, since this was due to a service that I was doing at work
I will investigate a little more to see if I can get this to start in linux
I will be attentive to new updates of the node 😉
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [4 February 2021 12:11 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/8 "2021-02-04T12:11:16Z")
> [@Nxito](#):
>
> there is a node-red file but not the cmd
There wouldn't be on Linux. It'll be the `node-red` file. Edit it with gedit or nano or vim or whatever you use / have.
---
### Author:  [@Nxito](https://discourse.nodered.org/u/Nxito)
#### Post date: [4 February 2021 12:36 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/9 "2021-02-04T12:36:43Z")
> [@Steve-Mcl](#):
>
> EdÃtelo con gedit o nano
I use nano.
node-red file is very similar to red.js
however I have found that the first line of the code uses something called "shebang", the first time I see it, I am not used to linux scripts
I have seen that this does not support parameters ... as it would be --tls-min-v1.0
>
If one of these days I find the solution, I will leave it here written
---
### Author:  [@Nxito](https://discourse.nodered.org/u/Nxito)
#### Post date: [4 February 2021 16:47 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/10 "2021-02-04T16:47:16Z")
@Steve-Mcl ,so much so that the solution is a simple click.
If I needed to connect to azure I could not, but to the local database I can
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [4 February 2021 17:37 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/11 "2021-02-04T17:37:35Z")
@Nxito I should have asked - I assumed you wanted to use encryption (otherwise I would have told you so check that) DOH!
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [18 February 2021 17:38 UTC](https://discourse.nodered.org/t/mssql-eproto-error-after-updating-nodejs-and-node-red/40323/12 "2021-02-18T17:38:06Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.