It seems that all images in the website cannot load correctly. The images url in console is not responding. error message: “NetworkFirst.js:120 Uncaught (in promise) no-response: no-response :: [{“url”:“http://127.0.0.1:4200/uploads/default/original/1X/d5bf693dd40d319b3ee59f6d36a65adce12a8c31.png”}] at w._handle (http://localhost:4200/assets/workbox-84721eb2561c34fa8575f276d429c215/workbox-strategies.prod.js:1:5420)” Please help me thanks! By the way, what is the storage way of discourse? How can it use the S3 storage? I figured it is using local storage in this case. Thank you very much!!! :grinning: [image]

Hey Alex, welcome. Thanks for trying out Discourse. These errors look a bit weird. Did you deploy them using our standard installation guide? discourse/docs/INSTALL.md at main · discourse/discourse · GitHub Or are you running this locally?

I run it on local In fact, when I installed it, I realized that it couldn’t display the the logo of discourse. But at first the other pictures were temporarily displayed, but later on they were not. :smiling_face_with_tear:And I cannot load the emoji [image]

The problem with the emojis and the logo waa reported here too Install Discourse on Ubuntu or Debian for Development - #607

Hi Alex, As nat asked, is that a standard install or something else like a development install?

There are a bunch of things that can go wrong on a development installation. You can use S3 as described at Configure an S3 compatible object storage provider for uploads. It’s likely very difficult to configure for development.

I install it on windows using WSL, following the stardard installation and I noticed that I use Ubuntu 22.04.2 LTS not ubuntu 18. Is it the possible reason？

If you installed according to the following link [image] Install Discourse for development using Docker Developer Guides Developing using Docker Since Discourse runs in Docker, you should be able to run Discourse directly from your source directory using a Discourse development container. white_check_mark Pros: No need to install any system dependencies, no configuration needed at all for setting up a development environment quickly. x Cons: Will be slightly slower than the native dev environment on Ubuntu, and much slower than a native install on MacOS. See also Developing Discourse using a Dev Container … I guess you can execute the following command in the project root directory every time you reopen the virtual machine： # In one terminal: d/rails s # And in a separate terminal d/ember-cli

Cannot load any images “Uncaught (in promise) no-response: no-response”

Product Support Self-hosting

darkpixlz (Pyx ) August 1, 2023, 7:10pm 10

I’m having the same issue on 22.04 on WSL.

Topic		Replies	Views
Images are not being populated in discourse Self-hosting	1	860	August 4, 2021
My images are not working Self-hosting uploads , s3	15	1174	April 24, 2023
New Discourse Installation: Emoji's not appearing Self-hosting	1	609	January 14, 2019
No images, js files, css files, or fonts after install Self-hosting	3	979	October 19, 2018
Problems with Patreon Login, Force HTTPS, and S3 CDN (three) Issues Self-hosting unsupported-install	12	2359	January 6, 2023

Cannot load any images “Uncaught (in promise) no-response: no-response”

Related topics