After an update, I always get a blank white page.

[FasteryXD]

So, I'm currently having a problem where, after an update, I always get a blank white page on Gramps Web.
This doesn't mean Gramps Web is broken or anything, because after a hard reload (Ctrl + F5), everything works perfectly again.
As additional information, I'm using the Nginx Proxy Manager (NPM).
My problem is that I personally don't have any issues with (Ctrl + F5), but my relatives probably don't.
Is this a problem with NPM, a problem with Gramps, or a problem with the browser?
It always works perfectly in incognito mode.
If anyone has any suggestions, I would be very grateful.

Thank you in advance.

[DavidMStraub]

I also sometimes get this but haven't been able to identify the root cause.

What would be helpful:

After an update, open browser dev tools and go to the network tab, check the requests that are made in the initial page load. Check for errors in the console.

[FasteryXD]

So, after the update, I had the white screen again, and this is what was displayed in the console:

• Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

• Laden fehlgeschlagen für das Modul mit der Quelle "https://gramps.de/o7XrE7RW.js".

Does this help us in any way?

[DavidMStraub]

Are you using latest-devel? It contains a fix that should help. (But probably only AFTER the update, as the bug is in the service worker.)

[FasteryXD]

So I'm using the following tag: ghcr.io/gramps-project/grampsweb:latest
And I'm still having the problem, but I'm already on the latest version, aren't I?

Gramps 6.0.8
Gramps Web API 3.12.2
Gramps Web Frontend 26.5.0
Gramps QL 0.4.0
Sifts 1.3.1
locale: en
multi-tree: false
task queue: true
OCR: true
chat: false

[PaulJ00]

Hi,
I sometimes get the same error. It happened in the Opera browser on Windows and in Chrome on iOS.
I was able to solve it by deleting all cookies.
If this happen aging i will expect this with Dev-Mode

[FasteryXD]

In my case, the error in Chrome still occurred even after the update.

[FasteryXD]

Well, with yesterday's version, which was updated today via Watchtower, I had exactly the same "problem" (in Chrome).

[DavidMStraub]

Yes, I can confirm it, but I'm at a loss explaining it.

[PaulJ00]

@FasteryXD are you using "jc21/nginx-proxy-manager:latest" as reverse proxy too?

[PaulJ00]

Getting this warning after the error described above:

The resource https://---.de/config.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloaded intentionally.

[DavidMStraub]

Oh, that's a helpful hint, thanks! Will Investigate.

[PaulJ00]

I’m encountering additional errors now:

Failed to load resource: net::ERR_NAME_NOT_RESOLVEDUnderstand this error
(index):1 ServiceWorker registered.

manifest.json:1  Failed to load resource: net::ERR_NAME_NOT_RESOLVEDUnderstand this error

5The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.Understand this warning

manifest.json:1  GET https://---.de/manifest.json net::ERR_NAME_NOT_RESOLVEDUnderstand this error

manifest.json:1  GET https://---.de/manifest.json net::ERR_NAME_NOT_RESOLVEDUnderstand this error

manifest.json:1  GET https://---.de/manifest.json net::ERR_NAME_NOT_RESOLVEDUnderstand this error

[PaulJ00]

GET https://---/DEqT1gwP.js net::ERR_NAME_NOT_RESOLVED

[PaulJ00]

I found that this error is caused by a VPN.

This may still be relevant, because the result is still a white screen and it might have the same underlying cause.

[DavidMStraub]

I hope this problem is finally resolved in v26.5.3. However, since the problem is caused by the previous service worker, what you should see is:

• previous updates: blank page, can only recover with hard reload
• v26.5.3 update: blank page, can recover with normal reload (F5)
• future updates: no blank page

[YTKme]

Hello,

I want to follow up on this discussion a bit (let me know if I should open a new discussion). I am also experiencing a blank page currently running version 26.6.1. It used to be if I do a hard reload it works, but now it doesn't. I only notice this after the recent update.

Note: I am running this with a reverse proxy (HAProxy on pfSense). It worked fine in the previous few version, but it doesn't load at all on the latest version.