-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unauthorized New accounts should be created on the new version of GitBook. Head to https://www.gitbook.com #2119
Comments
I'm new to Gitbook. I tried to sign in with my Github account and got the 401 message. |
I used Google account appeared 401 when I logged in gitbook -V
os win10 |
+1 I just created an account on the new version of GitBook and I'm getting this error message. This really sucks as I'm unable to add any comments in the docs here: https://basarat.gitbooks.io/typescript/content/docs/getting-started.html When I click the "Sign in to comment" link, I'm getting redirected to legacy.gitbooks.com. Selecting "Sign in with Google" results in the following error message. |
+1. I'm new to Gitbook. I tried to sign in with Google account but got 401.
And use it on windows 10. |
I have encountered the same problem, has the problem been solved yet? |
same problem here, any way to solve it? |
same problem |
Same here. Account on www.gitbook.com exists, but I cannot use that account to login into legacy.gitbook.com. Trying to login via "use github" leads to the 401 with a hint to www.gitbook.com. |
same here.
|
The same. |
same problem. |
I'm new to Gitbook. I tried to sign in with GitHub account but got 401. |
still the case(New accounts should be created on the new version of GitBook) |
same case |
same problem |
same case |
same problem
|
Has anyone been able to figure out what the issue is? 401 Unauthorized New accounts should be created on the new version of GitBook. Head to https://www.gitbook.com |
same case |
Unauthorized
New accounts should be created on the new version of GitBook. Head to https://www.gitbook.com
Thank you for giving us your feedback! We listed some guidelines to help you:
If possible, open separate issues for each bug report. Avoid grouping bugs that are unrelated.
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce. if possible, provide the GitBook version being used (
gitbook -V
) and the system infromations (OS and version).What is the expected behavior?
How do you think, or how would you like it should behave.
For legacy.gitbook.com
Provide, if possible, your username and the URL of the concerned book.
The GitBook Team
The text was updated successfully, but these errors were encountered: