[BUG] Socket proxy update breaks Dockhand logging

Is there an existing issue for this?

I have searched the existing issues

Current Behavior

Recently all machines using linuxserver docker proxy updated, to 3.4.4 and I lost logging access withing my Dockhand container.

Rolled back to 3.4.1-r0-ls87 and all is again well.

Hopefully others smarter than I have shared a similar.

Expected Behavior

Full logging functionality on apps connected via socket-proxy

Steps To Reproduce

Start Dockhand.
Select container logs
Keeps trying to connect. Fails.

Environment

- OS: Trixie
- How docker service was installed: Using Docker 29.7.2 from docker repo.

Docker creation

services:
  socket-proxy:
    image: lscr.io/linuxserver/socket-proxy:latest
    container_name: socket-proxy
    restart: unless-stopped
    networks:
      - socket_proxy
    environment:
      ## Granted by Default
      - EVENTS=1 # Container event monitoring
      - PING=1 # Health checks
      - VERSION=1 # Docker version info

      ## Revoked by Default
      # Security critical
      - AUTH=0 # Authentication APIs, Portainer per Copilot
      - SECRETS=0 # Docker secrets access
      - POST=1 # Required for create/update operations

      # Not always needed
      - ALLOW_START=1 # Dockge, Dockpeek,
      - ALLOW_STOP=1  # Dockge, Dockpeek,
      - ALLOW_RESTARTS=1  # Dockge, Dockpeek,
      - BUILD=0 # optional
      - COMMIT=0 # Container commits
      - CONFIGS=0 # Docker configs
      - CONTAINERS=1 # Container management
      - DF=1 # size data per dockhand
      - DISABLE_IPV6=1 # optional
      - DISTRIBUTION=0 # Distribution APIs
      - EXEC=1 # Execute commands in containers
      - IMAGES=1 # Image building
      - INFO=1 # Docker system info
      - NETWORKS=1 # Network management
      - NODES=0 # Node management
      - PLUGINS=0 # Plugin management
      - PROXY_READ_TIMEOUT=240 #optional
      - SERVICES=0 # Service management (Swarm), Portainer
      - SESSION=0 # Session management
      - SWARM=0 #  Docker Swarm features
      - SYSTEM=1 # System-wide operations, not for arcane
      - TASKS=0 # Task management (Swarm), Portainer
      - VOLUMES=1 # Volume management
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    read_only: true
    tmpfs:
      - /run

networks:
  socket_proxy:
    external: true

Container logs

NA. Rolled back to 3.4.2

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

The changelog has a hint about logs.

Thank you. `ALLOW_LOGS=1` works. But for me this is a breaking change. Notification would be nice. This one snuck in on me while trying to troubleshoot a different issue, and finding UI logs missing.

…

On 8/22/2026 4:57 PM, Simen - notifications at github.com wrote: *Roxedus* left a comment (linuxserver/docker-socket-proxy#53) <#53 (comment)> The changelog has a hint about logs. — Reply to this email directly, view it on GitHub <#53?email_source=notifications&email_token=AC66FHI633DKCRZ2WKUGMB35LICL3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZYGI2TMMBWGQZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5382560642>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC66FHOP5X2LHCYQ52PQHTT5LICL3AVCNFSNUABFKJSXA33TNF2G64TZHM3TQMZTGMZTMOBRHNEXG43VMU5TKMRSGM4DSNRSGQ3KC5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AC66FHO3Q57ZWSZCHAQHWH35LICL3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZYGI2TMMBWGQZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AC66FHMAH5RGY24ZVYU7VG35LICL3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZYGI2TMMBWGQZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

The changelog is our notification. This also makes it to the releasenote on github.

Got it.

The changelog is our notification. This also makes it to the releasenote on github.

Yeah no this is still should not have been a patch release..

It's not a patch release because our versioning is not semantic (semver). The version contains HAProxy (upstream) version plus Alpine's release version plus our build tag.

https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time#semver-info

Navigation Menu

Repository navigation

[BUG] Socket proxy update breaks Dockhand logging #53

Is there an existing issue for this?

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

Docker creation

Container logs

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG] Socket proxy update breaks Dockhand logging #53

Description

Is there an existing issue for this?

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

Docker creation

Container logs

Activity

github-actions commented on Aug 22, 2026

Roxedus commented on Aug 22, 2026

truthsword commented on Aug 22, 2026

Roxedus commented on Aug 22, 2026

truthsword commented on Aug 22, 2026

Blacks-Army commented on Sep 2, 2026

aptalca commented on Sep 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions