Guides/Fix Remote Connection Issues

Fix Remote Connection Issues

Diagnose HTTPS, Application Password, REST API, capability, and version compatibility problems.
Updated 5 June 2026·Task guide

Outcome

The remote passes connection and compatibility checks, so export/import/push/pull workflows can authenticate safely.

Video walkthrough

Video walkthrough coming soon.

The YouTube embed will appear here.
Risk level

Low. Diagnostic guide. Rotate credentials if they were exposed during troubleshooting.

Before you start

  • Both sites must have WPChangeSync active.
  • The target should be reachable over HTTPS.
  • The remote user needs admin-capable permissions.
  • Application Password auth must be accepted by the target.

Steps

  1. Open the remote URL in a browser
    Confirm the domain, SSL certificate, and WordPress site are correct.
  2. Check /wp-json/
    Make sure host/security plugins do not block the REST API.
  3. Recreate the Application Password
    Use a fresh Application Password, not the normal login password.
  4. Test the remote in Config
    Use the built-in Test action before running workflows.
  5. Check versions
    The REST layer uses version compatibility headers to reject unsupported transfers.
  6. Watch rate limits
    Avoid repeated automated retries that trip rate limiting.

Screenshots

Check HTTPS
Check HTTPS
/wp-json/wpchangesync/v1/infon/wp-json/wpchangesync/v1/integrations
Legacy namespace exists for compatibility
The code still registers the legacy bricks-sync/v1 namespace, but new integrations should use wpchangesync/v1.

Verify and recover

After completing this guide, verify the result in Activity and on the target site. Keep the pre-change export or backup until the release has been accepted. If anything looks wrong, stop further syncs, restore the affected item or integration from backup, and re-run with a narrower scope or safer conflict strategy.