Hey there, while hunting down some weird outages that we see on our forums, I was also checking the nginx logs within the app container. I haven’t checked them for a while now so I can’t say if those are there for longer but I see errors regarding missing Javascript files in a directory that doesn’…

Workbox appears to have to do with caching, I think. How recently did you upgrade? There could be some bug around it, but I think we might need more information

I’ve only updated the day before I posted. To my reasearch workbox seems to have to do with PWA and be looked for with Chrome/Chromium browsers. What more information do you need?

We’re still seeing this 9 months later and still I can’t find much about it. Not sure if just no one looks at their nginx error logs or just don’t care about it. Anyone with an idea what’s going on and if this might cause issues or not? I’m hunting down some 520/429 issues that don’t seem to direc…

[Bild] Helmi: Not sure if just no one looks at their nginx error logs or just don’t care about it. Given that workbox was dropped as a dependency 2 months ago and this is not a problem that affects sites up to date, I recommend updating your site.

I’m on 3.3.0beta2 - I don’t think there’s anything I can update to.

You are not alone @helmi I had issues moving from 3.2.5 to 3.3.0 (tons of 502, 429, etc) and had to downgrade back to 3.2.5. Recently tried re-upgrading to 3.3.1 hoping things would be better. They were… in a way. Just a plethora of 502 for all users. Decided to go all in and trust the test-passe…

It seems like our installation also has this issue - since updating from 3.2.x to 3.3.x we’ve been having waves of 502 when posting, latest posts not updating and similar issues. It seems like every x time (hours? unsure) there’s a background script that errors out(?) and creates these issues. edi…

We get a similar wave of errors every few hours: 2025/05/19 16:48:10 [error] 63#63: *1738520 open() "/var/www/discourse/public/assets/workbox-77b0e3e0dd4773bcd6c7e74f302f7c69/workbox-core.prod.js" failed (2: No such file or directory), client: unix:, server: _, request: "GET /forum/assets/workbox-7…

[Bild] Falco: Given that workbox was dropped as a dependency 2 months ago [Bild] MichaIng: We get a similar wave of errors every few hours: What version are you running?

3.5.0.beta5-dev, which does not serve these files anymore, nor is an up-to-date frontend asking for them. As said, either outdated cache/frontend (which should normally not happen with the dynamic HTML documents) or bots, client problem in any case.

Fehlendes workbox-Verzeichnis im public/javascript?

Unterstützung Installation

helmi (Helmi) 24. Juni 2024 um 07:10 6

Ich bin auf 3.3.0beta2 – ich glaube nicht, dass es etwas gibt, auf das ich aktualisieren kann.

Thema		Antworten	Aufrufe
Upgrade error for v3.2.0.beta3 Support two-container	1	551	13. November 2023
Error message for Google Chrome Service Workers Bug	10	1332	14. Juni 2023
Discourse Development: Failed to register/update a ServiceWorker Support	6	1331	11. Juni 2018
uMatrix browser add-on causes white pages when visiting Discourse instances Support	14	1600	6. April 2021
SetupWizard, blank screen, JS Error "`virtual-dom" Support	3	1529	27. Juli 2017

Fehlendes workbox-Verzeichnis im public/javascript?

Verwandte Themen