games-on-whales/wolfmanager

Fork 0

mirror of https://github.com/games-on-whales/wolfmanager.git synced 2026-10-15 21:12:13 +00:00

[GH-ISSUE #1] User Management UI #3

New issue

Closed

opened 2026-10-15 13:01:20 +00:00 by bsakaguchi · 9 comments

bsakaguchi commented

2026-10-15 13:01:20 +00:00

Owner

Originally created by @salty2011 on GitHub (Jan 15, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolfmanager/issues/1

Originally assigned to: @salty2011 on GitHub.

Wolf does not have a mechanism for user management but it does allow management of pair clients and the state folder that points to.

as a starting point this UI will do the following

When creating a user a state folder will be created
associate Steam API keys to that use for importing owned games
pairing a client will set its state folder to that user

Originally created by @salty2011 on GitHub (Jan 15, 2025). Original GitHub issue: https://github.com/games-on-whales/wolfmanager/issues/1 Originally assigned to: @salty2011 on GitHub. Wolf does not have a mechanism for user management but it does allow management of pair clients and the state folder that points to. as a starting point this UI will do the following - When creating a user a state folder will be created - associate Steam API keys to that use for importing owned games - pairing a client will set its state folder to that user

bsakaguchi

2026-10-15 13:01:20 +00:00

closed this issue
added the
enhancement
label

bsakaguchi commented

2026-10-15 13:01:21 +00:00

Author

Owner

@Bladestar2105 commented on GitHub (Feb 23, 2025):

I try to pair a client and the logs are showing the pending pairing but in the webui I cannot finish it, it shows nothing.

[2025-02-23T10:12:30.417Z] DEBUG: Fetching pending pair requests
[2025-02-23T10:12:30.418Z] INFO: Successfully fetched pending pair requests {"count":1}
[2025-02-23T10:12:30.414Z] INFO: Successfully fetched pending pair requests {"count":1}

@Bladestar2105 commented on GitHub (Feb 23, 2025): I try to pair a client and the logs are showing the pending pairing but in the webui I cannot finish it, it shows nothing. > [2025-02-23T10:12:30.417Z] DEBUG: Fetching pending pair requests [2025-02-23T10:12:30.418Z] INFO: Successfully fetched pending pair requests {"count":1} [2025-02-23T10:12:30.414Z] INFO: Successfully fetched pending pair requests {"count":1} <img width="260" alt="Image" src="https://github.com/user-attachments/assets/83e1818d-05a8-4dc2-9422-c44252c2a6de" />

bsakaguchi commented

2026-10-15 13:01:21 +00:00

Author

Owner

@salty2011 commented on GitHub (Feb 23, 2025):

Hey,

Just to confirm, in the "select client ip" drop down you see no pending request after clicking the refresh button next to the drop down?

@salty2011 commented on GitHub (Feb 23, 2025): Hey, Just to confirm, in the "select client ip" drop down you see no pending request after clicking the refresh button next to the drop down?

bsakaguchi commented

2026-10-15 13:01:22 +00:00

Author

Owner

@Bladestar2105 commented on GitHub (Feb 23, 2025):

Yeah that's right.

@Bladestar2105 commented on GitHub (Feb 23, 2025): Yeah that's right.

bsakaguchi commented

2026-10-15 13:01:22 +00:00

Author

Owner

@Bladestar2105 commented on GitHub (Feb 23, 2025):

In Browser Dev Tools I see this (pair_secret changed):

[Warning] Some pairing requests were invalid or duplicated: – {original: [{pair_secret: "0CD2D114XXXXXXXX", client_ip: "192.168.178.107"}], filtered: []} (index-D7Yh5hlc.js, line 1)

@Bladestar2105 commented on GitHub (Feb 23, 2025): In Browser Dev Tools I see this (pair_secret changed): > [Warning] Some pairing requests were invalid or duplicated: – {original: [{pair_secret: "0CD2D114XXXXXXXX", client_ip: "192.168.178.107"}], filtered: []} (index-D7Yh5hlc.js, line 1)

bsakaguchi commented

2026-10-15 13:01:22 +00:00

Author

Owner

@salty2011 commented on GitHub (Feb 23, 2025):

Ahh, are you on the latest version of Wolf?

I know in an earlier release there was a bug where pair requests would linger resulting in duplicate or stale requests. If you selected a request out an invalid pin and it fail this would invalidate all pending requests.

Submitting the pair request again would then work correctly.

However I believe that was fixed in newer version of wolf itself and interesting the issue I described seem to fix for wolf manager

@salty2011 commented on GitHub (Feb 23, 2025): Ahh, are you on the latest version of Wolf? I know in an earlier release there was a bug where pair requests would linger resulting in duplicate or stale requests. If you selected a request out an invalid pin and it fail this would invalidate all pending requests. Submitting the pair request again would then work correctly. However I believe that was fixed in newer version of wolf itself and interesting the issue I described seem to fix for wolf manager

bsakaguchi commented

2026-10-15 13:01:22 +00:00

Author

Owner

@Bladestar2105 commented on GitHub (Feb 23, 2025):

My wolf instance is up2date, just verified.
In wolf logs I get this many times. Also tried to pair with another client, same problem:

09:55:10.013811659 WARN | Received HTTPS request from a client which wasn't previously paired.
09:55:13.143021172 INFO | Insert pin at http://192.168.178.104:47989/pin/#1E7A7B0586E40EEC
09:55:15.058954649 WARN | Received HTTPS request from a client which wasn't previously paired.
09:55:18.153420356 INFO | Insert pin at http://192.168.178.104:47989/pin/#3CD16FE9F409B0F2
09:55:20.110172788 WARN | Received HTTPS request from a client which wasn't previously paired.
09:55:23.161380149 INFO | Insert pin at http://192.168.178.104:47989/pin/#9AA7D98F9847911D
09:55:25.160769747 WARN | Received HTTPS request from a client which wasn't previously paired.

@Bladestar2105 commented on GitHub (Feb 23, 2025): My wolf instance is up2date, just verified. In wolf logs I get this many times. Also tried to pair with another client, same problem: > 09:55:10.013811659 WARN | Received HTTPS request from a client which wasn't previously paired. 09:55:13.143021172 INFO | Insert pin at http://192.168.178.104:47989/pin/#1E7A7B0586E40EEC 09:55:15.058954649 WARN | Received HTTPS request from a client which wasn't previously paired. 09:55:18.153420356 INFO | Insert pin at http://192.168.178.104:47989/pin/#3CD16FE9F409B0F2 09:55:20.110172788 WARN | Received HTTPS request from a client which wasn't previously paired. 09:55:23.161380149 INFO | Insert pin at http://192.168.178.104:47989/pin/#9AA7D98F9847911D 09:55:25.160769747 WARN | Received HTTPS request from a client which wasn't previously paired.

bsakaguchi commented

2026-10-15 13:01:23 +00:00

Author

Owner

@salty2011 commented on GitHub (Feb 26, 2025):

Ok noted, I'll spin up an older version of WolfManager and looking into further.

Was about to migrate the code for this into the rebased version of wolf manager anyway

@salty2011 commented on GitHub (Feb 26, 2025): Ok noted, I'll spin up an older version of WolfManager and looking into further. Was about to migrate the code for this into the rebased version of wolf manager anyway

bsakaguchi commented

2026-10-15 13:01:23 +00:00

Author

Owner

@Bladestar2105 commented on GitHub (Mar 23, 2025):

Any chance of getting an package update for testing?

@Bladestar2105 commented on GitHub (Mar 23, 2025): Any chance of getting an package update for testing?

bsakaguchi commented

2026-10-15 13:01:23 +00:00

Author

Owner

@salty2011 commented on GitHub (Mar 23, 2025):

Soon, the code rebase is almost complete.

Just need to

Migrate pairing
Library display and artwork fetching.
repackage to container.

If your on the Discord channel there is a WolfManager thread user development channel where I posed a length update

Sorry about the delay. With the rebase the user management system has been greatly enhanced and this has taken longer than expected

@salty2011 commented on GitHub (Mar 23, 2025): Soon, the code rebase is almost complete. Just need to - Migrate pairing - Library display and artwork fetching. - repackage to container. If your on the Discord channel there is a WolfManager thread user development channel where I posed a length update Sorry about the delay. With the rebase the user management system has been greatly enhanced and this has taken longer than expected

bsakaguchi referenced this issue

2026-10-15 13:01:48 +00:00

[PR #9] [MERGED] Refactor: WolfManager UI Overhaul and Documentation Update #36