404 errors (assets) on Subfolder installation

Support
21

Here it is the full file.

en.app.yml.gz (2.1 KB)

UPD: that forum is working on 1.9.0, so I am not sure about latest, just in case…

1 Like
22

ahh, I see. well, I just regret updating it :frowning:

23

@pfaffman @Falco @Ivan_Rapekas I have noticed one change during the installation process i.e. previously during the compression of assets I could see this process twice, once with /public/assets... and then again with /public/community/assets... and the installation took time as it compiled twice. Now, I don’t see this message and i get only something like below and then the installation is completed.

3729805.649853851 Compressing: application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js
uglifyjs '/var/www/discourse/public/assets/_application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js' -p relative -m -c -o '/var/www/discourse/public/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js' --source-map-root '/assets' --source-map '/var/www/discourse/public/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js.map' --source-map-url '/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js.map'
gzip -f -c -9 /var/www/discourse/public/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js > /var/www/discourse/public/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js.gz

brotli -f --quality=11 /var/www/discourse/public/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js --output=/var/www/discourse/public/assets/application-177e5c04adfc0e63a82cc75f84460d3c59337339a5a12efa3bf1013e18f465f1.js.br

probably the below command does not work with the latest release or something.

- rm -fr public/assets
- sudo -E -u discourse bundle exec rake assets:precompile

but it does not work with or without these commands. However, this command did work for me previously.

1 Like
24

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 again and delete a line by line code of Nginx configuration file and found this to be the main culprit for /community folder. Rebuild, restore, boom!

Thank you @pfaffman @Falco @Ivan_Rapekas

4 Likes
25

Uh, Yeah. See also Install ngx_pagespeed - #2 by Falco.

Let’s hope not. :slight_smile:

2 Likes
26

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.