search

linuxserver / docker-wireshark

GNU General Public License v3.0
106 stars 12 forks source link

Login Failed For Display 0 #2

Closed typkrft closed 1 year ago

typkrft commented 4 years ago

linuxserver.io

When logging in with abc/abc I recieve an error message that states login failed for display 0. Oddly when I log in with a console session I see a screen share that would be from a VM I have in another guacamole instance that I have. The other guacamole share is on a different subnet in a separate docker created network and the port exposed isn't 3000. I'm wondering if maybe I could log into wireshark from my existing guacamole instance, if so what would the settings be, or if I can separate them some how. Or maybe that has nothing to do with the login failed issue.

Expected Behavior

I would expect to see the application window after logging in.

Current Behavior

Login Failed for Display 0

Steps to Reproduce

  1. sudo docker-compose -f /volume1/docker/wireshark.yml up -d --force-recreate
  2. xxx.xxx.x.xxx:3000 3.login to default session with user:abc pass:abc 4.error message described -> return to login manager

Environment

OS: Synology DSM CPU architecture: x86_64 How docker service was installed:

Command used to create docker container (run/create/compose/screenshot)

version: "3.7"
services:
  wireshark:
    image: ghcr.io/linuxserver/wireshark
    container_name: wireshark
    cap_add:
      - NET_ADMIN
    network_mode: host
    environment:
      - PUID=$PUID
      - PGID=$PGID
      - TZ=$TZ
    volumes:
      - $DOCKERDIR/wireshark:/config
    restart: unless-stopped

Docker logs

[20201105-15:03:50] [DEBUG] Security layer: requested 3, selected 1

ssl_tls_accept: TLS connection accepted

colorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp)

[20201105-15:03:50] [INFO ] connected client computer name: Guacamole RDP

postBeta2ColorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp 0xca02 15bpp 0xca03 16bpp 0xca04 24bpp)

highColorDepth 0x0010 (0x0004 4bpp 0x0008 8bpp 0x000f 15bpp 0x0010 16 bpp 0x0018 24bpp)

supportedColorDepths 0x0007 (0x0001 24bpp 0x0002 16bpp 0x0004 15bpp 0x0008 32bpp)

earlyCapabilityFlags 0x0421 (0x0002 want32)

got client client connection type 0x00000006

xrstarting sesman in foreground...

sesman config:

    ListenAddress:            127.0.0.1

    ListenPort:               3350

    EnableUserWindowManager:  1

    UserWindowManager:        startwm.sh

    DefaultWindowManager:     startwm.sh

    AuthFilePath:             disabled

Xvnc parameters:

    Parameter 00                   Xvnc

    Parameter 01                   -bs

    Parameter 02                   -nolisten

    Parameter 03                   tcp

    Parameter 04                   -localhost

    Parameter 05                   -dpi

    Parameter 06                   96

X11rdp parameters:

XOrg parameters:

    Parameter 00                   /usr/lib/xorg/Xorg

    Parameter 01                   -config

    Parameter 02                   xrdp/xorg.conf

    Parameter 03                   -noreset

    Parameter 04                   -nolisten

    Parameter 05                   tcp

    Parameter 06                   -logfile

    Parameter 07                   .xorgxrdp.%s.log

security configuration:

    AllowRootLogin:       1

    MaxLoginRetry:        4

    AlwaysGroupCheck:     0

    No TSUsersGroup defined

    No TSAdminsGroup defined

session configuration:

    MaxSessions:                 50

    X11DisplayOffset:            10

    KillDisconnected:            0

    IdleTimeLimit:               0

    DisconnectedTimeLimit:       0

    Policy:       0

SessionVariables parameters:

  Parameter 00                   PULSE_SCRIPT=/etc/xrdp/pulse/default.pa

[20201105-14:40:40] [DEBUG] libscp initialized

[20201105-14:40:40] [INFO ] starting xrdp-sesman with pid 323

[20201105-14:40:40] [INFO ] listening to port 3350 on 127.0.0.1

[20201105-14:41:01] [INFO ] A connection received from ::1 port 42325

pam_authenticate failed: System error

[20201105-14:41:02] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:41:20] [INFO ] A connection received from ::1 port 42486

pam_authenticate failed: System error

[20201105-14:41:21] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:41:22] [INFO ] A connection received from ::1 port 42488

pam_authenticate failed: System error

[20201105-14:41:22] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:41:27] [INFO ] A connection received from ::1 port 42519

pam_authenticate failed: System error

[20201105-14:41:28] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:41:30] [INFO ] A connection received from ::1 port 42540

pam_authenticate failed: System error

[20201105-14:41:31] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:43:50] [INFO ] A connection received from ::1 port 43809

pam_authenticate failed: System error

[20201105-14:43:51] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:44:09] [INFO ] A connection received from ::1 port 44024

pam_authenticate failed: System error

[20201105-14:44:10] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:44:28] [INFO ] A connection received from ::1 port 44189

pam_authenticate failed: System error

[20201105-14:44:28] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:55:26] [INFO ] A connection received from ::1 port 50194

pam_authenticate failed: System error

[20201105-14:55:27] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:55:39] [INFO ] A connection received from ::1 port 50321

pam_authenticate failed: System error

[20201105-14:55:40] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:55:43] [INFO ] A connection received from ::1 port 50337

pam_authenticate failed: System error

[20201105-14:55:43] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:55:52] [INFO ] A connection received from ::1 port 50471

pam_authenticate failed: System error

[20201105-14:55:53] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:55:55] [INFO ] A connection received from ::1 port 50495

pam_authenticate failed: System error

[20201105-14:55:56] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

[20201105-14:56:05] [INFO ] A connection received from ::1 port 50523

pam_authenticate failed: System error

[20201105-14:56:05] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)

guacd[627]: ERROR:  User is not responding.

guacd[627]: INFO:   User "@2c1e5a58-0996-4b6a-a557-c64b81c9617c" disconnected (0 users remain)

guacd[627]: INFO:   Last user of connection "$ba2cb9b4-39a5-4d96-8a29-32d823b3899d" disconnected

guacd[627]: INFO:   Internal RDP client disconnected

guacd[336]: INFO:   Connection "$ba2cb9b4-39a5-4d96-8a29-32d823b3899d" removed.
github-actions[bot] commented 4 years ago

Thanks for opening your first issue here! Be sure to follow the issue template!

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Bracciata commented 3 years ago

I too am having this issue!

repudi8or commented 3 years ago

me too

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

djarbz commented 2 years ago

I am having this issue as well.

thelamer commented 2 years ago

Must be a port conflict with synology when running host networking. I am rebasing this image to alpine, but you might also want to try passing the CUSTOM_PORT env variable for the gui app if 3000 is conflicting host level.

There is nothing that can be done if host level 3389 (rdp) or 4822 (guac) are occupied though.

IE: -e CUSTOM_PORT=30022 then access the webui on 30022.

Honestly I mostly use this container in K8s deployments (just generally to look into docker networks) so I can troubleshoot stuff, the host level networking stuff is only there as an option and it is functional on a standard Linux box.

More app info here: https://github.com/linuxserver/gclient#options

typkrft commented 2 years ago

I don't know if this issue still occurs, I could try later. But I am in the middle of migrating my containers and data to another host on another network. I assume there was a conflict somewhere, but I couldn't figure it out. My networking and docker configuration hasn't changed though on the network I originally had the issue with. 

❯❯❯ nc -zcw10 192.168.1.129 1-4822
Connection to 192.168.1.129 port 22 [tcp/ssh] succeeded!
Connection to 192.168.1.129 port 80 [tcp/http] succeeded!
Connection to 192.168.1.129 port 81 [tcp/hosts2-ns] succeeded!
Connection to 192.168.1.129 port 111 [tcp/sunrpc] succeeded!
Connection to 192.168.1.129 port 139 [tcp/netbios-ssn] succeeded!
Connection to 192.168.1.129 port 443 [tcp/https] succeeded!
Connection to 192.168.1.129 port 444 [tcp/snpp] succeeded!
Connection to 192.168.1.129 port 445 [tcp/microsoft-ds] succeeded!
Connection to 192.168.1.129 port 548 [tcp/afpovertcp] succeeded!
Connection to 192.168.1.129 port 873 [tcp/rsync] succeeded!
Connection to 192.168.1.129 port 892 [tcp/*] succeeded!
Connection to 192.168.1.129 port 2049 [tcp/nfsd] succeeded!
Connection to 192.168.1.129 port 2227 [tcp/di-msg] succeeded!
Connection to 192.168.1.129 port 3261 [tcp/winshadow] succeeded!
Connection to 192.168.1.129 port 3262 [tcp/necp] succeeded!
Connection to 192.168.1.129 port 3263 [tcp/ecolor-imager] succeeded!
Connection to 192.168.1.129 port 3264 [tcp/ccmail] succeeded!
Connection to 192.168.1.129 port 3265 [tcp/altav-tunnel] succeeded!
Connection to 192.168.1.129 port 4306 [tcp/*] succeeded!
Connection to 192.168.1.129 port 4357 [tcp/qsnet-cond] succeeded!
Connection to 192.168.1.129 port 4433 [tcp/*] succeeded!
github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.