Troubleshooting Login Issues

Instructions on how to troubleshoot login issues.

Can't "Sign Up" for Warp

Clicking it should open a login pop-up. If clicking the signup button opens a blank pop-up window, try using a proxy. Your ISP or Firewall may be blocking the app's call to * or * In some older Ruby development environments, .dev domains do not resolve properly and you may need to delete the /etc/resolver/dev, see more here.

All browsers

This error could occur if you installed an ad blocker and the ad blocker blocks all pop-ups, including our Firebase auth pop-up. To fix it:

  1. Disable your ad blocker for

  2. Refresh and try again


You are on Safari and you might notice in your console that you get the following messages:

  1. Unable to access localStorage

  2. And every time you click the "Sign Up" button, you get Unhandled Promise Rejection: Error: This operation is not supported in the environment the application is running on. "location.protocol" must be http, https, or chrome-extension and web storage must be enabled.

This error occurs likely because you are blocking all cookies in Safari's security settings, but Firebase Auth requires the cookie to record whether the user is logged in. To fix it:

  1. Go to Safari Preferences > Privacy

  2. Uncheck the "Block all cookies" checkbox

If "Sign Up" does not work after trying the steps above, fill out this Typeform and our team will reach out to you.


When behind a proxy, a possible workaround is to disable QUIC in the browser. It will then fall back to TCP and likely allow login.

  • In Chrome, or Chromium-based browsers like Edge, Opera, and Arc, type chrome://flags into the address bar.

    1. In the search bar on the flags page, type Experimental QUIC protocol.

    2. Locate the "Experimental QUIC protocol" flag and click on the drop-down menu next to it.

    3. Select "Disabled" from the options.

    4. Relaunch Chrome for the changes to take effect.

  • In Firefox, type about:config into the address bar.

    1. You will see a warning message. Click on the "Accept the Risk and Continue" button.

    2. In the search bar, type network.http.http3.enable.

    3. Double-click on the network.http.http3.enable preference to set its value to false. This will disable QUIC in Firefox.

    4. Restart Firefox for the changes to take effect.

  • In Safari, Unfortunately, there is no built-in option to disable QUIC in Safari. Safari uses QUIC as its default transport protocol and does not provide a user-accessible setting to disable it.

Can't open Warp from SSO

Directly launching Warp from Okta or other SSO providers' pages isn’t supported. This is due to a limitation with Warp authentication APIs. Instead, do the following:

  1. Choose “Continue with SSO”

  2. Login with your normal SSO credentials

How to get an Auth token to login

If the browser does not open from Warp directly when you click "Sign up" or "Sign in". Please go to the Signup page to create an account or Login page if you already have one, then copy the auth token from the "here" link on the logged_in page and paste it into Warp.

On Linux, the default copy-and-paste Keyboard shortcuts are CTRL-SHIFT-C and CTRL-SHIFT-V respectively. You may also need to change your default $BROWSER to chrome or firefox to workaround the log in issue.

If nothing happens when you click "Take me to Warp" on the logged-in page. If this happens to you, copy the "here" link on the web logged-in page ( to copy the authentication token, then paste it into the app as shown below.

If "Take me to Warp" is still not working it may be due to a proxy issue, please see this article for more information on a workaround here and please fill out this Typeform and our team will reach out to you.

Last updated