Technical Issues
Technical Issues
Question: Why can't I connect to my server using SSH?
Answer: The server's password might not have been set yet. Please wait a few minutes and try again. If the issue
persists, try using Doprax’s terminal, which utilizes a private key for authentication.
Question: What should I do if my application fails to deploy?
Answer: Ensure the deployment environment is configured correctly. Check for error logs in the deployment tab for
further debugging. Ensure all dependencies are listed in your requirements.txt or Dockerfile.
Question: How can I debug server errors?
Answer: Use the monitoring tools provided in the dashboard or SSH into the server to check logs in /var/log.
Question: I can't SSH to my server. It looks like SSH protocol is blocked on my ISP. However, I can ping the server.
Answer: Please try using our terminal, which utilizes a private key for authentication. You can access it directly from
your VM dashboard.
Question: I'm getting an error saying port 25 is closed. Have you blocked it?
Answer: Yes, port 25 is closed by default as it can be used for spam.
Question: When I tunnel on a Hetzner server, it doesn't work, but it works on OVH. Are there any port limitations on Hetzner?
Answer: By default, there is a firewall enabled on Hetzner machines. If needed, we can remove the firewall. Send us your
server's IP for assistance.
Question: How do I resolve frequent disconnections from my server?
Answer: Frequent disconnections could be due to network instability or firewall settings. Check your local network
first, and ensure that the server's firewall allows persistent SSH connections.
Question: What should I do if my server is inaccessible after a reboot?
Answer: Check if the server's IP address or firewall rules have changed after the reboot. Ensure that the SSH service is
running, and try reconnecting.
Question: My server is running, but my application isn’t accessible. What could be wrong?
**Answer:**Ensure your application is listening on the correct port and that the port is open in the firewall. Check
your application logs for errors.
Question: I need to use email services, but ports 465 and 587 are blocked. Can I open them?
Answer: Yes, but you need to request Doprax support to disable the firewall for your server.
Question: I disabled the firewall, but after rebuilding my server, it was enabled again. Why?
Answer: Firewall settings reset after a rebuild. If this happens, you need to contact support again to have it removed.
Question: Can you permanently disable the firewall for my account?
Answer: Yes, but it’s not recommended since your account may be flagged for abuse. Instead, disable the firewall only
for specific servers when needed.
Question: I need to send emails from my VPS, but SMTP ports (465, 587) are blocked. What should I do?
Answer: SMTP ports are often blocked by default to prevent spam. You can:
1. Ask support to disable the firewall for your server.
2. Use a third-party SMTP relay service like SendGrid, Mailgun, or AWS SES.
3. Try port 2525, which some providers allow as an alternative.
Question: Why does my VPS randomly reboot without my input?
Answer: Possible reasons include:
1. High resource usage – Check CPU & RAM usage.
2. Datacenter issues – Some providers perform automatic reboots for system updates.
3. Misconfigured cron jobs – Run crontab -l to check for unexpected reboot commands.
What should be done if a virtual machine (VM) remains stuck in the "Deploying" status for an extended period?
If a VM is stuck in the Deploying process for too long, it is recommended to delete it and create a new one. If the
issue persists, refresh the page or check the VM panel to update the status. If the problem continues, contact support
for further investigation.
Why does SSH access fail after a server reboot?
If SSH access is lost after rebooting, try the following steps:
- Check the VM panel to ensure the server is actually online.
- Refresh the page or manually power cycle the VM from the panel.
- If SSH still does not work, use the web terminal to check if the system is booting properly.
- If the web terminal only shows a black screen, it may indicate a deeper issue, and support should be contacted.
Why is a server not responding to pings or SSH even though it appears online in the panel?
If a server does not respond to ping or SSH, but the panel shows it as online, it may be due to:
- A firewall rule blocking connections (especially on Hetzner servers).
- Network issues causing the server to be unreachable.
- A misconfigured SSH service that needs to be restarted.
- If the issue persists after checking these, restarting the VM or contacting support is recommended.
Why does a server's domain sometimes not appear after creation?
Occasionally, a newly created server does not automatically receive a domain. If this happens:
- Wait a few minutes and refresh the page.
- If the domain still does not appear, try rebooting the server from the VM panel.
- If the issue continues, submit a domain request through the panel.
How can port 587 be opened for sending emails?
By default, ports 465 and 587 are blocked for security reasons. However, it is possible to disable the firewall on a
specific server upon request. If email sending is required, request firewall removal via support.
What can cause a server to be active in the panel but inaccessible?
If a server appears active in the panel but cannot be accessed:
- Click on the server to update its status.
- Check if it is actually responding to ping requests.
- Verify whether any recent changes (such as firewall updates or reboots) caused the issue.
- If necessary, try restoring the server using a snapshot.
Q: I have a server with 4 vCPU, 8GB RAM, 80GB disk, and 20TB traffic. Can I extend the RAM and storage?
A: This depends on the provider. Some allow live upgrades, while others require a migration to a new plan. Check your
cloud provider’s documentation.
Q: How can I properly configure an IPv6 GRE tunnel between two remote servers?
A: Ensure both servers support IPv6 and enable net.ipv6.conf.all.forwarding=1. Configure GRE tunnel using:
ip tunnel add gre1 mode gre remote <remote_IP> local <local_IP> ttl 255
Then, assign an IP and bring up the interface:
ip addr add dev gre1
ip link set gre1 up
Q: My iptables rules are not properly redirecting traffic after setting up tunneling. How can I fix this?
A: Verify NAT and FORWARD chain rules. Use iptables -t nat -L -v to inspect existing rules and adjust forwarding
policies.
Q: What is Rescue Mode in Doprax?
Rescue Mode is a recovery environment that allows you to boot your VPS into a temporary operating system (usually Linux)
when the main system fails to start or becomes inaccessible. It helps users recover data, fix configuration errors, or
reset critical settings such as SSH access.
Q: When should I use Rescue Mode?
Use Rescue Mode if:
- Your VPS is not booting properly after an update or configuration change.
- You lost SSH access due to a misconfigured firewall or port change.
- You need to recover files or repair the filesystem.
- The network configuration is broken and you can’t access the server remotely.
Q: What happens when I enable Rescue Mode?
When Rescue Mode is activated:
- Your main disk is mounted as a secondary drive.
- The server boots into a temporary recovery system.
- You can connect using SSH or the Doprax terminal to repair, copy, or back up your data.
- All active services (like web servers, VPNs, etc.) are temporarily stopped until you exit Rescue Mode.
Q: Does Rescue Mode delete or change my data?
No. Enabling Rescue Mode does not delete or modify your existing data.
Your disk remains intact and can be accessed safely from the recovery environment.
However, you should avoid formatting or overwriting system partitions unless you know exactly what you’re doing.
Q: How do I enable Rescue Mode in Doprax?
You can enable it directly from your VM dashboard:
1. Go to your Virtual Machine page.
2. Click on “Rescue Mode” under the “Actions” menu.
3. Confirm the action — your VM will reboot into the rescue environment.
4. Use the provided SSH or terminal credentials to access it.
Q: How do I exit Rescue Mode?
Once you’ve repaired your system:
1. Return to the VM dashboard.
2. Click “Exit Rescue Mode” or “Reboot to Normal Mode.”
3. The server will restart using your main disk and normal configuration.
Q: Does Rescue Mode have an extra cost?
No, Rescue Mode is free for all users.
It’s included in your existing VM plan and does not generate additional hourly charges.
Q: Can I use Rescue Mode to reset my root password or SSH key?
Yes. You can mount your main disk and edit files such as /etc/shadow (for root password) or /root/.ssh/authorized_keys
to restore SSH access.
Be cautious and only modify what’s necessary.
Q: Is network access available in Rescue Mode?
Yes, basic network connectivity (including SSH) is available so you can transfer or back up files to another system.
However, running services (like Nginx, Docker, or VPN) won’t start automatically.
Q: Does enabling Rescue Mode affect my billing?
No — your billing remains hourly and continuous. Even while in Rescue Mode, the server remains active.
To stop billing, you must delete the server entirely.
