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

Broken connection to Neurodesktop #32

Closed
korbinian90 opened this issue Dec 7, 2023 · 3 comments
Closed

Broken connection to Neurodesktop #32

korbinian90 opened this issue Dec 7, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@korbinian90
Copy link

OS: Windows
Neurodesktop App Version: 1.3.0

The Neurodesk App and The JupyterLab interface worked as usual, but opening the Neurodesktop failed.

Expected Behaviour:
Clicking the Neurodesktop button starts the Apache Guacamole window, where either RDP or VNC desktop connection can be selected

Error:
Instead of Starting the Apache Guacamole window to select the connection, a error 400 (I think) window was shown with some java problem (unfortunately no screenshot).
Restarting the app didn't fix the problem.

Solution:
After "Open Developer Tools -> Application -> Clear site data", the connection worked again

@korbinian90 korbinian90 added the bug Something isn't working label Dec 7, 2023
@iishiishii
Copy link
Collaborator

Hi Korbinian.

Thanks for logging the bug.
If it was fixed by clearing site data, I guess it was due to multiple instances spinned up so I tried to reproduce it by doing so.

Does the error look like this?

Screenshot from 2024-01-19 14-17-04

@iishiishii iishiishii self-assigned this Jan 19, 2024
@korbinian90
Copy link
Author

From what I remember, when clicking on the Neurodesktop button in the Launcher, a new window opened. Instead of the Guacamole window it showed a blank white window with an error. Maybe the javascript error was the same, I unfortunately didn't create a screenshot.

@iishiishii
Copy link
Collaborator

I found the cause of what I can replicate as in the screenshot above.

Every time new window is opened on top of existing window, docker starts another container with the same name name and try to remove the existing one but failed since the container is still running.

And cache is not cleared every time we start new window.

Fixed it in this commit 737f704 and new release.
I'll close the issue for now but feel free to re-open if you got the error again.

iishiishii added a commit that referenced this issue Jan 25, 2024
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