mirror of
https://github.com/games-on-whales/unraid-plugin.git
synced 2026-10-15 21:12:04 +00:00
[GH-ISSUE #33] Port 8080 is already in use and gpu is not shown in settings #11
Labels
No labels
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/unraid-plugin#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
Also when trying to run gow i get this in the settings menu:
@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.
@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:
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:
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:
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
@Joly0 commented on GitHub (May 21, 2026):
When deploying/installing wolf i even can see this:
So for whatever reason it still tries to bind to port 8080 although its used and configured differently
@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
@Joly0 commented on GitHub (May 21, 2026):
Alsoooo, when stopping the stack, for some reason, "WolfPulseAudio" as a running container stays left behind:
@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.