Checking all of the boxes on Safe mode does not help. I removed all app.yml plugins except docker manager. Any thoughts on how to troubleshoot this? I don’t see anything obvious in the re-build app log either.

If you followed Configure an S3 compatible object storage provider for uploads did you include the bit that uploads assets to s3?

Are you saying that the site is stuck at the loading? Can you check your browser’s console and copy-paste or screenshot what you see? (click right on the page → inspect → click on Console tab)

This is what I’m seeing in the console: Uncaught ReferenceError: define is not defined at apply-details.js:1:1 composer-presence-display.js:1 Uncaught ReferenceError: define is not defined at composer-presence-display.js:1:1 console.js:1 Uncaught ReferenceError: define is not defined at…

Is it an upgrade from the admin panel? If so, can you try rebuilding Discourse from the command line and see it it helps? It can happen sometimes; you need to rebuild the container fully. :thinking:

I’ve done several: ./launcher rebuild app tries from command line Even re-booted my server. I tried a rebuild app with all of the plugins commented out or the app.yml (except docker-manager). The only odd thing I’m seeing is occasionally, redis shows up in the log when rebuilding the app as port…

I also see this in the rebuild log: warning Resolution field “unset-value@2.0.1” is incompatible with requested version “unset-value@^1.0.0”

Maybe these warnings too: warning "@discourse/lint-configs > eslint-plugin-ember > ember-eslint-parser@0.3.8" has unmet peer dependency "@typescript-eslint/parser@^6.15.0". warning " > @glint/environment-ember-loose@1.4.0" has unmet peer dependency "@glimmer/component@^1.1.2". warning " > discourse…

Those warnings can be ignored. Don’t hesitate to paste the entire log here if we miss something. Also, are you behind Cloudflare or similar?

It’s on a Digital Ocean droplet with new images on S3 bucket.

[imagen] Jeff Vienneau: Uncaught ReferenceError: define is not defined at apply-details.js:1:1 What causes errors like this ^^^?

I’m not sure. I would say what we see is the consequence of an underlying issue (like a fatal error at early stage or something did not load properly). Hopefully someone can provide other insights on this. :thinking: Is it possible to share your Discourse URL (or by PM if you prefer)?

Puntos de carga de colores porque los assets no se subieron

Soporte Instalación

pfaffman (Jay Pfaffman) 13 Mayo, 2024 09:17 15

Si seguiste Configurar un proveedor de almacenamiento de objetos compatible con S3 para cargas, ¿incluiste la parte que carga los activos a S3?

Tema		Respuestas	Vistas
Troubleshooting S3 Uploads: Site hangs after rebuild, JS assets fail to load with net::ERR_... on both R2 and GCS Support	3	123	29 Septiembre 2025
Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL Support	43	6435	22 Abril 2020
Error Upgrading from 3.4.0.beta4-dev to 3.5.0.beta1 Support	3	161	5 Abril 2025
Unable to setup S3 bucket Self-hosting uploads , s3	11	334	12 Enero 2025
AI Plugin Build Error - 'bundle exec rake db:migrate' failed Self-hosting ai	10	1101	13 Diciembre 2023

Puntos de carga de colores porque los assets no se subieron

Temas relacionados