Skip to content
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

Keep getting logged out #1161

Open
theCapypara opened this issue Aug 2, 2023 · 10 comments
Open

Keep getting logged out #1161

theCapypara opened this issue Aug 2, 2023 · 10 comments

Comments

@theCapypara
Copy link

Description

Octotree keeps logging me out. This seems to be an issue with the API. I opened the inspector for the extension and can see that requests are regularly failing.

When that happens the extension immediately logs out.

Environment (if bug)

  • Octotree version: v7.9.3
  • Browser & version: Chrome 115.0.5790.102
  • OS & version: Arch Linux
  • Screenshot, if any (drag an image here)
  • Console error log below this line

_generated_background_page.html:1 Access to fetch at 'https://www.octotree.io/api/v1.0/users/token/refresh' from origin 'chrome-extension://bkhaagjahfmjljalopjnoealnfndnagc' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

@danhgit
Copy link
Contributor

danhgit commented Aug 11, 2023

Hi, we can't reproduce this issue. Is it still happening? If it is, can you check if you happen to have some other extension or behind firewall that blocks requests to Octotree?

@theCapypara
Copy link
Author

Hi! I can't test at the moment, will do in a couple of weeks when I'm back at work, but to add some context, I already looked a bit more into this, and it seems that every time this error occured your API has returned 500s without the Access-Control-Allow-Origin headers. I don't think another extension is interfering, as I was able to reproduce it with CURL by just cppying the Request as CURL from the Chrome Dev Tools. It seems the API is returning 500s randomly for a short time and then functions again.

This has been going on for 2-3 months for me before I opened the issue.

@danhgit
Copy link
Contributor

danhgit commented Oct 23, 2023

Hi @theCapypara is there any update?

@theCapypara
Copy link
Author

Hi thanks for asking! The issue did not really get better, so I stopped using Octotree for a while.
Will install again and see if it got any better now.

@theCapypara
Copy link
Author

@danhgit Sadly this is still happening. Today I just get logged almost immediately. Here's a screenshot from the extensions inspector:
image

@danhgit
Copy link
Contributor

danhgit commented Oct 26, 2023

Thanks. I appreciate you tested it. This is very strange because we do send CORS headers with that API call.
Can you email me at [email protected] with a screenshot of the response headers for the api/v1.0/users/token/refresh API call?

@theCapypara
Copy link
Author

Will do, I actually ran the extension today again and everything was fine. But next time this happens I'll record the headers and send them.

However I kinda also think I got the issue: It seems that whenever there is a Gateway Timeout, Internal Server Error or Too Many Requests* response, there are no CORS headers sent in the response and the extension logs me out.

*: Although the Too Many Requests response also makes no sense, I made the last screenshot 10 minutes after my previous attempt to get the extension working. In general I guess it's odd I'm running into so many errors.

@theCapypara
Copy link
Author

Today this happened again, I was unable to really use the extension at all. I have sent the response information via email.

@danhgit
Copy link
Contributor

danhgit commented Dec 4, 2023

@theCapypara sorry for taking long to get back. This has taken quite a bit of investigation. I'm sending you an email to follow up.

@ivan-moto
Copy link

Not sure if it's the same issue but I get asked to log in every single day. Would be nice to fix that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants