Apply this guide to your situation
This answer covers “Plan and troubleshoot private networking between VPS instances”. Read it with the summary and confirm that the symptom and service match what you are experiencing. Available options can vary by plan and account setup.
- Before changing anything, note what you expected, what happened and roughly when. Check whether the issue affects one page or the whole service.
- Save the full error message and note recent changes. Hide passwords, access codes, personal data and keys before sharing screenshots or logs.
- If a step requires administrator access, restarting services or editing server files, stop if you do not administer that server. Send support the service name, error and checks you have already made.
Likely-cause and resolution matrix
Follow a branch only when evidence supports it. A symptom may have more than one cause; do not change layers by guesswork.
01Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
02Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
03Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
04Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
05Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
Prerequisites
- Authorised service access and confirmation of the exact product/plan.
- A recent backup or export before changing data, storage or DNS.
Important warnings
- Paths and features vary by provider and plan. This documentation does not claim cPanel, Plesk, Titan or these external modules are integrated into Anayil Panel.
- Do not share passwords, private keys, tokens or personal data in screenshots or tickets.
Step-by-step walkthrough
1. Identify the product and preserve its current state
2. Follow the procedure with minimal changes
3. Verify the result before closing
Troubleshooting & Solutions
A private IP exists, but the instances cannot communicate.
Root cause: Different networks, incorrect route/subnet, firewall or service bound to loopback.
Resolution: Compare routes and interfaces on both sides and ask the provider to confirm network membership. Do not open all ports or expose internal services.
Rollback and recovery plan
If verification fails, stop further changes, preserve logs and restore only a confirmed previous copy or value. For managed services, ask the provider to roll back the layer it owns.
Related runbooks in this category:
Was this technical guide helpful?
Facing a production outage?
Hosting Anayil system administrators can directly intervene on your server infrastructure.