Login issues

Diagnose stuck sign-ins, OAuth provider errors, and "invalid credentials" messages.

May 21, 2026

If you can't sign in to Vulgate, work down this checklist — most issues are fixed in the first two or three steps.

1. Wrong email or password

Double-check:

  • The email address is correct (no typos, right domain).
  • Caps Lock is off — passwords are case-sensitive.
  • You're typing the password for Vulgate specifically — a password manager pulling from another site is a common cause.

If you're not sure of the password, use Forgot your password? and we'll send a reset link. See Resetting your password.

2. Email not confirmed

If your account exists but the email hasn't been confirmed, look for our confirmation email (it may have landed in spam — see Why didn't my email arrive?) and click the link inside.

3. OAuth sign-in (Google, Facebook, or Microsoft) fails

The most common OAuth issues:

  • "Permission denied" — You declined a permission the provider asked for. Try again and accept all requested permissions; Vulgate only asks for the minimum (email and basic profile).
  • "Account already exists" — You previously signed up with an email/password using the same address. Sign in with email and password first.
  • "Provider unreachable" — Google, Facebook, or Microsoft is having a temporary outage. Wait 5 minutes and retry, or use email/password sign-in.

4. Sign-in succeeds but the page is blank

This usually means a JavaScript error during initial app load. Try:

  • Hard reload. Press Ctrl+Shift+R (Windows / Linux) or Cmd+Shift+R (macOS).
  • Clear site data. In your browser's site settings for vulgate.ai, clear cookies and local storage, then sign in again.
  • Disable extensions. Ad blockers, privacy extensions (uBlock Origin, Privacy Badger), or password managers can occasionally block scripts. Try an Incognito window.

5. Browser issues

  • Out-of-date browser. Try the latest stable Chrome, Edge, Safari, or Firefox.
  • Cookies disabled. Vulgate uses cookies for authentication. Enable cookies for vulgate.ai.
  • Time-of-day skew. If your computer's clock is significantly wrong, OAuth and TLS will fail mysteriously. Make sure system time is synced.

6. Corporate VPN or proxy

A few corporate networks block parts of the auth flow. To test, try signing in:

  • On a personal device on home WiFi.
  • On a mobile phone on cellular data.

If those work and the corporate network doesn't, ask IT to whitelist vulgate.ai and your auth provider's domain.

Still stuck?

Email info@vulgate.ai with:

  • Your email address.
  • The exact error message (a screenshot is great).
  • Your browser and OS.
  • Whether the issue happens in an Incognito window.

We respond within one business day, often within hours.

Related

Search help