Docker compose does not start - Guacamole connection closed during handshake #56
Comments
|
I'm having the same issue. |
|
Same here. Any solution for this available yet? |
|
Having the same problem. Will there be fix for this in the near future? |
|
Ill try this config later this week to see if I can reproduce. |
|
I second that. Same problem for me. I hope somebody else fix it. I've tried using UFW to allow ports. Nothing seems to work. |
|
Using the following docker-compose.yml worked for me. Obsidian-remote now works, but I don't like how it works. It basically uses Guacamole as VNC server/viewer. It doesn't fit the whole browser window if you click on it. Docker-compose.yml config I found (you can modify it according to your own taste): |
|
same problem here, use shell interact with the container find that the server failed starting. |
|
|
|
I solved it by removing the "" from the port, like so |
Hi there! I tried doing what you did but mine just said |
I'm getting the same message and when loading the page in a browser I also get services:
obsidian:
image: 'ghcr.io/sytone/obsidian-remote:latest'
container_name: obsidian-remote
restart: unless-stopped
ports:
- 8081:8081
- 8443:8443
volumes:
- /home/obsidian/vaults:/vaults
- /home/obsidian/config:/config
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Stockholm
- DOCKER_MODS=linuxserver/mods:universal-git
- CUSTOM_PORT=8081
- CUSTOM_HTTPS_PORT=8443
- CUSTOM_USER=""
- PASSWORD=""
- SUBFOLDER=""
``` |
|
Hi Guys, By doing a bit of a mix of the two docker compose that are in this thread here is one that works: |
|
It seems like Looking into the container with I also noticed that the user and group within the container is I stopped at the point where I'd have to clone the repo and build the image from the Dockerfile as I am running out of time to fiddle with it today, if anyone gets it working definitely let me know. p.s. the docker compose config from @tosmaniac modified to have the commented fields uncommented and port numbers unquoted was the closest I managed to get, only outputting this error instead of the longer ones above. |
|
I had the
|
|
I ended up having to do a number things, which leads me to believe there's not one issue, but several small issues. Here's my docker-compose.ymlNote: I opted to build using the local services:
obsidian:
# image: 'ghcr.io/sytone/obsidian-remote:latest'
build:
context: ./
dockerfile: Dockerfile
container_name: obsidian-remote
restart: unless-stopped
security_opt:
- no-new-privileges:true
healthcheck:
test: curl -f http://localhost:7436/ || exit 1
ports:
- 7436:8080 # I'm using a different host port to avoid collision
- 7496:8443 # I'm using a different host port to avoid collision
- 27123:27123
- 27124:27124
volumes:
- ./my-vaults:/vaults
- ./my-config:/config
environment:
- PUID=1000 # this matches my user when I run `id $USER`
- PGID=1000 # this matches my user when I run `id $USER`
- TZ=America/New_York
- DOCKER_MODS=linuxserver/mods:universal-git
- CUSTOM_PORT=8080
- CUSTOM_HTTPS_PORT=8443
- CUSTOM_USER=yourUser
- PASSWORD=yourPassword
# - SUBFOLDER=""This gave me a little bit of progress, but I couldn't yet open Obsidian successfully. I got some sort of error like Updates to menu.xml
<?xml version="1.0" encoding="utf-8"?>
<openbox_menu xmlns="http://openbox.org/3.4/menu">
<menu id="root-menu" label="MENU">
- <item label="Obsidian" icon="/squashfs-root/usr/share/icons/hicolor/48x48/apps/obsidian.png">
+ <item label="Obsidian" icon="/usr/share/icons/hicolor/48x48/apps/obsidian.png">
<action name="Execute">
- <command>/squashfs-root/obsidian --no-sandbox --disable-dev-shm-usage --disable-gpu --disable-software-rasterizer</command>
+ <command>obsidian --no-sandbox --disable-dev-shm-usage --disable-gpu --disable-software-rasterizer</command>
</action>
</item>
<item label="xterm" icon="/usr/share/pixmaps/xterm-color_48x48.xpm">
<action name="Execute">
<command>/usr/bin/xterm</command>
</action>
</item>
<item label="Reload OB">
<action name="Reconfigure" />
</item>
</menu>
</openbox_menu>Changes to autostart
- /squashfs-root/obsidian --no-sandbox --disable-dev-shm-usage --disable-gpu --disable-software-rasterizer
+ obsidian --no-sandbox --disable-dev-shm-usage --disable-gpu --disable-software-rasterizerThe last change is not required, but something I did just to improve my QoL (Qualify of Life). Changes to Dockerfile ...
- ARG OBSIDIAN_VERSION=1.4.16
+ ARG OBSIDIAN_VERSION=1.5.3
... |
|
Is this on AMD or ARM? |
with this config i got no websocat error, but in the logs i got this: it doesnt matter if i use the last four lines with the costum ports, user and passwort, same result. does anybody got it working? |
I'm having the same issue, Tried all suggested changes above but nothing is working for me. |
|
I was able to get it working by pulling this newer image not from ghcr.io |
|
In 2024 images from ghcr.io are outdated. It is better to use images from dockerhub with latest Obsidian installations. PreparationFolders involved: Execute:
Attention: After docker-compose has been started, please open http://localhost:8082/ in your browser. If there is kind of black screen or empty desktop:
docker-compose.yml |
The following below does not work for me when I have a black screen. The directory does not exist. After docker-compose has been started, please open http://localhost:8082/ in your browser. If there is kind of black screen or empty desktop: |
|
@2ndwonder This is why you need root privileges. Otherwise you cannot access the system files /opt/obsidian |
|
First, I am using the one from linuxserver.io, as this project did not seem to work for me, ( white window) In portainer terminal it was giving error it cannot open the the config folder should be somewhere on your system, as it is maped via docker-compose (in my case) |
and others
Describe the bug
At first setup of docker compose logs shows error related to
Guacamole connection closed during handshakeTo Reproduce
Below docker compose:
Log info from docker:
Expected behavior
Start normally
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: