# Cannot Login Via CLI - › Warning: current base is set to https://prismic.io/

**URL:** <https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843>\
**Category:** Developing with Prismic\
**Tags:** cli, slice-machine\
**Created:** [May 3, 2024, 12:46pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843 "2024-05-03T12:46:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![createcacoon](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@createcacoon](https://community.prismic.io/u/createcacoon)\
**Post date:** [May 3, 2024, 12:46pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/1 "2024-05-03T12:46:01Z")

</div>

## Describe your question/issue in detail

Cheers,

I'm unable to login via CLI. When I execute `prismic login`, I first receive this message:

```auto
 › Warning: current base is set to https://prismic.io/
Prismic: Press any key to open up the browser to login or q to exit: 
Opening browser to https://prismic.io/dashboard/cli/login?port=5555
Prismic: Logging in... ⡿ Waiting for the browser response

```

Then I'm directed to the browser, where I get the error:

"Oops - It looks like you are trying to log into Prismic through your terminal, but something has gone wrong. You can try again by running `prismic login` from your terminal. If the issue persists, please post on [community.prismic.io](http://community.prismic.io)"

Repo: cacoon-slicemachine

### Impacted feature

### What steps have you taken to resolve this issue already?

### Errors

### Your Role

Engineer

### Hosting provider

Vercel

### Package.json file

### Steps to reproduce

---

<div class="post-metadata">

**Author:** ![nf\_mastroianni](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/nf_mastroianni/32/7071_2.png) [@nf\_mastroianni](https://community.prismic.io/u/nf_mastroianni)\
**Post date:** [May 3, 2024, 1:38pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/2 "2024-05-03T13:38:10Z")

</div>

Hi There! Simple quick question to see if this might help. Have you tried running `prismic logout` and then `prismic login` that used to be a trick that would help me when my login status was acting funky.

---

<div class="post-metadata">

**Author:** ![createcacoon](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@createcacoon](https://community.prismic.io/u/createcacoon)\
**Post date:** [May 3, 2024, 5:43pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/3 "2024-05-03T17:43:12Z")

</div>

Thanks for the quick response @nf_mastroianni . Unfortunately, that did not change the situation, I'm receiving the same error.

---

<div class="post-metadata">

**Author:** ![nf\_mastroianni](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/nf_mastroianni/32/7071_2.png) [@nf\_mastroianni](https://community.prismic.io/u/nf_mastroianni)\
**Post date:** [May 3, 2024, 5:55pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/4 "2024-05-03T17:55:44Z")

</div>

@createcacoon Can you report back your installed CLI version?  
FWIW, this is me:

```auto
prismic --version
prismic-cli/4.2.3 wsl-x64 node-v20.11.1

```

---

<div class="post-metadata">

**Author:** ![createcacoon](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@createcacoon](https://community.prismic.io/u/createcacoon)\
**Post date:** [May 3, 2024, 6:06pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/5 "2024-05-03T18:06:34Z")

</div>

Here's what I'm workin' with:

```auto
prismic --version
prismic-cli/4.2.3 darwin-arm64 node-v18.18.2

```

---

<div class="post-metadata">

**Author:** ![createcacoon](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@createcacoon](https://community.prismic.io/u/createcacoon)\
**Post date:** [May 8, 2024, 2:24am UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/6 "2024-05-08T02:24:35Z")

</div>

This is still an issue, I cannot save my new additions.

---

<div class="post-metadata">

**Author:** ![nf\_mastroianni](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/nf_mastroianni/32/7071_2.png) [@nf\_mastroianni](https://community.prismic.io/u/nf_mastroianni)\
**Post date:** [May 8, 2024, 2:59am UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/7 "2024-05-08T02:59:38Z")

</div>

Hi @createcacoon, I'm sorry you're still having this issue. I've never seen this error before.  
Have you, by chance, attempted to spin up another project just to see? Have you tried cloning your project on a different device to see if it has anything to do with your environment?

Ok so, for laughs, I decided to try using GitHub Codespaces to test out their environment. I did get a similar error to what you mentioned. I believe this has to do with the environment though. My logged in state on my local machine is not able to be seen by prismic-cli in the codespace instance.

I'd be very curious if you could test your setup on a different (but still local) machine.

---

<div class="post-metadata">

**Author:** ![createcacoon](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@createcacoon](https://community.prismic.io/u/createcacoon)\
**Post date:** [May 8, 2024, 5:25pm UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/8 "2024-05-08T17:25:26Z")

</div>

Interesting thought, I suppose I will have to try.

What I did try: I would log out, log back in. I created a new account, transferred project ownership to the new account, then tried logging in; same issue. I did this again with _another_ new account, same issue. Transferred back to the original account, still an issue.

I can try with a new project, I suppose. I can also try same project, different machine. I will circle back.

---

<div class="post-metadata">

**Author:** ![idealdl](https://avatars.discourse-cdn.com/v4/letter/i/76d3ee/32.png) [@idealdl](https://community.prismic.io/u/idealdl)\
**Post date:** [November 3, 2024, 10:50am UTC](https://community.prismic.io/t/cannot-login-via-cli-warning-current-base-is-set-to-https-prismic-io/15843/9 "2024-11-03T10:50:24Z")

</div>

Hey! I am having the same problem, I tried creating a new account, but it does not work. I have prismic-cli/4.2.3 darwin-arm64 node-v20.11.0 I can't login in chrome...  
I also tried to use Prismic on the different laptop with windows and it works, so it is definitely something connected with my Mac. Any ideas how can I overcome this?
