# Diagnostic Mode
# Hosting account not found
Problem: The hosting account has not been detected. It may have been removed.
Solutions for the administrator:
- Delete the service manually from PanelAlpha.
- You can also try to recreate the service manually. To do so, you will need the username associated with the missing hosting account. If you have a backup of the WordPress installation existing on that service, you may also restore it.
# How to restore a hosting service
- Find the username associated with the missing hosting account:
Manually create a service with the previously used username on the hosting server.
If WordPress instances were previously installed on the corrupted hosting service, you can restore them now using backups:
# Instance files not found
Problem: The WordPress installation files could not be detected.
Solution: Restore the WordPress installation from a backup.
# Manually Disabling Diagnostic Mode
Problem: You need to manually disable diagnostic mode for a specific instance. This is only necessary when Diagnostic Mode displays the message: "Diagnostic Mode has been enabled by admin."
You can also review active incidents and historical events in Admin Area → Logs → Diagnostic Mode (/logs/diagnostic-mode) using the Current Incidents and Logs tabs.
Solution: Use the following command on your PanelAlpha server:
docker compose -f /opt/panelalpha/app/docker-compose.yml exec api php artisan diagnostic-mode --app-id=INSTANCE_ID --disable
NOTE: Replace INSTANCE_ID with the actual ID of the instance you want to disable diagnostic mode for