# Issue suddenly with HTTPS Get - because of v3.1.0?
**URL:** https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400
**Category:** General
**Created:** [27 October 2023 15:33 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400 "2023-10-27T15:33:14Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [27 October 2023 15:33 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/1 "2023-10-27T15:33:14Z")
Hi all,
I'm doing a HTTPS GET for MyEnergi data, but I'm suddly getting an error within Node-Red
RequestError: write EPROTO C027C1C9E67F0000:error:0A00010B:SSL routines:ssl3\_get\_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3\_record.c:355:
: [https://s18.myenergi.net/cgi-jstatus-](https://s18.myenergi.net/cgi-jstatus-)\*
However, when I put the URL "[[https://s18.myenergi.net/cgi-jstatus-\*](https://s18.myenergi.net/cgi-jstatus-*)]" in a browser, and enter my creds, it retrieves the data perfectly
I think my system was automatically upgraded to v3.1 and it broke then
Thanks in advance
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [27 October 2023 19:32 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/2 "2023-10-27T19:32:30Z")
Did you also upgrade your version of Node.js?
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [27 October 2023 19:37 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/3 "2023-10-27T19:37:07Z")
> [@championc](#):
>
> my system was automatically upgraded to v3.1
Automatic update is not a standard feature of Node-RED. How / where do you run node-red?
What version of nodejs are you running?
Were you previously using a different version of nodejs?
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [27 October 2023 21:26 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/4 "2023-10-27T21:26:24Z")
I have somehow ended up with v3.1.0. I did a general update of my Linux Mint with apt-get upgrade.
If I downgrade nodejs (I think I was on v18.18.0, can I then downgrade Node-Red?
Or can I resolve my issue without doing that ?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [27 October 2023 21:41 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/5 "2023-10-27T21:41:31Z")
If you upgraded to a new major version of Node.js, you need to rebuild your node.js modules with something like:
```auto
cd ~/.node-red
npm rebuild
```
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [28 October 2023 04:55 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/6 "2023-10-28T04:55:17Z")
So can I go back to Node-Red v3.0.x ?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [28 October 2023 11:09 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/7 "2023-10-28T11:09:53Z")
Well, you can. Node-RED is a node.js app so you can install any version you like. However, you will like still have the same problem. First you should follow my suggestion and see if that fixes it.
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [31 October 2023 13:33 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/8 "2023-10-31T13:33:56Z")
What's the best way to find the location of /.node-red ? It's not in the root.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [31 October 2023 13:44 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/9 "2023-10-31T13:44:54Z")
If you start node-red in a command window it will tell you where it is.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [31 October 2023 16:05 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/10 "2023-10-31T16:05:06Z")
Or do a filing system search.
The default location is the home folder of whatever user is running node-red.
This is all documented.
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [9 November 2023 13:29 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/11 "2023-11-09T13:29:12Z")
Many thanks for your replies
No joy with the npm rebuild
I found a posting about adding options (permitting older TLS versions) when launching node-red. I launch it automatically at startup using PM2.
Where would I go to edit the script that is used to launch node-red to now add an option ?
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [13 November 2023 16:24 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/12 "2023-11-13T16:24:08Z")
BUMP again 😀
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [13 November 2023 17:57 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/13 "2023-11-13T17:57:06Z")
> [@championc](#):
>
> Where would I go to edit the script that is used to launch node-red to now add an option ?
You will want to find out how pm2 is configured. It has its own configuration files.
As maybe I've mentioned (I forget), I install my instances of Node-RED in a much more "node.js like" way which avoids a lot of these issues. See my alternate installer on GitHub for details if interested.
---
### Author:  [@bakman2](https://discourse.nodered.org/u/bakman2)
#### Post date: [13 November 2023 21:52 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/14 "2023-11-13T21:52:22Z")
Did you try to enable the SSL/TLS and then uncheck "verify server verification" in the tls config ?
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [15 November 2023 23:29 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/15 "2023-11-15T23:29:41Z")
I've no idea what you mean, sorry. Can you point me towards something which gies a step by step on this ?
---
### Author:  [@bakman2](https://discourse.nodered.org/u/bakman2)
#### Post date: [16 November 2023 05:46 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/16 "2023-11-16T05:46:11Z")
In the http request node: click "Enable secure (SSL/TLS) connection"
Click the icon on the right
uncheck:Verify server certificate
Update \> done \> deploy
Retry.
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [18 November 2023 15:26 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/17 "2023-11-18T15:26:44Z")
Unfortunately, no joy with that
---
### Author:  [@championc](https://discourse.nodered.org/u/championc)
#### Post date: [9 January 2024 21:13 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/18 "2024-01-09T21:13:11Z")
Just to confirm for the benefit of anyone else with similar issues - I did a full new install, using v3.1 too, and everything works
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [23 January 2024 21:13 UTC](https://discourse.nodered.org/t/issue-suddenly-with-https-get-because-of-v3-1-0/82400/19 "2024-01-23T21:13:40Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.