Features Use Cases Pricing
Blog Documentation Changelog
Sign In
Get Started

Cannot connect site to TTSWP

4 min read

You clicked Get Started on the Connect Card but the connection did not complete. The popup did not open, the new tab errored, or you returned to WordPress and nothing changed. This page covers the most common causes in order from most to least likely.

Cause 1: Popup blocker stopped the new tab

Symptom: Clicking Get Started does nothing visible. No new tab opens.

Why: Your browser blocked the popup before it could reach app.ttswp.com.

Fix:

  1. Look for a small popup-blocked icon in the browser address bar (right side, usually).
  2. Click it and choose Always allow popups from this site.
  3. Click Get Started again.

In Chrome: address bar → small blocked-popup icon → "Always allow". In Firefox: address bar → shield icon → site permissions. In Safari: Preferences → Websites → Pop-up Windows → Allow.

Cause 2: Your site cannot reach app.ttswp.com

Symptom: The popup opens but shows "Cannot reach server", or you complete sign-up on app.ttswp.com but the WordPress admin never shows the connected state.

Why: Your host blocks outgoing HTTPS requests to external domains, your firewall is filtering, or a corporate proxy is in the way.

Fix:

  1. From WordPress, open Tools → Site Health → Info → HTTP Requests.
  2. Look at the section labeled "Loopback request" and "HTTPS connection". Both should be green.
  3. If they are red, ask your host to allow outbound HTTPS to app.ttswp.com and *.ttswp.com.
  4. Common offenders: corporate firewalls, server-level mod_security rules, "WordPress security" plugins blocking outbound calls.

You can also test from the server itself:

curl -I https://app.ttswp.com/

A 200 or 301 response means the network path is fine. A timeout means the host is blocking it.

Cause 3: Third-party cookies blocked

Symptom: You sign in on app.ttswp.com successfully, the tab closes, but the WordPress Connect Card is still there.

Why: The connection handshake uses a short-lived cookie set by app.ttswp.com. If your browser blocks third-party cookies entirely, the cookie does not survive the redirect back.

Fix:

  • In Chrome: Settings → Privacy and Security → Cookies → Allow third-party cookies for ttswp.com.
  • In Safari: Preferences → Privacy → Prevent cross-site tracking off (for this session).
  • In Brave: lower the Shields setting for both ttswp.com and your WordPress site.

After the connection succeeds, you can turn third-party cookie blocking back on. The site token is stored in your WordPress database, not in cookies.

Cause 4: Local or staging site behind a VPN or private network

Symptom: The popup opens, sign-up looks fine, but the redirect back to your WordPress site fails because the URL is private (e.g. http://localhost:8080, https://staging.local, or a Cloudflare Access-protected URL).

Why: app.ttswp.com redirects back to your site URL on completion. If that URL is not reachable from the public internet, the redirect lands on nothing.

Fix:

  • On localhost: use a tunnel service like ngrok and set the WordPress site URL to the ngrok HTTPS URL for the connection step.
  • On a staging site behind Cloudflare Access or HTTP Basic Auth: temporarily disable the auth for the connection redirect URL, complete the connection, then re-enable.
  • If you cannot expose the site publicly, contact support for a manual token.

Cause 5: Site URL mismatch

Symptom: Connection completes but the plugin shows "Connected as a different site" or repeatedly drops the connection.

Why: Your WordPress Site Address (URL) in Settings → General does not match the URL the plugin is loaded from. Common causes: site is reachable on both www.example.com and example.com, or you recently migrated from HTTP to HTTPS but the Site URL still says http://.

Fix:

  1. In Settings → General, set both WordPress Address (URL) and Site Address (URL) to the canonical version (matching scheme, matching www/no-www).
  2. Save.
  3. Disconnect and reconnect from Text to Speech → My Plan & Credits.

Cause 6: Reverse proxy or CDN rewrites the connection callback

Symptom: Connection completes but the WordPress admin never updates. No errors visible.

Why: Cloudflare, Sucuri, or another reverse proxy is caching the WordPress admin or stripping the callback parameters.

Fix:

  • Exclude /wp-admin/ from the CDN cache.
  • In Cloudflare: Caching → Configuration → Bypass Cache on Cookie or add a page rule for *example.com/wp-admin/* set to Bypass Cache.

Cause 7: Already connected to another TTSWP account

Symptom: Sign-in on app.ttswp.com shows "This site is already connected to another account".

Fix:

  1. Sign in to the original TTSWP account on app.ttswp.com.
  2. Go to Sites and remove this site.
  3. Return to your WordPress admin and click Get Started again.

Still stuck?

Gather this information and contact support:

  • The exact step where the connection fails (popup, sign-up, redirect, or admin update)
  • Your WordPress Site URL from Settings → General
  • Whether the site is on localhost, staging, or production
  • Any error message visible in the browser console (F12 → Console)
  • The URL the browser was on when the connection failed