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

Images no longer loading after "a while" #897

Open
5 tasks done
chevdor opened this issue May 14, 2024 · 3 comments
Open
5 tasks done

Images no longer loading after "a while" #897

chevdor opened this issue May 14, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@chevdor
Copy link

chevdor commented May 14, 2024

First Check

  • This is not a feature request
  • I added a very descriptive title to this issue.
  • I used the GitHub search to find a similar issue and didn't find it.
  • I searched the documentation, with the integrated search.
  • I already read the docs and didn't find an answer.

Homebox Version

v0.10.3

What is the issue you are experiencing?

After "a while" (which I think is when the login cookie expires or something alike), the images are no longer displayed.
Here is a screenshot of a search with the search file empty:
image

If I sign out then sign in again (although I am using "remember me"), the issue is fixed.
image

It sounds like my session does expirre although I used "remember me". If the session did nonetheless expire, the question is why I can still browse and search?

I am using Brave but with shields down for Homebox.

How can the maintainer reproduce the issue?

I guess you would need to expirer those cookies and see what happends.

Deployment

Other

Deployment Details

Docker / K8S.

@chevdor chevdor added the bug Something isn't working label May 14, 2024
@Spreadcat
Copy link
Contributor

Not sure how to solve this permanently, but if somebody else encounters this bug, a temporary solution is to logout and re-login into homebox.

@chevdor
Copy link
Author

chevdor commented May 31, 2024

Yes, I confirm that logout/login is a workaround. Yet it seems a very repeatable.
Happy to provide more info on the env if that helps. Do you happen to have a link to the other issue ?

@Spreadcat
Copy link
Contributor

Other issue? Not sure I get what you mean?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants