Embiid's BLOG

Writing & talking about engineering, airplane, and things I find interesting. #100Days

Can Not Sign Up Or Sign In Warp With Github(Public Beta)

Can't sign up or sign in Warp with Github?

Oops! We are unable to log you in. Don't have an account? Click here to sign up.

Warp does not work properly when connected through a proxy?

Let's follow the article to summarize the Login issues and fix it hand by hand.

brown and white long coated small dog wearing eyeglasses on black laptop computer

Warp is now in the public beta

Warp, the Rust-based modern terminal, is now in public beta! That means you don't need an invite code anymore! Congrats!

Been using Warp since private beta and love how it gets better every week. Super exciting for Warp to get more attention. Rock on Warp team!

Excited to share that, Try it out now:

Any Mac user can now download and use Warp here 👉 https://warp.dev

Alternatively, you can via Homebrew: brew install warp

There is an exponential bomb in the GitHub issue list because of the public beta release. And the most is the Login issues.

Let's follow the article to summarize the Login issues and fix it hand by hand.

What is the reason of can't sign in to Warp?

Depending on the scenario, there can be different possibilities that are responsible for this error. Some of those causes are listed below:

Case one: Misleading the button text

When you click the "Sign in" button, it will look like this.

How it started:

How it’s going:

Look at it, you're either signing up or logging in to Github through the Warp, but the actuality is that you're signing up or logging in to Warp.

Therefore, It shows you the tips "Oops! We are unable to log you in. Don't have an account? Click here to sign up".

What does the button mean?

The button text "Sign up with Github" is a bit confusing, Meaning Sign up for Warp with your GitHub.

Yep, it should be more explicit. The big button "Sign up with Github" should be "Create a Warp account with your Github." and the smaller text "Sign in" should be "Already have a Warp account, sign in."

How to fix it?

As you can see, click the button "Sign up with Github"!

And It's Done! It will work fine.

Case two: No pop-up or get a blank pop-up

After the initialization of Warp, the app asks to sign in with the Github account. The sign-in process is not going further and blocks this window on the browser.

Or you get a blank pop-up, And once the pop-up is gone, it's just back to this with no other options.

How to fix it?

Oh dear, Do you have an ad blocker active? It could potentially block the sign-in pop-up.

Please inactive your ad blocker and try it again.

Alternatively, Try removing the Warp folders in the Library/ Application Support and then relaunch the Warp!

Case three: Login successful but Warp does not response

After you have verified by Github successfully on the webpage, you can see the "You're logged in!" message. Then follow the Take me to warp link to the app. After a time elapsed, the app responded.

However, there is nothing changed still waiting for you to log in or signup.

How to fix it?

Here’s a quick guide to how we go about Warp bug fixing.

If you use a rule based proxy for Mac, please follow the quick guide.

Method One: Add HTTP_PROXY and HTTPS_PROXY to the rc file and then run Warp .stable file

Method source: Warp does not work properly when connected through a proxy · Issue #705 · warpdotdev/Warp · GitHub

First, you should copy the command and config the proxy to your terminal.

Not sure which proxy HTTP port used that You could change 7890 to your HTTP port.

7890 means your proxy HTTP port.

NOTE:

If you use ClashX as your proxy, its default HTTP port maybe is 7890.

If you use ShadowsocksX-NG as your proxy, its default HTTP port maybe is 1087.

export https_proxy=http://127.0.0.1:7890 http_proxy=http://127.0.0.1:7890 all_proxy=socks5://127.0.0.1:7890

It's not necessary to add all_proxy=socks5://127.0.0.1:7890 to the rc file. Why we add it is because some proxy does not work for HTTP_PROXY.

Now, go to /Applications/Warp.app/Contents/MacOS directory and launch Warp via ./stable file.

cd /Applications/Warp.app/Contents/MacOS/stable

./stable

Alright, you did it.

Method Two: Check this article out: WARP does not work after submitting an invite code

Case four: Authorising with GitHub fails / authentication / firebase

It maybe is the Case four If you have the same issue:

Clicking 'Sign Up with GitHub' opens a blank pop-up that disappears after a few seconds.

Does your Mac seem to prevent the browser from seeing any response from the firebaseapp.com domain?

When your browser tries to load https://astral-field-294621.firebaseapp.com/__/auth/iframe.js, the requests appear to fail?

Does the Mac have various pieces of security software installed or connecting via company VPN?

More detail: Authorising with GitHub fails / authentication / firebase · Issue #233 · warpdotdev/Warp · GitHub

How to fix it?

I have no idea about it.

But the good news is that Warp has a potential lead on this issue! They will send updates as they investigate!

👉Authenticate Using Google with JavaScript  |  Firebase Documentation

If you have a method to fix it, please comment on the post to share it.

Last but not least

Here's the issue for the Login issue, please subscribe. The Warp team will update this first when fixed it.

If you are still having issues please join this WARP discord channel or open a new Github issue.

Originally published at Embiid’BLOG.

WARP does not work after submitting an invite code

Oops! We are unable to log you in. Don't have an account? Click here to sign up.

Not respond on signing-in Github even though It shows a "You‘re logged in!" message?

WARP doesn't follow system proxy?

Please follow the article to fix it.

At the end of the last article, we talk about the bug that login in with Github but WARP does not work.

In this article, I will share a method for achieving this.

What's the bug?

After you submit an invite code, then hit "Sign in" => "Login with GitHub". And you can see "You're logged in!" message.

However, there is nothing changed still waiting for you to log in or signup.

Ask for help

I have no idea about it. I think we should ask for help?

There are so many sources of help online.

Here we go, Bring-in outside help:

If you're in luck, It might be descriptive enough to tell you exactly what went wrong or else give you a search query to find the solution on the web somewhere.

Unfortunately, No luck in there.

What happens to WARP?

Let's return to the sign-in page, Type command cmd + shift + C.

The console of WARP logged some errors:

chromeconsolepng

According to the information, It seems like a network error :

WARP does not work because the WARP doesn't receive the message.

Therefore, Gather more Information in WARP.

WARP Log everything, so we can analyze the logs.

SHOW ME THE LOG!

After looking out the warp log, I immediately noticed it had some network errors:

Failed to flush events from Telemetry queue to Segment: https://api.segment.io/v1/batch: error trying to connect: connect timed out
Error checking for update error sending request for url (https://storage.googleapis.com/warp-releases/channel_versions.json?r=1234): operation timed out
Error loading invite from server: error sending request for url (https://securetoken.googleapis.com/v1/token?key=AzIaSsgBy4rew9hAdayJLxJ7mriFRsegUaUadaq): operation timed out
Initializing Sentry for cocoa app with endpoint https://1234a81da1234f55a93ee4534235f9ec@o563324.ingest.sentry.io/3213213

This can't be right! It's should be working for WARP.

How to Fix it?

Here’s a quick guide to how we go about WARP bug fixing.

If you use a rule based proxy for Mac, please follow the quick guide.

Method One: Add HTTP_PROXY and HTTPS_PROXY to the rc file and then run WARP .stable file

Method source: Warp does not work properly when connected through a proxy · Issue #705 · warpdotdev/Warp · GitHub

First, you should copy the command and config the proxy to your terminal.

Not sure which proxy HTTP port used that You could change 7890 to your HTTP port.

7890 means your proxy HTTP port.

NOTE:

If you use ClashX as your proxy, its default HTTP port maybe is 7890.

If you use ShadowsocksX-NG as your proxy, its default HTTP port maybe is 1087.

export https_proxy=http://127.0.0.1:7890 http_proxy=http://127.0.0.1:7890 all_proxy=socks5://127.0.0.1:7890

It's not necessary to add all_proxy=socks5://127.0.0.1:7890 to the rc file. Why we add it is because some proxy does not work for HTTP_PROXY.

Now, go to /Applications/Warp.app/Contents/MacOS directory and launch WARP via ./stable file.

cd /Applications/Warp.app/Contents/MacOS/stable

./stable

Alright, you did it.

But It still shows that "Oops! We are unable to log you in. Don't have an account? Click here to sign up." tips?

Check this article out: Can Not Sign Up Or Sign In Warp With Github(Public Beta)

I’d say that’s pretty sweet.

Method Two: Use ClashX Pro App

Step 1: Download ClashX Pro or others with Enhanced Mode

You'll need to make sure you have a rule based proxy for Mac with Enhanced Mode. To do that, let's step through the download.

Download ClashX Pro With Enhanced Mode and Native Apple Silicon support at AppCenter for free permanently.

Why we need a rule based proxy with Enhanced Mode?

IMPORTANT NOTE:

WARP may not obey the system proxy settings.

Using Enhanced Mode can make all applications handled by your rule-based proxy.

Step 2: Confirm open Enhanced Mode

Click Enhanced Mode:

clickEnhancedModepng

Step 3: Open the config file

Open config folder:

openconfigfolderpng

Step 4: Configure your config file

Add these rules to your config file.

PROXY is a name that I config. Maybe name proxy, proxies, or others. Please check it and replace it.
It depends on how your proxy-groups are config in your config file.

addrulestofilepng

NOTE:  I’m using Visual Studio Code as my editor. If you haven’t already tried it out, I’d highly recommend it! It’s lightweight, it’s FREE, it’s open source, and it runs everywhere.

This is all you need:

# > Warp
- DOMAIN,*.googleapis.com,PROXY
- DOMAIN,*.warp.dev,PROXY
- DOMAIN,*.segment.io,PROXY
- DOMAIN,*.sentry.io,PROXY

Save and close the config file you've edited.

We're done with the changes that need to be made!

Step 5: Restart ChashX Pro

Let's restart ClashX Pro.

That's all there is to it!

If you are still having issues please join this WARP discord channel or open a new Github issue.

Originally published at Embiid’BLOG.

How to get a Warp terminal invite code?

landscape photography of brown mountain

If you are interested in the Warp terminal, you should need an invite code.

Click here to download it.

Read more if the invite codes don't work.

What is Warp?

There is an introduction in warp documentation :

Warp is a blazingly fast, Rust-based terminal that makes you and your team more productive at running, debugging, and deploying code and infrastructure. It is a fully-native app built in Rust that renders on the GPU.

Why does the Warp terminal need an invite code?

Warp release started in 2021, so the product is in closed beta mode. They need some people to help them test out the product.

In the meantime, You'll need a GitHub account to log in (this is a temporary requirement until the product leave private beta)

How to get a Warp terminal invite code?

Here are some methods.

Method 1: Join the waitlist

Click the URL Request access here, and you will be on the waitlist after finishing the Questionnaire.

They are granting access regularly that be on the lookout for an email soon.

It will cost you almost a week.

Method 2: Join the Discord

You can also join their Discord—they drop invites every week in the #invite-codes channel.

As you can see, React with warp emoji to the message in #invite-codes channel that the warp bot should send you an invite code.

Please react to the Warp's icon:

Method 3: Invited by friends

Warp allow people to invite their friend but has a limit of 20 invites.

I also have 20 invites remaining that I want to be shared.

Please DM me. You could on Twitter, Medium, or The Article's Comments.

Why do we need to Log into Warp?

During our closed beta, we require a login so we can interact with you, get your feedback, and focus on improving the app. After installing Warp for the first time, you will be prompted to log in using your GitHub account (we only get access to the associated email address - read our approach to privacy).

Opening the app is the only time you need an active Internet connection. Otherwise, Warp is a fully-native, local app and runs fine with no internet connection whatsoever (although you will lose access to some of the cooler's features).

Warp does not respond after signing in?

Warp opens a new tab in the browser, but you still can't enter Warp after signing up with a Github account?

Do you have trouble like this image:

It may be your country blocking GitHub or maybe other reasons.

However, It is just a network problem.

Please change your network with proxy and try again.

Want to learn more details? Check this article -> WARP does not work after submitting an invite code.

Originally published at Embiid’BLOG.