![]() However, instead of being able to write “17.9.0” in the box next to specific version, Virtualmin prefills 18.2.0 in the dropdown, and there’s no way to specify 17.9.0 instead. I then went to update the live (as opposed to staging) site from 17.8.0 to 17.9.0, and assumed I’d be able to do that easily. I was able to do this for the staging site that I’d broken by going into Virtualmin > Install Scripts > Node.js > filling in 17.9.0 and “upgrading” to that older version. Unfortunately there’s an issue with Node.js 18.x.x no longer support CentOS 7 and similar distros: see NodeJS 18 revert to building on CentOS 7, RHEL 7, Ubuntu Bionic 18.04, other other LTS distros Īfter investigating further (thinking at first I could update libstdc++), I realized I needed to roll back to Node.js 17.x.x I recently did what I thought would be a routine update to Node.js from 17.8.0 to 18.2.0, using your Install Scripts in Virtualmin (an update process I do from time to time). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |