-
Notifications
You must be signed in to change notification settings - Fork 2.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
'token expired' on different time zones #638
Comments
@wcone could you try cleaning up the cache and cookies please? |
@hacdias i figured out why... my machine A was running on a different time zone. After correcting the time it works seamlessly thank you. |
@wcone oh, it shouldn't happen though. I'll reopen this. |
Same problem, but my machines are running on same time zone. |
@hacdias I also noticed this problem. (and I've wrote an article http://nanodm.net/post/why-filebrowser-raise-wrong-credentials-error-even-with-right-credentials/ ) it is a frontend code problem. frontend/src/utils/auth.js if (Math.round(new Date().getTime() / 1000) > data.exp) {
throw new Error('token expired')
} |
@ttys3, what would you recommend? Just remove that code and let the backend determine it? If so, could you open a PR for that ? 😃 |
I'm closing this since this repository will be archived. Please read the information on the README for more information. Thanks for all your contributions! |
Hi i'm quite new to this and docker.
i setup a v2.0.0 with docker on machine A in the local network and everything works like a charm.
i tried to access the filebrowser from machine B in the same local network but somehow i'm getting "invalid credential" error message. I've checked the token return on jwt, seems valid and with proper expiry date.
i proceed with a "noAuth" config and this time round on machine B i'm getting "Uncaught (in promise) Error: token expired" from the console.
![screenshot 2019-01-22 at 2 49 42 pm](https://user-images.githubusercontent.com/46917021/51517186-f8193b00-1e54-11e9-9d3d-eb2bacfc3f52.png)
this is how i ran the docker:
docker run -d --privileged --name=filebrowser -v <root path>:/srv -v <path to json>:/.filebrowser.json -p 80:80 filebrowser/filebrowser:v2.0.0
and this is the json config:
{ "port": 80, "noAuth": true, "baseURL": "", "address": "", "log": "stdout", "database": "/database.db", "root": "/srv" }
I've tried v1.11.0 and is working as expected.
i'm not sure if i missed out anything for v2.0.0 but any help is appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: