In this article:

    Applicable to

    • Twingate Component: Client
    • Platform: Linux
    • OS: Ubuntu 24.04

    Overview

    Twingate Linux Client notifier will call out auth.sock errors on Ubuntu 24.04, and fully fail to authenticate or connect to Resources. This primarily happens after an upgrade from older versions of Ubuntu to 24.04 but has also been observed more rarely in fresh installs, but also on network changes during sleep/wake cycle. Putting a Linux device to sleep on network1, and waking the device on network2, can cause these errors to bubble up and for the client to fail.

    Cause

    NetworkManager attempts to call for network deletions from D-Bus, which fail and results in an inability to create a network path for the Client. This also results in our notifier service elevating the auth.sock failures.

    These will be seen with:

    twingate-notifier status
    17:43:07 [ERROR] Error: auth.sock socket is not found

    Workaround

    We can workaround this by switching the renderer from NetworkManager to networkd for the sdwan0 interface.

    If your system includes the file:

    /etc/netplan/01-network-manager-all.yaml

    ...edit with sudo and adjust the contents to look like:

    network:
      version: 2
      # renderer: NetworkManager
      renderer: networkd

    Then issue a sudo netplan apply, which should allow the Twingate notifier to function.

    If it does not automatically prompt for auth, issue a twingate stop and twingate start.

    If your system only includes files like /etc/netplan/90-NM-GUID-VALUE.yaml then you need to identify the file under /etc/netplan which includes config for sdwan0 and change the renderer: value to networkdin the proper placement.

    These files will have a scheme like /etc/netplan/90-NM-GUID-VALUE.yaml

    Use sudo to edit the file and update the contents to look like this:

    network:
      version: 2
      renderer: networkd
      nm-devices:
        NM-d0ba585b-5270-40e5-b289-21c88252c725:
          # renderer: networkd
          networkmanager:
            uuid: "d0ba585b-5270-40e5-b289-21c88252c725"
            name: "sdwan0"
            passthrough:
              connection.type: "tun"
              connection.autoconnect: "false"
              connection.autoconnect-priority: "999"
              connection.interface-name: "sdwan0"
              tun._: ""
              ipv4.address1: "100.96.0.2/32"
              ipv4.dns: "100.95.0.251;100.95.0.252;100.95.0.253;100.95.0.254;"
              ipv4.dns-priority: "-1"
              ipv4.dns-search: "~.;"
              ipv4.method: "manual"
              ipv6.addr-gen-mode: "default"
              ipv6.method: "auto"
              proxy._: ""

    Then issue a sudo netplan apply which may give a warning, but it is safe to ignore and you should then be prompted by the notifier to authenticate into your tenant.

    If you do not get an authentication prompt after issuing the sudo netplan apply you may need to restart.