Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
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.

New to Dedicated Server, Resources to manage the server

akrdevakrdev Member

I have managed vps in the past but recently I have got into Dedicated server. I don't find it as straightforward to manage it like vps. Any tips and resources on how to manage it effectively.

Comments

  • MikeAMikeA Member, Patron Provider

    What issues are you running into? The only different really would be lack of tools for higher up management like what virtualization offers. In that case you could just virtualize the dedicated server (or use a company that does it for you.)

  • MrRadicMrRadic Host Rep, Veteran

    It should be identical to managing a VPS.

  • Debian has auto manage feature

  • Rakane_SCRakane_SC Member, Host Rep

    When you move from VPS to dedicated, you're responsible for alot more.

    Hardware monitoring, rescue environments, reboots, aswell as security hardening,

    With that said, I would suggest installing basic monitoring tools like htop, iotop, netdata, and fail2ban for brute force attacks, then ufw or iptables-nft for firewall measures.

    If you want to run multiple services, run cockpit, or webmin to control your dashboard easier just make sure you lock down correctly.

    If your host provides IPMI, DCImanager, iDRAC, or remote KVM then I would learn that first just incase your systems lock up through ssh or you break networking in netplan or something.

    If you want to host VM's or containers I would suggest Proxmox or VMware depending on how much comfort you want.

    We work with alot of users transitioning from VPS to dedicated, so if you ever need more tips on hardening, disk layouts, or just setup, i'm happy to help!

    • Rakane, ServerCrate
    Thanked by 2anakara DediRock
  • Security: Use SSH keys, set up a firewall (UFW), and install Fail2Ban.

    Monitoring: Use htop, nmon, or Glances for resource checks.

    Backups: Automate with rsync, cloud backups, or snapshots.

    Performance: Tune web servers (Nginx/Apache) and DBs.

    Automation: Use Ansible or Puppet for configs.

    Docs: Keep a log of changes.

    https://www.digitalocean.com/community/tutorials
    https://www.linode.com/docs/

  • WLISWLIS Member, Host Rep

    For dedicated server management, it is recommended that you acquire a server with Lights-out management (LOM), also known as out-of-band management (OOB) capabilities. These technologies allow you to remotely manage your servers, independent of the host operating system, by enabling functions such as power cycling, firmware update, or remotely accessing your server for troubleshooting.

    You can also monitor the server's power usage, resources, or any errors by checking the event logs. You can also reinstall any Operating system remotely or even update the system firmware.

    The most well-known LOM brands are:
    Cisco: IMC
    Dell: DRAC
    HP: iLO

    Thanked by 1nghialele
  • jsgjsg Member, Resident Benchmarker
    edited July 2025

    @KaneHosting said:
    If your host provides IPMI, DCImanager, iDRAC, or remote KVM then I would learn that first just incase your systems lock up through ssh or you break networking in netplan or something.

    And if it does not, then you shouldn't buy it! Because IPMI/LOM basically is the major difference between a dedi and a virtual machine, anyway wrt. administration. All the rest like e.g. diverse software tools like htop, fail2ban, etc. are and work just the same as on a VDS/VPS.

    Secondly be sure that your provider (a) provides access to the IPMI/LOM, usually with an extra IP (can be internal or private range), and (b) cares about at least some basic protection, e.g. by limiting access to it to only a few source IPs or opening access via some panel or similar.
    Both, (a) and (b) are very important, do not buy a dedi without that! (And NO, "the IPMI/LOM requires a username and password" does not cut it!).

  • Rakane_SCRakane_SC Member, Host Rep

    @jsg said:

    @KaneHosting said:
    If your host provides IPMI, DCImanager, iDRAC, or remote KVM then I would learn that first just incase your systems lock up through ssh or you break networking in netplan or something.

    And if it does not, then you shouldn't buy it! Because IPMI/LOM basically is the major difference between a dedi and a virtual machine, anyway wrt. administration. All the rest like e.g. diverse software tools like htop, fail2ban, etc. are and work just the same as on a VDS/VPS.

    Secondly be sure that your provider (a) provides access to the IPMI/LOM, usually with an extra IP (can be internal or private range), and (b) cares about at least some basic protection, e.g. by limiting access to it to only a few source IPs or opening access via some panel or similar.
    Both, (a) and (b) are very important, do not buy a dedi without that! (And NO, "the IPMI/LOM requires a username and password" does not cut it!).

    Very said and true! IPMI/iDRAC/iLO is non-negotiable if you're serious about dedi ops, full recovery access is the line between running infrastructure or just praying to god it works lmao. We lock ours behind ACLs + Panel triggered tunnel access (so not exposed 24/7) to keep the attack surface tuned down, even with Path mitigation (it still happens). Shared or static access is literally begging for trouble. Too many hosts skip that, and still wonder why clients bounce after the first downtime!

    Thanked by 1jsg
  • DediRockDediRock Member, Patron Provider

    @KaneHosting said:
    When you move from VPS to dedicated, you're responsible for alot more.

    Hardware monitoring, rescue environments, reboots, aswell as security hardening,

    With that said, I would suggest installing basic monitoring tools like htop, iotop, netdata, and fail2ban for brute force attacks, then ufw or iptables-nft for firewall measures.

    If you want to run multiple services, run cockpit, or webmin to control your dashboard easier just make sure you lock down correctly.

    If your host provides IPMI, DCImanager, iDRAC, or remote KVM then I would learn that first just incase your systems lock up through ssh or you break networking in netplan or something.

    If you want to host VM's or containers I would suggest Proxmox or VMware depending on how much comfort you want.

    We work with alot of users transitioning from VPS to dedicated, so if you ever need more tips on hardening, disk layouts, or just setup, i'm happy to help!

    • Rakane, ServerCrate

    yup def a lot more to manage!

  • akrdevakrdev Member
    edited July 2025

    @MikeA said:
    What issues are you running into? The only different really would be lack of tools for higher up management like what virtualization offers. In that case you could just virtualize the dedicated server (or use a company that does it for you.)

    @WLIS said:
    For dedicated server management, it is recommended that you acquire a server with Lights-out management (LOM), also known as out-of-band management (OOB) capabilities. These technologies allow you to remotely manage your servers, independent of the host operating system, by enabling functions such as power cycling, firmware update, or remotely accessing your server for troubleshooting.

    You can also monitor the server's power usage, resources, or any errors by checking the event logs. You can also reinstall any Operating system remotely or even update the system firmware.

    The most well-known LOM brands are:
    Cisco: IMC
    Dell: DRAC
    HP: iLO

    So, they have provided access through open vpn . I installed open vpn and then connected the server through it. But, Now when I try to open the IPMI login through any web browser, it doesn't open. Also, starting an Open vpn has started messing with my wifi router. The internet goes slow after that and I have to restart it.

  • you may also need to tune the kernel for your usecase

Sign In or Register to comment.