• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Correct Set-Up To Avoid DNS Suspension

P

pkonstan

Guest
I have a dedicated host running Plesk. I followed all of the basic instructions for set up as provided by my host as well as the most basic Plesk instructions that I found.

This week my host unexpectedly disabled my host because of "abuse." I installed nothing extra, did the basic configuration and yet I wasn't protected from this type of attack.

In talking with tech support at my host, they gave me some initial comments about needing to have a firewall installed and something about making sure my local.host is not local.host but instead is my domain.

My question is, "What did I miss?" Where are these type of "basic" yet crucial instructions. For something as serious as having ones server shut down unexpectedly, one would think that basic instructions to secure your server would be very obvious and out front. Did I miss something in my rush to get the server set up, or is there some unwritten, hidden understanding out there? How could I miss something that is causing me such headaches.

Is there a "Plesk for Dummies" type of manual or a "white papers" of crucial things not to miss in set up? Once my host gives me my site back I want to make sure I fix the problem as best I can.

In summary, what are the "must do's" in order to correctly set-up a Plesk server to avoid getting hacked.
 
This is a good place to start I think:

http://www.web-hosting-control-pane....php/HOW-TO_setup_a_PLESK_Dedicated_Server/6/

Add a subscription to ASL which gives you a gresec patched kernel, easy install of mod_security and other useful things and you are quite secure. (incidentally the securing of the /tmp directly is not necessary if you have the grsec kernel running)

But who the hell is your host? "abuse" could mean anything. They are not being helpful. Do they mean someone was sending spam, or had gained access to the system or what? You can't protect against something you don't know about. Basically if you have a customer deliberately doing something stupid there is little you can do about it.

Faris.
 
Back
Top