-
Notifications
You must be signed in to change notification settings - Fork 138
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
Can't restart obsidian #90
Comments
Hi. I had a same issue. First I thought the issue was by old version of Docker on my Synology server or lack of git was a problem. Next I used a LXC container using same methodology and Docker Compose file like others, but nothing work. Only white window. Finally, I found a solution. I used a docker hub repo instead of Github Container Repository (ghcr.io). |
When I closed out the obsidian app, I now just get a blank screen. I have restarted the container and also even tried to point to a different obsidian repo with no luck. Any way to get it back up? |
Still having this problem. I believe, similarly to the original post here, that the obsidian.asar in the obsidian config directory is somehow related to the issue. By making sure this file does not exist prior to starting the docker container, everything will work perfectly fine. However, if it does exist, this error will be thrown.
This is accompanied by a white screen in the web interface, where the terminal and all other Guacamole actions work perfectly fine, it's just that Obsidian refuses to display anything under any circumstance. The error above suggests that the white screen is caused by Obsidian being unable to load a certain html file. I'm not skilled enough yet at Docker to figure out where the obsidian executable is being called, so that I can add the --trace-warnings flag, so I'm not entirely sure what already having Obsidian downloaded has to do with Obsidian refusing to load a certain html file. See comment below for better solution than this.
|
https://forum.obsidian.md/t/can-not-load-obsidian-ui-err-blocked-by-client-upon-launch/74066 |
Found a better workaround. This issue was mentioned in the original README.md of obsidian-remote, where the screen goes all white, and you're supposed to be able to right click and click Obsidian when that happens, to fix it. That wasn't working for me, and would create a new white screen. I fixed this by overriding the /config/.config/openbox/menu.xml with a new Obsidian launch command that deletes the .asar file before every launch. Same principle as my workaround above, but now it works without having to restart the container. My launch command for the container:
patch.xml (must be in same folder as start.sh)
|
Describe the bug
When running the latest version of obsidian, obsidian crashes when it re-starts without error logs.
I set obsidian-remote with the config and vaults as volumes like in the example docker-compose. It worked fine for a time, but in the past weeks, I have been unable to restart obsidian. It seems to be due to the obsidian config since it works when I remove it.
This is blocking for me since I can't synchronize the sync settings.
To restart obsidian, I used the method described at the bottom of the README and tried restarting the container. Both give the same result.
Edit:
This seems to be due to the updated version. When removing the downloaded
.asar
file, it works fine again, but when it re-downloads, it breaks again.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Obsidian should restart without errors
Desktop (please complete the following information):
Additional context
After restart screenshot:
Docker compose logs:
Obsidian logs:
The text was updated successfully, but these errors were encountered: