How to Open a Support Ticket
A complete ticket gets resolved much faster. This guide tells you what to include for every type of problem.
02
Always Necessary Information
Whatever the problem, always include:
- Server ID (visible in client panel or VirtFusion)
- Server IP
- Operating system (Ubuntu 22.04, Windows Server 2022, etc.)
- Since when problem occurs (approximate date and time)
- What you tried to fix it
03
For Connectivity / Server Unreachable Issues
- Server IP
- Result of: ping <IP>
- Result of: traceroute <IP> (Linux/Mac) or tracert <IP> (Windows)
- Last successful access (when?)
- Status in VirtFusion (Online/Offline?)
- Did you modify firewall or iptables recently?
04
For Performance Issues (High CPU/RAM)
Quick commands to paste in ticket:
bash
echo "=== CPU/RAM ===" && top -bn1 | head -20
echo "=== MEMORY ===" && free -h
echo "=== DISK ===" && df -h
echo "=== UPTIME ===" && uptime
- Output of: top -bn1 | head -20
- Output of: free -h
- Output of: df -h
- Output of: vmstat 1 5
- Any suspicious process if visible
- Since when is machine slow?
05
For SSH Issues (Access Denied, Timeout)
- Exact error message (copy text, not screenshot)
- SSH port in use (22 or custom)
- Auth type (password or key)
- Output from client: ssh -vvv user@IP 2>&1 | tail -30
- Did you modify /etc/ssh/sshd_config recently?
- Fail2ban active? (sudo fail2ban-client status sshd)
06
For Website / Service Issues
sudo tail -50 /var/log/nginx/error.log
sudo tail -50 /var/log/apache2/error.log
- Domain and complete URL
- HTTP error code (404, 500, 502, 503...)
- Output of: sudo nginx -t (or apache2ctl configtest)
- Last error log lines:
- Problem on all sites or just one?
07
For Windows Issues (RDP, System Errors)
(Start > eventvwr.msc > Windows Logs)
- Windows Server version (2019/2022/2025)
- Exact error message (screenshot or text)
- Event Viewer > Windows Logs > Application/System: recent errors
- RDP port in use (3389 or custom)
- Last successful RDP access
08
For DDoS Attack In Progress
Guide: DDoS: Analysis and Dump to capture dump.
- Server IP under attack
- Since when (exact time)
- Traffic type if known (UDP flood, SYN flood, HTTP...)
- Output of: ss -s
- Top attacking IPs (see DDoS dump guide)
- .pcap file if available (even 30-60 seconds)
09
For Billing / Account Issues
- Account email
- Order number or service ID
- Screenshot of error in client panel
10
What NOT to Do
- Don't open multiple tickets for same problem: slows down queue
- Don't write just "doesn't work" without details
- Don't attach only terminal screenshots: copy text (it's searchable)
- Don't wait days before opening ticket: report sooner, fix sooner
11
Priority and Response Times
Tickets are handled by priority:
| Type | Priority |
|---|---|
| Server completely unreachable | Urgent |
| Services partially degraded | High |
| Configuration issues | Normal |
| Questions / info requests | Normal |
For urgent problems, clearly indicate in ticket subject: [URGENT] Server Unreachable.
Articoli correlati
Getting Started
Change Root Password
How to change your server's root password and how to recover it if forgotten
2 min di lettura
Getting Started
First Server Access
What to do immediately after activating your VPS or VDS
2 min di lettura
Getting Started
SSH Keys
How to generate and configure SSH keys for secure password-less access
2 min di lettura
