Find the step that is failing.
A connection problem can happen before the request reaches WordPress, during authentication, or when a tool runs. Start with the symptom you can observe.
The client cannot reach the site
Check that the endpoint is reachable from where the client runs. A local URL may work in your browser but remain inaccessible to a cloud connector. Confirm HTTPS and the exact endpoint from Avius.
Hosting protection, a firewall, or a staging login can intercept a request before WordPress receives it. Review the relevant logs and allow the specific required route when appropriate. Do not disable site security broadly as a first fix.
The connection is active, but no tools appear
Check that Avius is active and that the relevant abilities are enabled. Refresh or reconnect the client after configuration changes. A cached tool list may not immediately reflect a change in WordPress.
Unexpected output from another plugin can interfere with a structured response. Use server logs to investigate without exposing debug output to public visitors.
A tool times out or stops halfway
Reduce the task to a smaller operation and inspect the site before retrying. A timeout does not prove that no change happened. Long-running work may need a supported background workflow.
Record which tool ran, the approximate time, the site environment, and the visible error. These details help separate a network failure from a server execution limit.
What to include in a support request
Provide the Avius, WordPress, and PHP versions; the client name; the authentication method; the failing step; and the exact error with secrets removed.
Never send a license key, Application Password, private content, or a complete database export in an ordinary support message.
Contact support