Displaying 5 results from an estimated 5 matches for "nodesourc".
Did you mean:
nodesource
2020 Apr 22
1
nodejs version 14
Hi All,
I was following the instructions for installing nodejs version 14.
https://github.com/nodesource/distributions
First thing was:
curl -sL https://rpm.nodesource.com/setup_14.x | bash -
After that :
yum -y install nodejs
---> Package nodejs.x86_64 2:12.16.2-1nodesource will be installed
--> Finished Dependency Resolution
You can see its installing the OLD Version 12. not the 14. ??? W...
2019 Aug 28
2
I broke "yum update" - C7
...x86_64 error was
14: curl#60 - "Peer's Certificate issuer is not recognized."
* base: mirrors.clouvider.net
* epel: mirrors.coreix.net
* extras: mirrors.clouvider.net
* remi-php72: mirror.netweaver.uk
* remi-safe: mirror.netweaver.uk
* updates: mirrors.vooservers.com
https://rpm.nodesource.com/pub_6.x/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized."
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a p...
2015 Dec 17
0
curl problem
Hello,
curl (yum upgrade) stopped with this errormessage:
https://rpm.nodesource.com/pub/el/7/x86_64/repodata/repomd.xml: [Errno
14] curl#60 - "Peer's Certificate issuer is not recognized."
whats happend?
thx.
Joey
2019 Aug 29
0
I broke "yum update" - C7
...| 3.4 kB 00:00:00
google-chrome | 1.3 kB 00:00:00
https://rpm.nodesource.com/pub_6.x/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized."
Trying other mirror.
It was impossible to connect to the CentOS servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a p...
2019 Aug 29
4
I broke "yum update" - C7
On Wednesday 28 August 2019 22:41:24 Jonathan Billings wrote:
> If it?s really out of date, you might need to update the ca-certificates package, but that?d have to be a really old system.
>
> I?d suggest by checking to make sure the clock on your computer isn?t really out of date. If its right, I?d double-check with ?curl? to see if you aren?t getting a MitM response, where your HTTPS