Measurements not showing

[SuperDarius-git]

Hi

All my measurements are gone or not showing anymore. When clicking on the Measurements button on the web version, it just has a small waiting icon, and then it is gone and nothing shows. Not sure how to troubleshoot this. Can't find any errors in logs.

Please help
Thank you,
Darius

[rolandgeider]

oh no, you are really unlucky. Do you see any errors in the browser's developer console?

[SuperDarius-git]

Yeah, it looks like I might just be unlucky! Haha... ANyway... this is what the console says:

TypeError: document.adoptedStyleSheets.filter is not a function index.js:1081:51
[SpaceLlama] Content script initialized content.js:460:11
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=19&limit=20&offset=20” measurement
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=17&limit=20&offset=20” measurement
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=17&limit=20&offset=20” measurement
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=19&limit=20&offset=20” measurement
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=17&limit=20&offset=20” measurement
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=19&limit=20&offset=20” measurement
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=17&limit=20&offset=20” measurement
Uncaught TypeError: can't access property "length", e.data is undefined
    VQ MeasurementCategoryOverview.tsx:58
    React 16
    batchCalls notifyManager.js:56
    n notifyManager.js:8
    a notifyManager.js:30
    a notifyManager.js:29
    r notifyManager.js:11
    a notifyManager.js:28
    setTimeout handler*Fye timeoutManager.js:62
    a notifyManager.js:27
    batch notifyManager.js:45
    #i query.js:385
    fetch query.js:300
    #d queryObserver.js:179
    onSubscribe queryObserver.js:52
    subscribe subscribable.js:9
    mve useBaseQuery.js:58
    React 36
    B scheduler.production.js:151
    Zst scheduler.production.js:200
    Zst scheduler.production.js:340
    elt index.js:4
    React 3
main.js:488:47773
    VQ MeasurementCategoryOverview.tsx:58
    React 16
    batchCalls notifyManager.js:56
    n notifyManager.js:8
    a notifyManager.js:30
    forEach self-hosted:157
    a notifyManager.js:29
    r notifyManager.js:11
    a notifyManager.js:28
    (Async: setTimeout handler)
    Fye timeoutManager.js:62
    a notifyManager.js:27
    batch notifyManager.js:45
    #i query.js:385
    fetch query.js:300
    InterpretGeneratorResume self-hosted:1332
    AsyncFunctionThrow self-hosted:804
    (Async: async)
    #d queryObserver.js:179
    onSubscribe queryObserver.js:52
    subscribe subscribable.js:9
    mve useBaseQuery.js:58
    React 36
    B scheduler.production.js:151
    (Async: EventHandlerNonNull)
    Zst scheduler.production.js:200
    Zst scheduler.production.js:340
    elt index.js:4
    React 3
Blocked loading mixed active content “http://fit.super.org.za/api/v2/measurement/?category=19&limit=20&offset=20” measurement

[rolandgeider]

mhhh, "mixed content". I'm guessing the application uses https?

edit: ah, wait, it's the pagination. If you open https://fit.super.org.za/api/v2/measurement the link in "next" is probably http right? I've seen this before, it's a setting somewhere, I'll need to check

[SuperDarius-git]

Yes, the link is http in "next".

[rolandgeider]

so this seems to be an nginx header configuration problem, which are... fun... I'll write you later again when I know what to ask for 😄

As a workaround I have added to the measurements a max pagination size of 999 so this shouldn't happen so early (and will be faster since there's fewer requests).

[SuperDarius-git]

Thank you... Now I'm not sure how it works. Must I test the workaround yet or wait?

[rolandgeider]

it's not available yet

[SuperDarius-git]

Ok, I thought so, just wanted to make sure... but thank you so much

[rolandgeider]

can you post the nginx.conf you are using? (or send it to me on discord if you prefer)

The original http / https mismatch issue: wger-project/flutter#911 (comment)

[SuperDarius-git]

You're gonna have to tell me how to do that, please? Is this now the configuration of my NGINX Proxy Manager which points to wger container? Is it the whole NPM configuration or just that files pointing to wger? Or will you help me on Discord, please?

[rolandgeider]

I don't quite remember how your setup looked like? Did you have an nginx in your network as well as ours in the docker compose or did you route everything through yours? If you are also using ours, I'd need our config (It's the ningx.conf in the config folder)

[SuperDarius-git]

Here is the wger NGINX container's config:

pstream wger {
    server web:8000;
}

server {

    listen 80;

    location / {
        proxy_pass http://wger;
        proxy_set_header Host $http_host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_redirect off;
    }

    location /static/ {
        alias /wger/static/;
    }

    location /media/ {
        alias /wger/media/;
    }

    # Increase max body size to allow for video uploads
    client_max_body_size 1000M;
}

I am not sure how to get the config for the main NGINX container.

Thank you
Darius

[rolandgeider]

mhh, that looks all correct. PR #139 might be the solution for this.

BTW, the workaround with the page size is in the latest image, if you pull them you should at least be able to access everything again.

[SuperDarius-git]

Hi @rolandgeider - I fixed my NGINX Proxy Manager container and can now test the new wger container, but it still does not load the Measurements, unfortunately.