Skip to content
For AI agents and documentation tools, use llms.txt for the documentation index. Full public content is available at llms-full.txt. Markdown versions of pages are available by appending .md to canonical URLs when published; the homepage Markdown is available at /index.md.
Installation Troubleshooting

Troubleshooting

Common issues and quick fixes.

Google or Apple sign-in does not return to the app

Section titled “Google or Apple sign-in does not return to the app”
Start again from https://metermonitor.monetizationapps.com/login and allow the Google or Apple redirect to complete.
Use the same sign-in method and email you used when creating the account. A verified email can be linked across methods, but Apple private relay or a different provider email can open a separate workspace.
If you land back on the login page without a session, capture the timestamp, browser, provider, and any visible error before contacting support.

I see a different workspace after signing in

Section titled “I see a different workspace after signing in”
Check whether Google or Apple returned the same email address as your original account.
If Apple private relay was used, try the original sign-in method or the original email/password account.
If you see an account-already-exists message, continue with the original Google or Apple method, or reset access from the original sign-in method.
Contact support if both sign-in methods are yours and the workspace still looks wrong.

Checkout shows HTTP 502 or checkout_creation_failed

Section titled “Checkout shows HTTP 502 or checkout_creation_failed”
Retry once from Settings → Subscription & Billing.
If it repeats, capture the timestamp and contact support.
This is normal — billing updates can take a moment to arrive, so the page may not refresh the instant checkout completes.
Wait 30 to 60 seconds, then click Refresh Billing.

Restricted key save fails with mode mismatch

Section titled “Restricted key save fails with mode mismatch”

If you see a message like:

The selected mode does not match the key.
Selected mode is live, but key belongs to test mode.

Do this:

  1. Verify the selected mode in SettingsTest vs Live.
  2. Verify the key prefix:
    • Test uses rk_test_...
    • Live uses rk_live_...
  3. Generate or copy the key from the same Stripe dashboard mode.
Click Refresh Status.
Re-run Connect Stripe.
Confirm you used the intended mode — Test vs Live.
Retry from Settings → Subscription & Billing.
Click Refresh Billing to confirm the latest provider state.
If you still see an HTTP error, capture the timestamp and contact support.
Compare active customer count to the plan limit in Settings.
Upgrade plan if active count exceeds your current tier.

Use monetizationapps.com/contact and include:

Timestamp with timezone.
Account email and sign-in method used, such as email/password, Google, or Apple.
Stripe account ID if applicable.
Screenshot of the error.