-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Sometimes i get invalid session after login when i try to execute a command and sometimes it works fine. Is this a known issue? #2
Comments
No, it isn't. Does it happen shortly after you execute the |
Yes it happens immediately after login as well. It gives following error.
Error: invalid session
And when I run the same again, it sometimes runs and sometimes gives this error. This happens about 33% of the times.
Thanks
Atul Gupta
…
On Jul 16, 2024 at 9:01 PM, Piotr Karasiński ***@***.***> wrote:
No, it isn't. Does it happen shortly after you execute the login command?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Are you using Quick Connect? Can you take a look in the You can also try to run the app with |
No, I am using it with local LAN IP only as it is within the same network and not using quick connect.
…
On Jul 16, 2024 at 10:55 PM, Piotr Karasiński ***@***.***> wrote:
Are you using Quick Connect? Can you take a look in the $HOME/.syno-photos-util if the address of your Synology looks correct?
You can also try to run the app with RUST_LOG=debug syno-photos-util ... and see if the output reports anything interesting, although that error is caused by the Synology API rejecting the session id, so it's unlikely we'll see anything useful.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sometimes i get invalid session after login when i try to execute a command and sometimes it works fine. Is this a known issue?
The text was updated successfully, but these errors were encountered: