Apply this guide to your situation
This answer covers “Remote Management and Migration of WordPress Cloud Manager”. 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
- Multiple Anayil Panel server instances running WordPress
- Generated Anayil Panel API token for fleet synchronization
Important warnings
- Ensure ports 8090 and 443 are reachable between instances to permit API heartbeat traffic.
- Secure fleet API credentials in encrypted secret managers.
Step-by-step walkthrough
1. Connect Anayil Panel instance
2. Multi-node fleet monitoring
3. Fleet migration and data synchronization
curl -k -X POST https://your-server:8090/api/getWordPressSites -H 'Content-Type: application/json' -d '{"adminUser":"admin","adminPass":"secret"}'{"status": 1, "sites": [...]}Troubleshooting & Solutions
Failed to connect to remote agent
Root cause: Perimeter firewall or network security groups blocking inbound port 8090 traffic.
Resolution: Verify port 8090/tcp is authorized in firewalld: firewall-cmd --list-ports.
Site synchronization out of sync
Root cause: Direct filesystem changes not captured by the telemetry agent.
Resolution: Click Force Resync in the manager to rebuild the local inventory cache.
Rollback and recovery plan
Disconnect the instance anytime by revoking the API key to operate in standalone local mode.
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.