[GH-ISSUE #33] Port 8080 is already in use and gpu is not shown in settings #11

Closed
opened 2026-10-15 12:54:32 +00:00 by bsakaguchi · 6 comments
Owner

Originally created by @Joly0 on GitHub (May 21, 2026).
Original GitHub issue: https://github.com/games-on-whales/unraid-plugin/issues/33

So, first to the settings, i can see this:

Image I tried to run "reconfigure" but that didnt change anything. Not sure if or what my gpu now is, i do not have any option now to select it, compared to previously.

Also when trying to run gow i get this in the settings menu:

Image Makes sense, because port 8080 is a widely used defualt port for many applications and imo there should be a way to configure this (or let gow find a random free port and use that)
Originally created by @Joly0 on GitHub (May 21, 2026). Original GitHub issue: https://github.com/games-on-whales/unraid-plugin/issues/33 So, first to the settings, i can see this: <img width="814" height="502" alt="Image" src="https://github.com/user-attachments/assets/5bc523af-fcce-4b28-9d9b-d9056b5f4f78" /> I tried to run "reconfigure" but that didnt change anything. Not sure if or what my gpu now is, i do not have any option now to select it, compared to previously. Also when trying to run gow i get this in the settings menu: <img width="801" height="585" alt="Image" src="https://github.com/user-attachments/assets/a6006c00-0653-41f1-b90f-6ceb4beb0b7c" /> Makes sense, because port 8080 is a widely used defualt port for many applications and imo there should be a way to configure this (or let gow find a random free port and use that)
Author
Owner

@JBailes commented on GitHub (May 21, 2026):

Fixed in #34 and released as 2026.05.21a: Wolf Den now has a configurable host port, dashboard links/deploy output use that port, and Reconfigure now opens the setup form even when an existing Wolf stack is present.

<!-- gh-comment-id:4507546851 --> @JBailes commented on GitHub (May 21, 2026): Fixed in #34 and released as 2026.05.21a: Wolf Den now has a configurable host port, dashboard links/deploy output use that port, and Reconfigure now opens the setup form even when an existing Wolf stack is present.
Author
Owner

@Joly0 commented on GitHub (May 21, 2026):

@JBailes Not rly. I stopped the stack, containers were removed. I reconfigured (also gpu now does show up, which is good) and when i start the stack i can see this:

Image

So looks correct for me, but when i try to access any of these urls shown here for den, my firefox (or even chrome browser) dont show anytihng, page is not available. Checking under docker page shows why:

Image

So although port 8080 is already in use, the den container still uses it somehow, instead of respecting the port i configured. When i try to go to port 8080 instead of my configured port, i still see no page available, and the problem is the same as i have previously posted in another issue:

Waiting for Wolf socket: /tmp/sockets/wolf.sock Socket file exists, testing connectivity...
Socket is available and responsive
Starting Server
SQL logic error
no such table: __EFMigrationsHistory
info: WolfLeash.Components.Classes.CompatibilityToolsService[0]
      Ensured compatibility tools directory /etc/wolf/compatibilitytools.d/fedora43
info: WolfLeash.Components.Classes.CompatibilityToolsService[0]
      Ensured compatibility tools directory /etc/wolf/compatibilitytools.d/ubuntu
warn: Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository[50]
      Using an in-memory repository. Keys will not be persisted to storage.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[59]
      Neither user profile nor HKLM registry available. Using an ephemeral key repository. Protected data will be unavailable when application exits.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
      No XML encryptor configured. Key {19909dbb-0123-4519-a3b7-0e8b10f04589} may be persisted to storage in unencrypted form.
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://[::]:8080
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /app

Not to sound mean or anything, but you are vibe coding this and not really testing what you are shipping, no? I mean, in the past 2 days i have found so many obvious bugs which you have "fixed" in a short amount of time and there seems to be no validation or testing at all

<!-- gh-comment-id:4507624441 --> @Joly0 commented on GitHub (May 21, 2026): @JBailes Not rly. I stopped the stack, containers were removed. I reconfigured (also gpu now does show up, which is good) and when i start the stack i can see this: <img width="773" height="563" alt="Image" src="https://github.com/user-attachments/assets/3a486b2d-0621-4280-805d-101cfd4b95da" /> So looks correct for me, but when i try to access any of these urls shown here for den, my firefox (or even chrome browser) dont show anytihng, page is not available. Checking under docker page shows why: <img width="956" height="286" alt="Image" src="https://github.com/user-attachments/assets/4b306711-0823-4b84-8a4c-ece4da746c5a" /> So although port 8080 is already in use, the den container still uses it somehow, instead of respecting the port i configured. When i try to go to port 8080 instead of my configured port, i still see no page available, and the problem is the same as i have previously posted in another issue: ``` Waiting for Wolf socket: /tmp/sockets/wolf.sock Socket file exists, testing connectivity... Socket is available and responsive Starting Server SQL logic error no such table: __EFMigrationsHistory info: WolfLeash.Components.Classes.CompatibilityToolsService[0] Ensured compatibility tools directory /etc/wolf/compatibilitytools.d/fedora43 info: WolfLeash.Components.Classes.CompatibilityToolsService[0] Ensured compatibility tools directory /etc/wolf/compatibilitytools.d/ubuntu warn: Microsoft.AspNetCore.DataProtection.Repositories.EphemeralXmlRepository[50] Using an in-memory repository. Keys will not be persisted to storage. warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[59] Neither user profile nor HKLM registry available. Using an ephemeral key repository. Protected data will be unavailable when application exits. warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35] No XML encryptor configured. Key {19909dbb-0123-4519-a3b7-0e8b10f04589} may be persisted to storage in unencrypted form. info: Microsoft.Hosting.Lifetime[14] Now listening on: http://[::]:8080 info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down. info: Microsoft.Hosting.Lifetime[0] Hosting environment: Production info: Microsoft.Hosting.Lifetime[0] Content root path: /app ``` Not to sound mean or anything, but you are vibe coding this and not really testing what you are shipping, no? I mean, in the past 2 days i have found so many obvious bugs which you have "fixed" in a short amount of time and there seems to be no validation or testing at all
Author
Owner

@Joly0 commented on GitHub (May 21, 2026):

When deploying/installing wolf i even can see this:

Image

So for whatever reason it still tries to bind to port 8080 although its used and configured differently

<!-- gh-comment-id:4507648603 --> @Joly0 commented on GitHub (May 21, 2026): When deploying/installing wolf i even can see this: <img width="760" height="504" alt="Image" src="https://github.com/user-attachments/assets/a231074d-8e69-4aa8-8915-39a4a37119b7" /> So for whatever reason it still tries to bind to port 8080 although its used and configured differently
Author
Owner

@Joly0 commented on GitHub (May 21, 2026):

Also, just as a tip, before you claim a bug is fixed and closing any issues, test it yourself and verify it works or better let the person who opened the issue confirm the bug is fixed

<!-- gh-comment-id:4507659749 --> @Joly0 commented on GitHub (May 21, 2026): Also, just as a tip, before you claim a bug is fixed and closing any issues, test it yourself and verify it works or better let the person who opened the issue confirm the bug is fixed
Author
Owner

@Joly0 commented on GitHub (May 21, 2026):

Alsoooo, when stopping the stack, for some reason, "WolfPulseAudio" as a running container stays left behind:

Image Image
<!-- gh-comment-id:4507704720 --> @Joly0 commented on GitHub (May 21, 2026): Alsoooo, when stopping the stack, for some reason, "WolfPulseAudio" as a running container stays left behind: <img width="785" height="580" alt="Image" src="https://github.com/user-attachments/assets/8a274d71-801d-4751-b205-db6a325a7b8b" /> <img width="893" height="97" alt="Image" src="https://github.com/user-attachments/assets/4bca344a-b4e4-4f74-a3f9-f7924e0f9052" />
Author
Owner

@JBailes commented on GitHub (May 21, 2026):

WolfPulseAudio is a known issue, @ABeltramo would be the one to ping on this as it is significantly over and above what I can do in this plugin.

The code itself was tested and worked on my machine, I'm not seeing the same UI in the pictures you are presenting as the UI I saw.

<!-- gh-comment-id:4507773660 --> @JBailes commented on GitHub (May 21, 2026): WolfPulseAudio is a known issue, @ABeltramo would be the one to ping on this as it is significantly over and above what I can do in this plugin. The code itself was tested and worked on my machine, I'm not seeing the same UI in the pictures you are presenting as the UI I saw.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
games-on-whales/unraid-plugin#11
No description provided.