Unable to access the webui #77

sendev1 · 2024-12-03T04:46:33Z

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I used the docker compose as below in my raspberry pi which runs Debian GNU/Linux 12 (bookworm)

services:
  kasm:
    image: lscr.io/linuxserver/kasm:latest
    container_name: kasm
    privileged: true
    security_opt:
      - apparmor:rootlesskit #optional
    environment:
      - KASM_PORT=4443
      #- DOCKER_HUB_USERNAME=user #optional
      #- DOCKER_HUB_PASSWORD=pass #optional
      #- DOCKER_MTU=1500 #optional
    volumes:
      - ./data:/opt
      - ./profiles:/profiles #optional
      - ./dev/input:/dev/input #optional
      - ./run/udev/data:/run/udev/data #optional
    ports:
      - 3000:3000
      - 4443:443
    restart: unless-stopped

The container is up

docker ps
CONTAINER ID   IMAGE                                     COMMAND                  CREATED          STATUS
   PORTS                                                                                            NAMES
a326b350ca30   lscr.io/linuxserver/kasm:latest           "/init"                  18 minutes ago   Up 18 minutes           0.0.0.0:3000->3000/tcp, :::3000->3000/tcp, 0.0.0.0:4443->443/tcp, [::]:4443->443/tcp             kasm

But when i hit the url https://my-ip:4443/ i am not seeing any ui. I am seeing ERR_CONNECTION_REFUSED in browser.

Expected Behavior

No response

Steps To Reproduce

See above.

Environment

- OS:Debian
- How docker service was installed: using Open Media Vault. I other containers running successfully.

CPU architecture

arm64

Docker creation

docker compose up -d

Container logs

Logs

docker logs kasm
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

...+......+...+....+............+...............+...+............+.....+...+......+.......+..+..................+....+.....+......+.........+.+..+.......+...+.....+.+.........+.....+.+..+...+....+..+.........+.......+..+......+.......+............+...+...+..+..........+..+.+..+.......+.....+.+.........+.....+......+.+.....+...+............+.+...+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*..+.......+............+.....+....+.....+.+...+..+......+.......+..+.........+....+...+..+.+......+........+.+..+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*.+.................+.+...+............+..+.......+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
..+...+...+...+.+.........+..+..........+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*..............+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*......+.............+...+............+..+.+..................+..+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----
[custom-init] No custom files found, skipping...
[ls.io-init] done.

The text was updated successfully, but these errors were encountered:

github-actions · 2024-12-03T04:46:56Z

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

drumtechphoto · 2024-12-04T00:12:54Z

I am getting a similar of not the same issue on Unraid 6.12.14

Kasm just gets stuck after "[ls.io-init] done."
New error found as already noted at bottom of this log relating to >>
-- "WARNING! Using --password via the CLI is insecure. Use --password-stdin...."

Steps Taken to Reproduce & attempt Resolve:

Wiped installation completely including deleting all files for kasm
Reinstalled with latest docker image, "1.16.1-ls50" (container already set to use the latest).
When the issue occurred: noticed as of today, 12/3/2024
Previous image release was outputting a lot of errors, did not save logs for review... :(

Environment:

OS: Unraid 6.12.14 / Slackware 15.0 x86_64 (post 15.0 -current) x86_64
Host: Supermicro X10DRi-T4+
Kernel: 6.1.118-Unraid
Shell: bash 5.2.15
CPU: Intel Xeon E5-2667 v3 (32) @ 3.600GHz
GPU: NVIDIA Tesla P4
GPU: NVIDIA Tesla P4
Memory: 14676MiB / 64301MiB

Current Logs for latest docker image of ""1.16.1-ls50":

docker logs kasm:

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

  ██╗     ███████╗██╗ ██████╗
  ██║     ██╔════╝██║██╔═══██╗
  ██║     ███████╗██║██║   ██║
  ██║     ╚════██║██║██║   ██║
  ███████╗███████║██║╚██████╔╝
  ╚══════╝╚══════╝╚═╝ ╚═════╝

Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID: 911
User GID: 911
───────────────────────────────────────

WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Get "https://registry-1.docker.io/v2/": unauthorized: your account must log in with a Personal Access Token (PAT) - learn more at docs.docker.com/go/access-tokens
[custom-init] No custom files found, skipping...
[ls.io-init] done.
`

drizuid · 2024-12-09T12:58:29Z

But when i hit the url https://my-ip:4443/ i am not seeing any ui. I am seeing ERR_CONNECTION_REFUSED in browser.

As stated in the application setup portion of the readme, you must do the initial setup on port 3000. OP also failed to properly set the kasm_port, as noted in the container readme. Since @drumtechphoto claims the same or similar issue, and they didnt provide a docker run, i will assume neither read/followed the readme.

github-actions · 2024-12-09T12:58:55Z

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

drumtechphoto · 2024-12-12T03:24:54Z

But when i hit the url https://my-ip:4443/ i am not seeing any ui. I am seeing ERR_CONNECTION_REFUSED in browser.

As stated in the application setup portion of the readme, you must do the initial setup on port 3000. OP also failed to properly set the kasm_port, as noted in the container readme. Since @drumtechphoto claims the same or similar issue, and they didnt provide a docker run, i will assume neither read/followed the readme.

Thank you for the reply. My apologies for not posting my docker compose, I over-sighted it when replying to add-in on this for support. I was also using my dockerhub creds (optional) / currently no longer using them.

The docker compose I pulled via running another container, had to remove all unneeded extra info >>
"docker run --rm -v /var/run/docker.sock:/var/run/docker.sock red5d/docker-autocompose kasm"

I reverted back to version tag "1.16.0-ls44" for now. If need be, I can create a new/separate kasm container with the "latest" tag and report back.

services:
kasm:
container_name: kasm
cpuset: 8,9,10,11,12,13,14,15,24,25,26,27,28,29,30,31,
environment:
- NVIDIA_DRIVER_CAPABILITIES=all
#- DOCKER_HUB_USERNAME=
- UMASK=022
- NVIDIA_VISIBLE_DEVICES=all
- KASM_PORT=6333
#- DOCKER_HUB_PASSWORD=
- TZ=America/New_York
image: lscr.io/linuxserver/kasm:1.16.0-ls44
networks:
- bridge
ports:
- 4533:3000/tcp
- 6333:6333/tcp
privileged: true
security_opt:
- label=disable
volumes:
- /mnt/user/:/Shares_Unraid:rw
- /mnt/user/media/kevan/backup/family/docker/kasm/profiles:/profiles:rw
- /mnt/cache/appdata/kasm/opt:/opt:rw
networks:
bridge:
external: true`

freemanpt · 2024-12-28T00:04:59Z

Hi, I am having the same behaviour but I changed the initial 3000 port while using my pi5, since I have a container already running there, still cant get access to webUI for the initial setup. my docker compose is as follows:

services:
kasm:
image: lscr.io/linuxserver/kasm:latest
container_name: kasm
privileged: true
security_opt:
- apparmor:rootlesskit #optional
environment:
- KASM_PORT=443
- DOCKER_HUB_USERNAME= #optional
- DOCKER_HUB_PASSWORD= #optional
volumes:
- /opt/Kasm/data:/opt
- /opt/Kasm/profiles:/profiles #optional
ports:
- 3003:3003
- 443:443
restart: unless-stopped

drizuid · 2024-12-28T01:00:42Z

3003:3003

you changed the container side, you should only be changing the host side

freemanpt · 2024-12-28T12:14:27Z

3003:3003

you changed the container side, you should only be changing the host side

That's the thing I have a container already running on that internal 3000 port, which is another kasm only with libreoffice, I have to really use 3000 then huh ?

j0nnymoe · 2024-12-28T12:15:33Z

Internal ports can be the same as they all have their own address on the docker network.

freemanpt · 2024-12-28T13:01:07Z

Internal ports can be the same as they all have their own address on the docker network.

Thanks for the help got that confused. All working now.

LinuxServer-CI moved this to Issues in Issue & PR Tracker Dec 3, 2024

LinuxServer-CI added this to Issue & PR Tracker Dec 3, 2024

drizuid added the invalid This doesn't seem right label Dec 9, 2024

LinuxServer-CI moved this from Issues to Insufficient Info in Issue & PR Tracker Dec 9, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to access the webui #77

Unable to access the webui #77

sendev1 commented Dec 3, 2024 •

edited

Loading

github-actions bot commented Dec 3, 2024

drumtechphoto commented Dec 4, 2024

drizuid commented Dec 9, 2024 •

edited

Loading

github-actions bot commented Dec 9, 2024

drumtechphoto commented Dec 12, 2024

freemanpt commented Dec 28, 2024

drizuid commented Dec 28, 2024

freemanpt commented Dec 28, 2024

j0nnymoe commented Dec 28, 2024

freemanpt commented Dec 28, 2024

Unable to access the webui #77

Unable to access the webui #77

Comments

sendev1 commented Dec 3, 2024 • edited Loading

Is there an existing issue for this?

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

CPU architecture

Docker creation

Container logs

github-actions bot commented Dec 3, 2024

drumtechphoto commented Dec 4, 2024

drizuid commented Dec 9, 2024 • edited Loading

github-actions bot commented Dec 9, 2024

drumtechphoto commented Dec 12, 2024

freemanpt commented Dec 28, 2024

drizuid commented Dec 28, 2024

freemanpt commented Dec 28, 2024

j0nnymoe commented Dec 28, 2024

freemanpt commented Dec 28, 2024

sendev1 commented Dec 3, 2024 •

edited

Loading

drizuid commented Dec 9, 2024 •

edited

Loading