mirror of
https://github.com/games-on-whales/wolfmanager.git
synced 2026-10-15 21:12:13 +00:00
[GH-ISSUE #6] Blank site #4
Labels
No labels
a11y
bug
enhancement
enhancement
good first issue
pull-request
question
refactor
security
shadcn
tech-debt
ui
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolfmanager#4
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 @Bladestar2105 on GitHub (Feb 16, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolfmanager/issues/6
I deployed a container with wolfmanager and exposed the socket from wolf so it is accessible. But when opening the site it is blank.
In the logs I see this:
@Nicolas-Casto commented on GitHub (Feb 16, 2025):
Can you check the devtools console in your browser if there are any react errors? Also are you trying to access it from the same computer with localhost or from a separate pc?
@Bladestar2105 commented on GitHub (Feb 16, 2025):
I use another computer in the same network.
This is logged in Safari (tried in Edge too, same problem).
@Nicolas-Casto commented on GitHub (Feb 16, 2025):
The crypto api in browsers requires a secure context, that being https or localhost. I have a fork with https but it also has unfinished login functionality. I'll try to create a pr for basic ssl support
@salty2011 commented on GitHub (Feb 16, 2025):
Looking at the above error it's failing to load the config. That should be wolf-manager.json
Just to clarify
As for security, yeah the current version here lacks that. It sorta grew from testing out CursorAI and ideas to what we have now. I'm in the midst of rebasing the entire code base into some standard frameworks to make development easier and easier for other contributors
In the rebased version I've
Not negating your issue. I'll merge the client pairing branch in today. That should fix a number of issues, but it still the version before i rebased
@Bladestar2105 commented on GitHub (Feb 17, 2025):
I use the Container you offer in stable branch.
@salty2011 commented on GitHub (Feb 17, 2025):
Thanks @Bladestar2105 , apologies ive been working heavily from the Client Pairing branch where aside adding the the client pairing / unpairing I did resolve a few issues.
Just commit the changes and merging into stable atm. New image should build shortly
@salty2011 commented on GitHub (Feb 17, 2025):
@Nicolas-Casto / @Bladestar2105
Just an fyi I am currently in the midst of re-basing the code to use Shadcn, nextjs and next-auth etc. Doing this so that its easier to maintain and for other to contribute in the long run.
Will have another branch/pr soonish with this rebase. But currently migrating the part of the code I have into this new version.
Apologies, honestly didn't expect this project to get much attention :)
@salty2011 commented on GitHub (Feb 17, 2025):
New image image based the Client Pairing branch is now available, if you do
docker pull ghcr.io/games-on-whales/wolfmanager:stable
should for update to the latest version.
Could you give this a go and attache wolf manger log file it creates.
Also if you can provide the docker compose / docker run you are using so I can replicate here
@Bladestar2105 commented on GitHub (Feb 17, 2025):
See the logs attached.
And this is my compose-file:
_wolf-manager_logs.txt
@salty2011 commented on GitHub (Feb 17, 2025):
@Bladestar2105, so based on the wolf logs looks like your now using the new image I just pushed out are you still getting a blank page if you goto http://localhost:9971 ?
and like @Nicolas-Casto mention if you bring up the console in the Dev tools are there any errors listed?
@Bladestar2105 commented on GitHub (Feb 17, 2025):
Yeah this is right, the logs are after the update.
The error is the same with http.
@salty2011 commented on GitHub (Feb 17, 2025):
hmm ok, im not able to reproduce that error in Firefox, Chrome or Brave. i also cleared my config to mimic first start as well.
Also not seeing that error in the console logs either.
Just wondering if there is some sort of extension in the browser at plan. Have you tried in a Private window with now extensions loaded?
@Nicolas-Casto were you also getting this issue as well?
@salty2011 commented on GitHub (Feb 17, 2025):
@Nicolas-Casto , now I follow what you saying in regards to the crypto api, just pushed fix and tested. Also checked your repo to add in the login page. In the rebase I've used next-Auth to do this along bcrypt to encrypt the credentials along with the Steam ID/API keys, along with this have added access control to pages so that you can have admin users and standard users.. Sorry didn't mean redo your work here. Once I upload the rebase welcome the the PR to improve further.
Have added notes to the ReadMe page regarding the rebase so that others are aware > again apologies
@Bladestar2105 try pulling the latest image and test,
apologies when I tested here locally was using localhost as the address not the IP, repeated using IP locally and another desktop and was able to reproduce.
@Bladestar2105 commented on GitHub (Feb 17, 2025):
Ok now the site loads properly 😄
@salty2011 commented on GitHub (Feb 17, 2025):
Excellent, shall take note and ensure rebase also include this