{"slug":"vps-managing","title":"Managing VPS Instances","description":"Complete guide to managing, monitoring, and maintaining your VPS instances.","section":"Features","url":"https://docs.danubedata.ro/vps-managing","markdown_url":"https://docs.danubedata.ro/vps-managing.md","breadcrumbs":[{"title":"Features","slug":null},{"title":"VPS Instances","slug":"vps-overview"},{"title":"Managing VPS","slug":"vps-managing"}],"headings":[{"level":1,"title":"Managing VPS Instances","id":"managing-vps-instances"},{"level":2,"title":"Overview","id":"overview"},{"level":2,"title":"Instance Dashboard","id":"instance-dashboard"},{"level":3,"title":"Dashboard Sections","id":"dashboard-sections"},{"level":2,"title":"Instance Operations","id":"instance-operations"},{"level":3,"title":"Start Instance","id":"start-instance"},{"level":3,"title":"Stop Instance","id":"stop-instance"},{"level":3,"title":"Force Stop (Stuck Instances)","id":"force-stop-stuck-instances"},{"level":3,"title":"Reboot Instance","id":"reboot-instance"},{"level":3,"title":"Reinstall OS","id":"reinstall-os"},{"level":3,"title":"Redeploy","id":"redeploy"},{"level":3,"title":"Delete Instance","id":"delete-instance"},{"level":2,"title":"Editing Instance Configuration","id":"editing-instance-configuration"},{"level":3,"title":"Change Instance Name","id":"change-instance-name"},{"level":3,"title":"Resize (Profile, CPU, RAM, Disk)","id":"resize-profile-cpu-ram-disk"},{"level":3,"title":"Attach/Detach Firewalls","id":"attachdetach-firewalls"},{"level":3,"title":"Add/Remove SSH Keys","id":"addremove-ssh-keys"},{"level":2,"title":"Resource Monitoring","id":"resource-monitoring"},{"level":3,"title":"CPU Usage","id":"cpu-usage"},{"level":3,"title":"Memory Usage","id":"memory-usage"},{"level":3,"title":"Disk Usage","id":"disk-usage"},{"level":3,"title":"Network Traffic","id":"network-traffic"},{"level":2,"title":"Software Management","id":"software-management"},{"level":3,"title":"Update System","id":"update-system"},{"level":3,"title":"Install Software","id":"install-software"},{"level":3,"title":"Service Management","id":"service-management"},{"level":2,"title":"User Management","id":"user-management"},{"level":3,"title":"Create Users","id":"create-users"},{"level":3,"title":"SSH Key Management","id":"ssh-key-management"},{"level":2,"title":"Security Hardening","id":"security-hardening"},{"level":3,"title":"Configure Firewall","id":"configure-firewall"},{"level":3,"title":"Install Fail2Ban","id":"install-fail2ban"},{"level":3,"title":"Secure SSH","id":"secure-ssh"},{"level":3,"title":"Adjust SSH Session Timeout","id":"adjust-ssh-session-timeout"},{"level":3,"title":"Enable Automatic Security Updates","id":"enable-automatic-security-updates"},{"level":2,"title":"Backup & Recovery","id":"backup-recovery"},{"level":3,"title":"Create Snapshots","id":"create-snapshots"},{"level":3,"title":"Manual Backups","id":"manual-backups"},{"level":2,"title":"Performance Optimization","id":"performance-optimization"},{"level":3,"title":"Optimize Web Server","id":"optimize-web-server"},{"level":3,"title":"Enable Caching","id":"enable-caching"},{"level":3,"title":"Database Optimization","id":"database-optimization"},{"level":2,"title":"Troubleshooting","id":"troubleshooting"},{"level":3,"title":"Cannot SSH","id":"cannot-ssh"},{"level":3,"title":"High Load","id":"high-load"},{"level":3,"title":"Out of Disk Space","id":"out-of-disk-space"},{"level":3,"title":"Service Won't Start","id":"service-wont-start"},{"level":2,"title":"Best Practices","id":"best-practices"},{"level":3,"title":"Regular Maintenance","id":"regular-maintenance"},{"level":3,"title":"Monitoring","id":"monitoring"},{"level":3,"title":"Documentation","id":"documentation"},{"level":2,"title":"Next Steps","id":"next-steps"}],"format":"markdown","word_count":2213,"content":"# Managing VPS Instances\n\nComplete guide to managing, monitoring, and maintaining your VPS instances.\n\n## Overview\n\nOnce your VPS is created, you can manage it through the dashboard or SSH. This guide covers all management operations.\n\n## Instance Dashboard\n\nAccess your VPS dashboard:\n\n1. Go to **Pods** in the main menu\n2. Click on your instance name\n3. View the instance dashboard\n\n### Dashboard Sections\n\n**Overview Tab**:\n- Instance status\n- Resource usage charts\n- Connection information\n- Quick actions (Start, Stop, Reboot)\n\n**Metrics Tab**:\n- Real-time performance graphs\n- CPU usage\n- Memory utilization\n- Disk I/O\n- Network traffic\n\n**Snapshots Tab**:\n- Create and manage snapshots\n- Restore from snapshots\n- Delete old snapshots\n\n**Console Tab**:\n- Full **graphical VNC console** in the browser — no SSH required\n- Emergency access when SSH is unavailable (boot issues, firewall lockout, etc.)\n\n## Instance Operations\n\n### Start Instance\n\nStart a stopped instance:\n\n1. Go to your instance dashboard\n2. Click **Start** button\n3. Instance boots in 30-60 seconds\n\n**Cost Note**: Instances are billed whether running or stopped. Starting simply resumes compute activity.\n\n### Stop Instance\n\nShut down your instance:\n\n1. Go to your instance dashboard\n2. Click **Stop** button\n3. Confirm the action\n4. Instance shuts down in 30-60 seconds\n\n**Important**:\n- All data is preserved\n- Still billed at the full rate (delete to stop billing)\n- Can start anytime\n- Network connections are lost\n\n**Graceful Shutdown**:\n```bash\n# Prefer SSH shutdown for clean stop\nssh root@your-ip\nsudo shutdown -h now\n```\n\n### Force Stop (Stuck Instances)\n\nIf an instance gets stuck in a transitional state (starting, stopping, rebooting), use **Force Stop** to force-kill it and return it to a stopped state.\n\n1. Open the actions menu on the instance\n2. Click **Force stop**\n3. Confirm in the dialog\n\nForce Stop is only offered when the platform detects that an instance is stuck.\n\n### Reboot Instance\n\nRestart your instance:\n\n1. Go to your instance dashboard\n2. Click **Reboot** button\n3. Confirm the action\n4. Instance reboots in 1-2 minutes\n\n**Use Cases**:\n- After kernel updates\n- To apply system changes\n- Troubleshooting issues\n- After configuration changes\n\n**SSH Reboot**:\n```bash\nsudo reboot\n```\n\n### Reinstall OS\n\nReinstall the operating system on the **same** instance — handy for starting fresh without changing the IP address.\n\n1. Open the actions menu and choose **Reinstall OS**\n2. Pick the OS image and confirm\n3. Your custom cloud-init script (if any) runs again on first boot\n\n**Warning**: Reinstalling **erases all data on the disk**. Take a snapshot first if you need to keep anything.\n\n### Redeploy\n\nIf an instance is stuck in an **error** or **pending** state, **Redeploy** re-runs its deployment (with detailed logs) — often the quickest way to recover without recreating the instance.\n\n### Delete Instance\n\n**Warning**: This permanently deletes your instance and all data!\n\n**Before Deleting**:\n1. ✅ Backup important data\n2. ✅ Create snapshot if needed\n3. ✅ Update DNS records\n4. ✅ Notify team members\n5. ✅ Document configuration\n\n**Delete Steps**:\n1. Go to your instance dashboard\n2. Click **Delete** button\n3. Type instance name to confirm\n4. Click **Confirm Delete**\n5. Instance deleted in 1-2 minutes\n\n**Cannot be undone!**\n\n## Editing Instance Configuration\n\n### Change Instance Name\n\n1. Go to instance dashboard\n2. Click **Edit** button\n3. Update name\n4. Click **Save**\n\n### Resize (Profile, CPU, RAM, Disk)\n\nFrom the instance **Edit** page you can move to a different resource profile, or fine-tune CPU, memory, and disk directly. A live price estimate updates as you change values.\n\n- **Disk can be grown but not shrunk** — profiles whose maximum disk is smaller than your current disk are disabled\n- Resizing briefly powers the instance off while resources are applied, then powers it back on\n- Billing adjusts from the hour the resize takes effect\n\nSee [Resource Profiles → Resizing](https://docs.danubedata.ro/vps-profiles#resizing).\n\n### Attach/Detach Firewalls\n\n**Attach Firewall**:\n1. Go to instance dashboard\n2. Click **Edit** button\n3. Select firewall from dropdown\n4. Click **Save**\n5. Rules apply immediately\n\n**Detach Firewall**:\n1. Click **Edit** button\n2. Remove firewall selection\n3. Click **Save**\n4. All traffic allowed (not recommended!)\n\n### Add/Remove SSH Keys\n\n**Add Key**:\n1. Go to instance dashboard\n2. Click **SSH Keys** section\n3. Click **Add Key**\n4. Select existing key or add new\n5. Key added to `~/.ssh/authorized_keys`\n\n**Remove Key**:\n1. Go to **SSH Keys** section\n2. Click **Remove** next to key\n3. Key removed from server\n\n## Resource Monitoring\n\nEvery instance keeps **7 days of historical metrics**. You can set [metric alerts](https://docs.danubedata.ro/monitoring-alerting) on CPU, memory, and disk to be emailed when a threshold is breached — and the platform continuously health-monitors your instances, alerting your team if one crashes or runs out of memory. CPU and memory figures reported inside the VM reflect your instance's real limits, not the host's.\n\n### CPU Usage\n\nMonitor CPU utilization:\n\n**Dashboard**:\n- Real-time graph\n- Average over 1h, 6h, 24h\n- Peak usage highlighted\n\n**SSH Monitoring**:\n```bash\n# Real-time CPU usage\nhtop\n\n# CPU info\nlscpu\n\n# Load average\nuptime\n\n# Per-process CPU\ntop -o %CPU\n```\n\n**High CPU Troubleshooting**:\n1. Identify process: `top`\n2. Check logs: `journalctl -xe`\n3. Restart service if needed\n4. Consider upgrading profile\n\n### Memory Usage\n\nTrack RAM utilization:\n\n**Dashboard**:\n- Used vs. Available\n- Swap usage\n- Historical trends\n\n**SSH Monitoring**:\n```bash\n# Memory usage\nfree -h\n\n# Detailed memory info\ncat /proc/meminfo\n\n# Per-process memory\ntop -o %MEM\n\n# Find memory hogs\nps aux --sort=-%mem | head\n```\n\n**High Memory Solutions**:\n1. Identify memory leak\n2. Restart services\n3. Clear caches\n4. Upgrade to larger profile\n\n### Disk Usage\n\nMonitor storage utilization:\n\n**Dashboard**:\n- Used/Total storage\n- I/O operations per second\n- Read/write bandwidth\n\n**SSH Monitoring**:\n```bash\n# Disk space\ndf -h\n\n# Largest directories\ndu -h --max-depth=1 /\n\n# Find large files\nfind / -type f -size +100M -exec ls -lh {} \\;\n\n# I/O stats\niostat -x 1\n```\n\n**Low Disk Space Solutions**:\n```bash\n# Clean package cache\napt clean  # Ubuntu/Debian\ndnf clean all  # AlmaLinux/Rocky\n\n# Remove old logs\njournalctl --vacuum-time=7d\n\n# Find and remove old files\nfind /tmp -type f -atime +7 -delete\n\n# Docker cleanup (if applicable)\ndocker system prune -a\n```\n\n### Network Traffic\n\nMonitor bandwidth usage:\n\n**Dashboard**:\n- Inbound traffic\n- Outbound traffic\n- Peak bandwidth\n- Monthly total\n\nThe **traffic visualizer** breaks your VPS traffic down by connection/flow, and inbound connections are enriched with source-reputation data to help you spot suspicious sources. Only public egress counts toward your included traffic quota — traffic to your own resources over the private network is free.\n\n**SSH Monitoring**:\n```bash\n# Network interfaces\nifconfig\n\n# Live traffic\niftop\n\n# Bandwidth per process\nnethogs\n\n# Network statistics\nnetstat -i\n```\n\n## Software Management\n\n### Update System\n\nKeep your system updated:\n\n**Ubuntu/Debian**:\n```bash\n# Update package list\nsudo apt update\n\n# Upgrade packages\nsudo apt upgrade -y\n\n# Upgrade distribution\nsudo apt dist-upgrade -y\n\n# Remove old packages\nsudo apt autoremove -y\n```\n\n**AlmaLinux/Rocky/Fedora**:\n```bash\n# Update all packages\nsudo yum update -y\n\n# Or with dnf (Fedora)\nsudo dnf update -y\n\n# Clean old packages\nsudo yum autoremove -y\n```\n\n**Auto-Updates** (Ubuntu/Debian):\n```bash\n# Install unattended-upgrades\nsudo apt install unattended-upgrades -y\n\n# Enable auto-updates\nsudo dpkg-reconfigure -plow unattended-upgrades\n```\n\n### Install Software\n\n**Web Server**:\n```bash\n# Nginx\nsudo apt install nginx -y\nsudo systemctl enable nginx\nsudo systemctl start nginx\n\n# Apache\nsudo apt install apache2 -y\nsudo systemctl enable apache2\nsudo systemctl start apache2\n```\n\n**Database**:\n```bash\n# MySQL\nsudo apt install mysql-server -y\nsudo mysql_secure_installation\n\n# PostgreSQL\nsudo apt install postgresql postgresql-contrib -y\n\n# Redis\nsudo apt install redis-server -y\n```\n\n**Programming Languages**:\n```bash\n# Python 3\nsudo apt install python3 python3-pip -y\n\n# Node.js (via NodeSource)\ncurl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -\nsudo apt install nodejs -y\n\n# PHP\nsudo apt install php php-fpm php-mysql -y\n\n# Go\nsudo apt install golang -y\n\n# Ruby\nsudo apt install ruby-full -y\n```\n\n**Docker**:\n```bash\n# Install Docker\ncurl -fsSL https://get.docker.com -o get-docker.sh\nsudo sh get-docker.sh\n\n# Add user to docker group\nsudo usermod -aG docker $USER\n\n# Install Docker Compose\nsudo curl -L \"https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)\" -o /usr/local/bin/docker-compose\nsudo chmod +x /usr/local/bin/docker-compose\n```\n\n### Service Management\n\nControl system services:\n\n```bash\n# Start service\nsudo systemctl start nginx\n\n# Stop service\nsudo systemctl stop nginx\n\n# Restart service\nsudo systemctl restart nginx\n\n# Reload configuration\nsudo systemctl reload nginx\n\n# Enable on boot\nsudo systemctl enable nginx\n\n# Disable on boot\nsudo systemctl disable nginx\n\n# Check status\nsudo systemctl status nginx\n\n# View logs\nsudo journalctl -u nginx -f\n```\n\n## User Management\n\n### Create Users\n\nAdd non-root users:\n\n```bash\n# Create user\nsudo adduser johndoe\n\n# Add to sudo group (Ubuntu/Debian)\nsudo usermod -aG sudo johndoe\n\n# Add to wheel group (AlmaLinux/Rocky)\nsudo usermod -aG wheel johndoe\n\n# Set password\nsudo passwd johndoe\n```\n\n### SSH Key Management\n\n**Add SSH key for user**:\n```bash\n# Switch to user\nsudo su - johndoe\n\n# Create .ssh directory\nmkdir -p ~/.ssh\nchmod 700 ~/.ssh\n\n# Add public key\necho \"ssh-ed25519 AAAA...\" >> ~/.ssh/authorized_keys\nchmod 600 ~/.ssh/authorized_keys\n```\n\n**Disable password authentication**:\n```bash\n# Edit SSH config\nsudo nano /etc/ssh/sshd_config\n\n# Set these values:\nPasswordAuthentication no\nPubkeyAuthentication yes\n\n# Restart SSH\nsudo systemctl restart sshd\n```\n\n## Security Hardening\n\n### Configure Firewall\n\n**UFW (Ubuntu/Debian)**:\n```bash\n# Install UFW\nsudo apt install ufw -y\n\n# Default policies\nsudo ufw default deny incoming\nsudo ufw default allow outgoing\n\n# Allow SSH (important!)\nsudo ufw allow 22/tcp\n\n# Allow HTTP/HTTPS\nsudo ufw allow 80/tcp\nsudo ufw allow 443/tcp\n\n# Enable firewall\nsudo ufw enable\n\n# Check status\nsudo ufw status verbose\n```\n\n**Firewalld (AlmaLinux/Rocky)**:\n```bash\n# Start firewalld\nsudo systemctl start firewalld\nsudo systemctl enable firewalld\n\n# Allow services\nsudo firewall-cmd --permanent --add-service=ssh\nsudo firewall-cmd --permanent --add-service=http\nsudo firewall-cmd --permanent --add-service=https\n\n# Reload\nsudo firewall-cmd --reload\n\n# Check status\nsudo firewall-cmd --list-all\n```\n\n### Install Fail2Ban\n\nProtect against brute-force attacks:\n\n```bash\n# Install\nsudo apt install fail2ban -y\n\n# Create local config\nsudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local\n\n# Edit config\nsudo nano /etc/fail2ban/jail.local\n\n# Find [sshd] section and ensure:\nenabled = true\nmaxretry = 3\nbantime = 3600\n\n# Start fail2ban\nsudo systemctl enable fail2ban\nsudo systemctl start fail2ban\n\n# Check status\nsudo fail2ban-client status sshd\n```\n\n### Secure SSH\n\nBest practices for SSH:\n\n```bash\n# Edit SSH config\nsudo nano /etc/ssh/sshd_config\n\n# Recommended settings:\nPort 22                          # Or custom port\nPermitRootLogin no              # Disable root login\nPasswordAuthentication no        # Key-based only\nPubkeyAuthentication yes\nPermitEmptyPasswords no\nX11Forwarding no\nMaxAuthTries 3\nClientAliveInterval 300\nClientAliveCountMax 2\n\n# Restart SSH\nsudo systemctl restart sshd\n```\n\n### Adjust SSH Session Timeout\n\nBy default, SSH sessions timeout after 10 minutes of inactivity. You can increase this by editing the SSH configuration:\n\n```bash\n# Edit the production SSH config\nsudo nano /etc/ssh/sshd_config.d/99-production.conf\n\n# Find and modify these values:\nClientAliveInterval 300    # Seconds between keep-alive checks\nClientAliveCountMax 2      # Number of missed keep-alives before disconnect\n```\n\nThe total timeout = `ClientAliveInterval × ClientAliveCountMax` seconds.\n\n**Common timeout settings**:\n\n| Timeout | ClientAliveInterval | ClientAliveCountMax |\n|---------|---------------------|---------------------|\n| 10 min (default) | 300 | 2 |\n| 30 min | 900 | 2 |\n| 1 hour | 1800 | 2 |\n| 4 hours | 3600 | 4 |\n| 8 hours | 3600 | 8 |\n| Disabled | 0 | 0 |\n\nAfter editing, restart SSH:\n\n```bash\nsudo systemctl restart sshd\n```\n\n**Note**: Longer timeouts may pose a security risk if you leave sessions unattended. Consider your security requirements when adjusting this setting.\n\n### Enable Automatic Security Updates\n\n**Ubuntu/Debian**:\n```bash\nsudo apt install unattended-upgrades -y\nsudo dpkg-reconfigure -plow unattended-upgrades\n```\n\n**AlmaLinux/Rocky**:\n```bash\nsudo dnf install dnf-automatic -y\nsudo systemctl enable --now dnf-automatic.timer\n```\n\n## Backup & Recovery\n\n### Create Snapshots\n\nRegular snapshots protect your data:\n\n1. Go to instance dashboard\n2. Click **Snapshots** tab\n3. Click **Create Snapshot**\n4. Enter descriptive name\n5. Click **Create**\n\n**Snapshot Tips**:\n- Take before major changes\n- Weekly for production\n- Before system updates\n- Label with date and purpose\n\n### Manual Backups\n\nBackup specific data:\n\n**Database Backup**:\n```bash\n# MySQL\nmysqldump -u root -p database_name > backup.sql\n\n# PostgreSQL\npg_dump database_name > backup.sql\n```\n\n**File Backup**:\n```bash\n# Tar archive\ntar -czf backup.tar.gz /path/to/data/\n\n# Rsync to remote server\nrsync -avz /path/to/data/ user@remote:/backup/\n```\n\n**Automated Backups**:\n```bash\n# Create backup script\ncat > /root/backup.sh << 'EOF'\n#!/bin/bash\nDATE=$(date +%Y%m%d)\ntar -czf /backup/data-$DATE.tar.gz /var/www/\nfind /backup/ -name \"data-*.tar.gz\" -mtime +7 -delete\nEOF\n\nchmod +x /root/backup.sh\n\n# Add to crontab\ncrontab -e\n# Add: 0 2 * * * /root/backup.sh\n```\n\n## Performance Optimization\n\n### Optimize Web Server\n\n**Nginx**:\n```nginx\n# /etc/nginx/nginx.conf\nworker_processes auto;\nworker_connections 2048;\n\ngzip on;\ngzip_types text/plain text/css application/json application/javascript;\n\nclient_max_body_size 100M;\n```\n\n**PHP-FPM**:\n```ini\n# /etc/php/8.1/fpm/pool.d/www.conf\npm = dynamic\npm.max_children = 50\npm.start_servers = 5\npm.min_spare_servers = 5\npm.max_spare_servers = 35\n```\n\n### Enable Caching\n\n**Redis for sessions**:\n```bash\n# Install Redis\nsudo apt install redis-server -y\n\n# Configure PHP to use Redis\necho \"session.save_handler = redis\" >> /etc/php/8.1/fpm/php.ini\necho \"session.save_path = 'tcp://127.0.0.1:6379'\" >> /etc/php/8.1/fpm/php.ini\n```\n\n### Database Optimization\n\n**MySQL tuning**:\n```sql\n-- Check slow queries\nSHOW VARIABLES LIKE 'slow_query_log';\nSET GLOBAL slow_query_log = 'ON';\n\n-- Add indexes\nCREATE INDEX idx_user_email ON users(email);\n\n-- Analyze tables\nANALYZE TABLE users;\n```\n\n## Troubleshooting\n\n### Cannot SSH\n\n**Check instance status**:\n- Verify instance is running\n- Check SSH service: `sudo systemctl status sshd`\n- Check firewall allows port 22\n\n**Test connectivity**:\n```bash\n# Ping server\nping your-ip\n\n# Test SSH port\ntelnet your-ip 22\n\n# Verbose SSH\nssh -v root@your-ip\n```\n\n### High Load\n\n**Check processes**:\n```bash\n# CPU hogs\ntop -o %CPU\n\n# Memory hogs\ntop -o %MEM\n\n# Disk I/O\niotop\n```\n\n**Solutions**:\n- Kill rogue processes\n- Restart services\n- Upgrade instance profile\n- Optimize applications\n\n### Out of Disk Space\n\n**Find space hogs**:\n```bash\ndu -h --max-depth=1 / | sort -rh | head -20\n```\n\n**Clean up**:\n```bash\n# Old logs\nsudo journalctl --vacuum-time=7d\n\n# Package cache\nsudo apt clean\n\n# Docker cleanup\ndocker system prune -a\n\n# Old kernels (Ubuntu)\nsudo apt autoremove --purge\n```\n\n### Service Won't Start\n\n**Check logs**:\n```bash\nsudo journalctl -u service-name -n 50\n\n# Or\nsudo tail -f /var/log/nginx/error.log\n```\n\n**Common fixes**:\n```bash\n# Check configuration\nsudo nginx -t\n\n# Fix permissions\nsudo chown -R www-data:www-data /var/www/\n\n# Check ports\nsudo netstat -tlnp | grep :80\n```\n\n## Best Practices\n\n### Regular Maintenance\n\n**Weekly**:\n- [ ] Review resource usage\n- [ ] Check for updates\n- [ ] Review logs for errors\n- [ ] Verify backups\n\n**Monthly**:\n- [ ] Full system update\n- [ ] Create snapshot\n- [ ] Review security logs\n- [ ] Clean up old files\n- [ ] Review firewall rules\n\n### Monitoring\n\nSet up monitoring:\n- CPU/memory alerts\n- Disk space alerts\n- Service health checks\n- Uptime monitoring\n\n### Documentation\n\nKeep records of:\n- Configuration changes\n- Software installed\n- User accounts\n- Firewall rules\n- Backup schedules\n\n## Next Steps\n\n- [VPS Snapshots Guide](https://docs.danubedata.ro/vps-snapshots)\n- [SSH Access Guide](https://docs.danubedata.ro/vps-ssh)\n- [Firewall Configuration](https://docs.danubedata.ro/networking-firewalls)\n- [Monitoring Setup](https://docs.danubedata.ro/monitoring-overview)\n\nNeed help? Contact support through the dashboard.\n\n","prev":{"title":"Creating VPS","slug":"vps-creating","url":"https://docs.danubedata.ro/vps-creating","markdown_url":"https://docs.danubedata.ro/vps-creating.md","json_url":"https://docs.danubedata.ro/vps-creating.json"},"next":{"title":"Resource Profiles","slug":"vps-profiles","url":"https://docs.danubedata.ro/vps-profiles","markdown_url":"https://docs.danubedata.ro/vps-profiles.md","json_url":"https://docs.danubedata.ro/vps-profiles.json"},"index_url":"https://docs.danubedata.ro/index.json"}