-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant get Wger to work properly ? Is it my configuration ? , permissions? … :( #45
Comments
Hi, is anyone able to help, I'd love to get wger up and running. |
Hi, I’d really appreciate any help on this, I’d love to be able to use Wger.. @rolandgeider any suggestions ? |
Still, hoping to use Wger, but continue to suffer from the same issue reported earlier.. if anyone is able to try the Docker compose I shared earlier, just to see and share what their experience is, that would help.. |
Hi! Answering here to keep the other issue focused on the CSRF stuff. The one port where you say that you can access the site but has no static files is probably the "raw" django application, the other one is nginx. However besides the CSRF origins both should work or at least allow you to log in, I don't think we do any JS there. The way the docker compose is configured, it shouldn't allow you to acces the ports within its network so that you should only be able to access the reverse proxy where everything is served (or can you access e.g. postgres port 5432?) |
Attached is a screenshot of my QNAP Container Station app, where containers are created etc. The chain icons on the bottom two represent resolvable links/urls that are made available for access, and as you can see i have one for wger server and wger ngnix. (See IP/port mapping below too)
|
I have gotten the same original error and identified a quick fix, but still experience some problems like favicons etc not loading. While I don't know what truly causes this on the inside, the bug can be partially sovled, by not linking specific folders to "media" and "static" directories, but to instead use docker volumes. When mounting a normal host folder there seems to errupt some kind of permissions error, which prevents the web server container from saving its static and media content in the respective directories. All in all I think the whole docker part of wger needs a permission overhaul, not only to fix issues like these, but also to allow for rootless container operation. |
That was originally the reason why I used volumes, specially on windows this was a real pain. On the other hand, this might be a bug/misconfiguration that the volumes simply hide |
Quite a few of the other container I run require me to provide a user and group ID within the environment variable in order to handle permissions issues when accessing mapped volumes. Here it is in speedtester one..
And an extract of Paperless-ngx.
|
Can confirm this is a problem with network shares but I dont see any errors. Tried setting the user id/gid but still didnt save the files. NGINX config works fine being on a share but static/media files only work locally on VM/docker host as volumes. |
Hi @rheaalleen For some reason I’m able to access wger today, no My two recurring issues are with CSRF verification failures, and which URL/port to use.. When it comes to the latter, and looking at my mapped volumes (network shares) my docker compose (in the original post above), uses the same share in both, but I noticed wger specifies two slightly different locations within each of it’s container.. It is likely nothing but sharing it just in case.. Under web (wger_server) I have this.. volumes: and under ngnix (wger_ngnix) it’s this.. volumes: I only see images/graphics when I access wger via the ngnix port, not the web one.. Are you able to share you docker compose ? |
I think my main problem is that NGINX gets Permission denied on reading the files in the network share 2023/03/04 11:08:20 [error] 35#35: *15 open() "/wger/static/CACHE/css/output.1a831572686b.css" failed (13: Permission denied) The files are there after checking but NGINX cant open them. Inside the container the IDs are the same like they are for the share and even with o+r permissions (-rwxrwxr--).
|
I'll comment here as well, as I've spent a couple hours fighting the lack of /static... I was using Ansible instead of docker-compose directly, so my setting was: This found its way to the container as Now docker entrypoint does
and thus I always got empty static folder. Hopefully this helps someone... |
Thanks @anarion80 for sharing that.. I must admit, I don’t quite understand what you’ve done (that’s more about my lack of understanding, rather than your explanation:-) ), but I’d love someone to jump in and share how this should be handled/translated in the Docker_compose.yml ? Not sure how this plays into it, but if i recall correctly, in order to get the full CSRF_Verification error messages, you had to have Also just an FYI, I tried a docker_compose with no mapped volumes for |
Yes, my comment is maybe more related to how Ansible uses variables, but looking at your original post, you have: But looking at your later posts seems like you can in fact see the images but only when accessing nginx, so maybe that is rather related to permissions or something else.. |
Thanks @anarion80 , I’m not entirely sure of the cause, i share your view too, in that it feels permissions related , but when all is said and done, it really shouldn’t be this complicated to get working. Untill I know it’s a rock solid product (for me) I can’t commit all my fitness data to it :( |
Just wanted to add my 2c. Thanks for the app. |
I just created an environment section under nginx and added PGID, PUID parameters now everything works great all images show including favicon. |
Hi @nncrypted , any chance you could share your full docker compose so i could test it out too ? |
services: nginx: db: cache: volumes: networks: |
Hi,
no matter what I try, I can’t seem to get the Wger Docker instance to work correctly.. I’ve created 3 persistent local locations to store config, media and static content , but they don’t seem to get picked up. If someone is able to review / or better yet try my config (or a close approximation of it,) that would help me a lot..
my Docker compose is..
Here’s my nginx.conf too
Which makes it look like this..
The text was updated successfully, but these errors were encountered: