Technical support handled by the engineers who built the platform. No outsourced call centers, no chatbot mazes, no 72-hour email queues.
Different issues, different inboxes. Routing your message correctly gets you a faster answer.
Server issues, connectivity problems, OS reinstalls, control panel bugs, SSH/RDP access trouble. The stuff that keeps your VPS running.
support@freevps.it.comSpam originating from our IPs, DDoS attacks, phishing pages, malware, or any violation of our Acceptable Use Policy. We take every report seriously.
abuse@freevps.it.comPayment issues, invoice questions, plan upgrades/downgrades, refund requests, or account access recovery.
billing@freevps.it.comDMCA takedown notices, counter-notices, law enforcement requests, subpoenas, or legal inquiries.
legal@freevps.it.comGDPR/CCPA data access, rectification, deletion requests, or questions about our Privacy Policy.
privacy@freevps.it.comReseller inquiries, affiliate programs, media coverage, sponsorship, or integration partnerships.
partners@freevps.it.comUse this form and we'll route your message to the correct team. Include as much detail as possible — server ID, error messages, timestamps — so we can skip the back-and-forth.
Manage your VPS, view tickets, check status
Real-time infrastructure health & incidents
Common questions answered instantly
Uptime commitments & credit claims
Existing customers: For the fastest response, open a ticket directly from your control panel instead of using this form. Panel tickets are automatically linked to your account and server details.
Deploy your free VPS in the region closest to your users. All locations run the same hardware and software stack.
Equinix NY5, Secaucus NJ
Tier III+CoreSite LA2, Downtown
Tier IIIInterxion FRA, Sossenheim
Tier III+Equinix AM7, Science Park
Tier IVEquinix SG3, Loyang
Tier III+Most issues fall into a handful of categories. Check here first — you might have your answer in 30 seconds.
Most common cause: Firewall rules blocking port 22. If you recently ran ufw enable without allowing SSH first, you locked yourself out. Use the VNC/console access in the control panel to regain access and fix your firewall rules. If the server is unresponsive in VNC too, check if you're out of disk space (df -h) or if a kernel panic occurred — a reinstall via the panel may be needed.
Run top or htop to identify the process consuming resources. Common culprits: runaway PHP processes, unoptimized database queries, or a compromised server running a cryptominer. If you see a process you didn't install (especially xmrig, kdevtmpfsi, or random-named binaries in /tmp), your server may be compromised — reinstall immediately and secure SSH with key-based auth.
Log into the control panel → select your VPS → click "Reset Root Password." The new password will be displayed once. For Windows RDP, use the same panel function — it resets the Administrator password. If you've lost access to the control panel itself, email support@freevps.it.com from your registered email for account recovery.
Yes. Go to the control panel → select your VPS → "Reinstall OS." Choose any supported image. Warning: reinstalling wipes all data on the current disk. Back up everything you need via SCP/SFTP before clicking reinstall. The process takes 2-5 minutes.
Check your email for a notification explaining the reason. Common causes: AUP violation (mining, spam, attacks), unpaid invoice (paid plans), or a compromised server detected sending malicious traffic. Reply to the suspension email with your remediation plan and we'll review. For AUP violations, refer to our Acceptable Use Policy for severity levels and appeal eligibility.
No. We're a small engineering team, not a call center. Email and ticket-based support lets us research your issue properly, share screenshots and logs, and maintain a written record of the resolution. This consistently produces better outcomes than phone calls where details get lost. For urgent issues, mark your ticket as "Critical" and we'll prioritize it.
The more detail, the faster we resolve it. Include: (1) Your VPS ID or IP address, (2) What you expected to happen, (3) What actually happened, (4) When it started, (5) Any error messages (exact text, not paraphrased), (6) Steps you already tried. A good ticket gets resolved in one reply. A vague "my server doesn't work" ticket takes three rounds of back-and-forth.