PushRPMPushRPM

Support and recovery

PushRPM Plugin Connection Troubleshooting

Troubleshoot PushRPM plugin connection issues, site mismatch, expired authorization, payment access, HTTPS, and diagnostics.

Main intent

Help customers recover from connection failures without exposing secrets or guessing at settings.

Short answer

Most connection issues come from domain mismatch, expired links, missing payment access, HTTPS problems, or manual credential mistakes.

Check the domain first

Confirm the WordPress domain shown in the plugin matches the site selected or purchased in PushRPM. Watch for staging domains, www/non-www differences, and HTTP/HTTPS mismatch.

Use the guided connection path

Click Connect with PushRPM from wp-admin, log in if needed, and authorize the visible site. Manual setup should be a recovery path, not the default path.

Send diagnostics without secrets

The plugin support bundle should include version, site URL, mode, last sync, and safe errors. It should not expose API secrets in support messages.

Implementation checklist

  • Confirm public HTTPS works.
  • Check domain shown in the plugin.
  • Retry Connect with PushRPM.
  • Verify product access in billing.
  • Copy diagnostics before contacting support.

Common mistakes

  • Pasting old manual credentials.
  • Authorizing a staging site by mistake.
  • Sharing secret keys in screenshots.

Example

If the product is locked to example.com but the plugin runs on staging.example.com, the connection may correctly show a mismatch instead of enabling paid features.

Use a related tool

FAQ

What if Google OAuth is blocked?

During beta, some Google integrations may require verification or test-user access. PushRPM should show a friendly explanation instead of raw failure text.

Should I uninstall and reinstall?

Usually no. Try reconnecting and checking diagnostics first.

Related docs