It’s been one month exactly since discourse has been giving me 404 error on assets files (css/js etc) after I did “git pull” and then “rebuild” on approximately May 15th as its was asking me upgrade via command line on the automatic upgrade page. And then now today after several days, I have tried …

Alright, folks… after like several hours and days and lol… The issue was with the pagespeed configuration code i.e. location ~* \.(jpg|jpeg|png|gif|ico|css|js|pdf)$ { expires 7d; add_header Cache-Control "public, no-transform"; } I had to rebuild again and ag…

I destroyed the container and then rebuild it with the stable release, the problem is with the assets i.e. CSS or javascript files which are not being found. This error happened probably in the update of May. Is there a way I install the previous versions?

Destroying the container doesn’t help, your database was migrated, and as I’ve already said above there’s no way to migrate back. If you didn’t take a backup prior to upgrade you’re stuck at tests-passed until beta or stable reaches the same level.

If you have a backup from then you might be able to do a new build and put the Verdun you want in the version line. You might try entering the container and doing a rake assets:precompile My current subfolder solution is with traefik as the reverse proxy. I offer that installation as a service i…

Currently, I am trying a fresh installation first, as you can see in the first post even the registration page is not working fine. I have tried assets:precompile but its same no effect. Is there a way I can try to install an older version of discourse docker?

[image] john3: Is there a way I can try to install an older version of discourse docker? Unless you want to use this forum for a week or two and then delete it, you really, really, really don’t want to do that. My guess is that you missed some tiny step somewhere that’s causing the problem, …

Yes, it’s not working, that is why I am stuck at 404 errors, javascript files are not being loaded and giving 404 error as shown in the first post.

this is my external config for the Nginx reverse proxy. location /community { pagespeed off; rewrite /(.*) /$1 break; proxy_pass http://127.0.0.1:25654/; proxy_read_timeout 90; proxy_redirect http://127.0.0.1:25654/ https://www.domain.com…

But the yml file you have above doesn’t look like the one in Subfolder support with Docker .

That’s because that config file didn’t work in the past, so the one I am using now was suggested by @neil here and it worked in the past. Currently, I also tried the config file uploaded there, but that didn’t work too.

Erreurs 404 (assets) sur une installation en sous-dossier

Soutien

Falco (Falco) Juin 27, 2019, 6:43 10

A complete fresh install following Serve Discourse from a subfolder (path prefix) instead of a subdomain is not working?

Sujet		Réponses	Vues
Serve Discourse from a subfolder (path prefix) instead of a subdomain Self-Hosting docker , subfolder , how-to , advanced-setup	30	43219	Avril 14, 2026
Blank Page After installing Discourse on Subfolder Self-hosting	9	1535	Septembre 5, 2018
Setup wizard emoji wrong in subfolder install Bug subfolder	39	3223	Juillet 25, 2018
Upgrade doesn't work when installed with subfolder Bug	6	1544	Juin 6, 2017
Discourse Assets Missing Self-hosting unsupported-install	17	2297	Février 22, 2020

Erreurs 404 (assets) sur une installation en sous-dossier

Sujets connexes