New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Don't update Virtualizor to 3.1.7 (6)
If anybody here is using Virtualizor don't update to version 3.1.7 (6) it will break your Debian based Setup or templates
None of the Debian Templates will work with this Version, it basically breaks SSH, you will need to manually login via VNC and fix SSH for all the Debian based VPS.
And when contacted, they are just giving a php file that needs to be updated in all the VPS nodes manually to fix it.
So do consider it before updating Virtualizor
Comments
@MannDude
Oh God my virtualizor are automatically updated. My user are using Debian generally.
Just submit a ticket, they will give you a file, upload it on all your servers to fix it
Thanks for your information. I Will contact them .
Fun.
Luckily, auto-updates are off. (Thanks for the heads up)
They've released an update to fix it: https://www.virtualizor.com/blog/virtualizor-3-1-7-7-release-candidate/
Though keep in mind it's in RC, not stable. Just an option perhaps for those who don't want to do manual patching.
updated to this version, but still debian template has same issue
For anyone who have this problem:
Create a new vps from debian template with 3 GB of disk.
Login to it and create new cron with
crontab -e
And put
@reboot ssh-keygen -A
to end of the cron file.Save.
Shutdown vps, delete old debian template and go to Virtualizor, create new template from vps.
Done. It works.
Oh I discovered that problem @ColoCrossing too