scheme (#59) #72

New issue

Closed

opened 2026-10-15 12:55:23 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 12:55:23 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/games-on-whales/unraid-plugin/pull/64
Author: @JBailes
Created: 7/19/2026
Status: ✅ Merged
Merged: 7/19/2026
Merged by: @JBailes

Base: main ← Head: worktree-fix-wolfden-socket-59

📝 Commits (1)

a512f22 Give Wolf Den's socket path the unix:// scheme so it stops dialing localhost:80 (#59)

📊 Changes

1 file changed (+8 additions, -2 deletions)

View changed files

📝 scripts/deploy.sh (+8 -2)

📄 Description

Fixes #59.

Problem

On Unraid, the Wolf Den web management interface loads only the template frames — all dynamic data is empty and no changes can be saved. Its logs repeat:

The Wolf API SSE encountered an HttpRequestException exception: Connection refused (localhost:80)
System.Net.Http.HttpRequestException: Connection refused (localhost:80)

Root cause

Wolf Den's .NET client (GamesOnWhales.Wolf.Net.Bindings) only dials the Wolf UNIX socket when WOLF_SOCKET_PATH carries a unix:// scheme:

if (socketPath.StartsWith("unix://")) { /* connect over the UDS */ }
else { /* plain HttpClient against BaseUrl = http://localhost/ */ }

The plugin set a bare path (WOLF_SOCKET_PATH=/tmp/sockets/wolf.sock), so the bindings took the else branch and dialed the default HTTP base address http://localhost:80 over TCP — where nothing is listening — producing the repeated Connection refused (localhost:80). (The localhost:80 in the message is the request URI authority, not the real endpoint.)

Fix

Add the unix:// scheme to WOLF_SOCKET_PATH in both compose variants (NVIDIA and standard) so the bindings connect over the socket that Wolf already exposes on the shared wolf-socket volume. The env var is only set on the wolf-den service; Wolf itself keeps deriving its own socket path from XDG_RUNTIME_DIR, so nothing else changes.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/games-on-whales/unraid-plugin/pull/64 **Author:** [@JBailes](https://github.com/JBailes) **Created:** 7/19/2026 **Status:** ✅ Merged **Merged:** 7/19/2026 **Merged by:** [@JBailes](https://github.com/JBailes) **Base:** `main` ← **Head:** `worktree-fix-wolfden-socket-59` --- ### 📝 Commits (1) - [`a512f22`](https://github.com/games-on-whales/unraid-plugin/commit/a512f223cbb817fcc5d4726cd084752ed5bfb174) Give Wolf Den's socket path the unix:// scheme so it stops dialing localhost:80 (#59) ### 📊 Changes **1 file changed** (+8 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `scripts/deploy.sh` (+8 -2) </details> ### 📄 Description Fixes #59. ## Problem On Unraid, the Wolf Den web management interface loads only the template frames — all dynamic data is empty and no changes can be saved. Its logs repeat: ``` The Wolf API SSE encountered an HttpRequestException exception: Connection refused (localhost:80) System.Net.Http.HttpRequestException: Connection refused (localhost:80) ``` ## Root cause Wolf Den's .NET client (`GamesOnWhales.Wolf.Net.Bindings`) only dials the Wolf UNIX socket when `WOLF_SOCKET_PATH` carries a `unix://` scheme: ```csharp if (socketPath.StartsWith("unix://")) { /* connect over the UDS */ } else { /* plain HttpClient against BaseUrl = http://localhost/ */ } ``` The plugin set a bare path (`WOLF_SOCKET_PATH=/tmp/sockets/wolf.sock`), so the bindings took the `else` branch and dialed the default HTTP base address `http://localhost:80` over TCP — where nothing is listening — producing the repeated `Connection refused (localhost:80)`. (The `localhost:80` in the message is the request URI authority, not the real endpoint.) ## Fix Add the `unix://` scheme to `WOLF_SOCKET_PATH` in both compose variants (NVIDIA and standard) so the bindings connect over the socket that Wolf already exposes on the shared `wolf-socket` volume. The env var is only set on the `wolf-den` service; Wolf itself keeps deriving its own socket path from `XDG_RUNTIME_DIR`, so nothing else changes. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 12:55:23 +00:00