Results 1 to 3 of 3

Thread: New WSL2 issue with win-kex

  1. #1
    Join Date

    New WSL2 issue with win-kex


    I've been using Kali trough wsl2 on Windows 10 for a while, but since a few days, I cannot connect anymore.
    I've done some research, but can't find anything that works.

    I've uninstalled kali completely and reinstalled it from the store.
    Then I installed win-kex exactly like described in the tutorial, and afterwards, whenever I type "kex" in the terminal, now I receive this:
    Error connecting to the KeX server.
    Please try "kex start" to start the service.
    If the server fails to start, please try "kex kill" or restart your WSL2 session and try again.
    I launch the command from home path ("~"), but not working.

    Inside the folder ~/.vnc, there is a log file:
    Wed Mar 17 18:28:40 2021
     vncext:      VNC extension running!
     vncext:      Listening for VNC connections on all interface(s), port 5901
     vncext:      created VNC server for screen 0
    3NI3X0 New Xtigervnc server 'DESKTOP-PE9SK8H.localdomain:1 (sylvain)' on port 5901 for display :1.
    3NI3X0 Use xtigervncviewer -SecurityTypes VeNCrypt,TLSVnc -passwd /home/sylvain/.vnc/passwd DESKTOP-PE9SK8H.localdomain:1 to connect to the VNC server.
     ComparingUpdateTracker: 0 pixels in / 0 pixels out
     ComparingUpdateTracker: (1:-nan ratio)
    /usr/bin/startxfce4: X server already running on display :1
    xrdb: Connection refused
    xrdb: Can't open display ':1'
    Unable to init server: Could not connect: Connection refused
    xfce4-session: Cannot open display: .
    Type 'xfce4-session --help' for usage.
    If I start the server "manually", by typing
    vncserver :1 -SecurityTypes VncAuth --PasswordFile ~/.vnc/passwd
    the server is start, but then, when I start kex, the VNC Client is launched but displays this message:
    "No matching security types"

    Please can you help me ?

  2. #2
    Join Date
    Similar situation. I had win-kex running fine on WSL2.
    After a new install of win10 I installed kali and then win-kex by exact same process but now i keep getting VNC errors.
    When i run kex --win or kex --s the tigervnc client on windows says unable to connect, connection refused.
    In the kali terminal i get unable to run tigervnc pl see log. The log has a lot of xkbcomp errors saying could not resolve keysym and a "failed to create listner"
    Buy kex --esm works fine, I get an RDP windows with the kali desktop.
    Can't do the seamless or other vnc options.

  3. #3
    Join Date
    The Netherlands
    Hey there, Ive come across the same issue when i just installed win-kex on WSL 2.

    Ive run the first boot config of the server with TigerVNC.

    After that TigerVNC refused to connect.

    I found a way to still be able to connect to the VNC server.

    It seems that -win and kex share a different config file

    When you first run kex --win it asks for a password. the same happens when you run kex without --win.

    If you, after you close the session, try to connect with only kex, it would spawn a session without problems.

    I hope this helps as a temporal solution to bypass this bug.
    We go to school, but school means free time, confusing isn't it?

Similar Threads

  1. Wsl2 Kali Linux Kex no mic device
    By Daniel_kaly in forum Kali Linux General Questions
    Replies: 0
    Last Post: 2021-04-17, 23:14
  2. Various WSL2 issues.
    By aaronouthier in forum TroubleShooting Archive
    Replies: 13
    Last Post: 2021-01-17, 09:52
  3. Windows 10 - WSL2 - kex
    By AzO666 in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2020-11-11, 21:39
  4. Kali WSL2 / KEX change from XFCE to KDE
    By AGZ in forum General Archive
    Replies: 1
    Last Post: 2020-09-17, 08:45
  5. Problem running Kex on wsl2
    By mwoodpatrick in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2020-09-15, 13:40

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts