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

installation
1

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
image2540×1018 302 KB

1 Like
2

Hey Alex, welcome. Thanks for trying out Discourse.

These errors look a bit weird. Did you deploy them using our standard installation guide? https://github.com/discourse/discourse/blob/main/docs/INSTALL.md

Or are you running this locally?

3 Likes
5

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
image729×210 11.8 KB

1 Like
6

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

1 Like
7

Hi Alex,

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

1 Like
8

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.

1 Like
9

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？

1 Like
10

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

1 Like
11

If you installed according to the following link

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