* The root password the customer enters into the form on sign-up sets the VNC password.

(Quote)

The most common way customers got hacked when I used to run SolusVM was that they signed up with a trivial password initially with a plan to change it later.

As an example, within just the past few months alone we've seen significant security-related updates involving Linux kernels, cPanel, Plesk, and plenty of other commonly used software. Sometimes the v

So was basically a pishing to store user password...

If the user tried to login, they put their password on the malicious site. No DB was leaked.

(Quote)

(Quote)

Considering they use encryption based on your user password, they would have to blatantly lie about their setup in order to read mail. It's not client-side encryption (the key is kept in server memory

* In the Virtualizor master panel: reset all API keys, restrict API access by IP, remove any

Reset to last working config. You had backups, right?

(Quote)

(Quote)

(Quote)

One advise I would give to other provides is to cycle your DB passwords on each slave.

(Quote)

I did a hard reset, so things should be up.

* 22:33:56 – successful password SSH login as proxyuser from 193.32.127.248.

* RESET/LIMIT ALL API CREDENTIALS IN THE VIRT MASTER PANEL BY IP

AlmaLinux, Rocky Linux, Debian, Ubuntu LTS, Fedora, CentOS Stream, CloudLinux (+ cPanel / Plesk / DirectAdmin bundles), FreeBSD, OpenBSD — and 100+ application images.