Troubleshooting Login Issues
Instructions on how to troubleshoot login issues.
Last updated
Was this helpful?
Instructions on how to troubleshoot login issues.
Last updated
Was this helpful?
Clicking it should open a signup or login pop-up. If clicking the button opens a blank pop-up window, try using a proxy. Your ISP or Firewall may be blocking the app's call to *.googleapis.com
.
This error could occur if you installed an ad blocker or have stale browser cookies, including our Firebase auth pop-up. To fix it:
Disable your ad blocker for app.warp.dev
Clear any cookies and cache, or open a incognito / private browser window
Try again
You are on Safari and you might notice in your console that you get the following messages:
Unable to access localStorage
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:
Go to Safari Preferences > Privacy
Uncheck the "Block all cookies" checkbox
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.
In the search bar on the flags page, type Experimental QUIC protocol
.
Locate the "Experimental QUIC protocol" flag and click on the drop-down menu next to it.
Select "Disabled" from the options.
Relaunch Chrome for the changes to take effect.
In Firefox, type about:config
into the address bar.
You will see a warning message. Click on the "Accept the Risk and Continue" button.
In the search bar, type network.http.http3.enable
.
Double-click on the network.http.http3.enable
preference to set its value to false
. This will disable QUIC in Firefox.
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.
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:
Choose โContinue with SSOโ
Login with your normal SSO credentials
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 (https://app.warp.dev/logged_in) to copy the authentication token, then paste it into the app as shown below.
Go to
If the browser does not open from Warp directly when you click "Sign up" or "Sign in". Please go to the page to create an account or 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.
the On Linux, the default copy-and-paste are CTRL-SHIFT-C
and CTRL-SHIFT-V
respectively.
On Linux and WSL you should install and set your default $BROWSER
to brave-browser
to workaround any copy-paste issues. Please see the workaround guide below.
If "Take me to Warp" is still not working it may be due to a , please see this article for more information on a workaround .
If Sign Up or Login does not work after trying the steps above, fill out and our team will reach out to you.