Default port 22 closure on SolusVM nodes and need for a proper management panel

colonelserver

We’re planning to close some default ports (including port 22) on our nodes and VMs, but we need a precise and secure management panel that can handle opening and closing these ports per-IP.

SolusVM2 doesn’t provide this feature in a clean or fully automated way.

Has anyone built a similar workflow or implemented a reliable setup for this scenario? Any guidance or suggestions would be appreciated.

MikeA

Solution - Don't use Solus

colonelserver

@MikeA said:
Solution - Don't use Solus

advise for other platforms ?

loay

Why did you get suspended on LET?

colonelserver

@loay said:
Why did you get suspended on LET?

long conversation! short end msg :

"Because of the newness of your company and based on our review of the application, we need to pause the process for 60 days. After 60 days we will revisit your application.
Upon approving your application in the future we will reset your billing period for your Provider Tag payment so that you do not lose any "paid time." "

MikeA

@colonelserver said:

@MikeA said:
Solution - Don't use Solus

advise for other platforms ?

Yes, Virtfusion if you have the funds for it. Clients will be much happier too since they don't need to contact support for anything.

Mason

Speedrunning the provider tag requirements? Patience, my man... enjoy the ride.

colonelserver

@Mason said:
Speedrunning the provider tag requirements? Patience, my man... enjoy the ride.

little rush on it, but if the topics feel like spmy let me know

ahnlak

Yeah it does

ReadyDedis

@colonelserver said:

@MikeA said:
Solution - Don't use Solus

advise for other platforms ?

You can try our platform too https://hypervisor.io

AnthonySmith

VirtFusion can do this.

jcn50

You can ask @EthernetServers about this, he closed port 22 for a year or two, then (finally) reverted... For an end-user/customer perspective it was (very) burdensome.

Rackoona

why not use proxmox ?

somik

@Mason said:
Speedrunning the provider tag requirements? Patience, my man... enjoy the ride.

If he is paying for the servers and panels every month, 2 months of lost income is a huge loss. So it only makes sense to rush it, as the faster the money starts coming in, the faster he can make a profit and ensure the business is sustainable.

MannDude

@jcn50 said:
You can ask @EthernetServers about this, he closed port 22 for a year or two, then (finally) reverted... For an end-user/customer perspective it was (very) burdensome.

As long as the offset port is communicated, it shouldn't be a burden to the customer.

Just toss in the email template for the new server deployment:

"By default, we close port 22 for security reasons. You may connect to your new VPS using port XXXX instead. See below for guides." (or something)

It's something we've considered, but haven't felt the need to do yet. If customers are deploying new servers with 22 open, password based auth, and passwords like "admin123" then that's sort of their own fault.

kako1talk

look at Knocknoc

AnthonySmith

I have never used solusvm V2 I assumed that whole thing was on ghost ship mode since the only Dev that understood the product moved on about 3 years ago.

I just had a look and solusvm V2 has cloud init support so I don't understand the issue?