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 to reinstall again and it’s still the same even though it’s been days. My app.yml file content is given below. ## ## After making changes to this file, you MUST rebuild for any changes ## to take effect in your live Discourse instance: ## ## /var/discourse/launcher rebuild app ## ## Make sure to obey YAML syntax! You can use this site to help check: ## http://www.yamllint.com/ ## this is the all-in-one, standalone Discourse Docker container template # You may add rate limiting by uncommenting the web.ratelimited template. # Out of the box it allows 12 reqs a second per ip, and 100 per minute per ip # This is configurable by amending the params in this file templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" expose: - "25654:80" # - "80:80" # - "2222:22" params: db_default_text_search_config: "pg_catalog.english" version: tests-passed env: LANG: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en UNICORN_WORKERS: 2 DISCOURSE_DEVELOPER_EMAILS: '' DISCOURSE_HOSTNAME: '' DISCOURSE_RELATIVE_URL_ROOT: /community ## TODO: The mailserver this Discourse instance will use DISCOURSE_SMTP_ADDRESS: DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: DISCOURSE_SMTP_PASSWORD: DISCOURSE_SMTP_ENABLE_START_TLS: true DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none DISCOURSE_SMTP_AUTHENTICATION: login ## The CDN address for this Discourse instance (configured to pull) #DISCOURSE_CDN_URL: //discourse-cdn.example.com ## These containers are stateless, all data is stored in /shared volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log ## The docker manager plugin allows you to one-click upgrade Discourse ## http://discourse.example.com/admin/docker hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git # - git clone https://github.com/discourse/discourse-chat-integration.git # - git clone https://github.com/gdpelican/babble.git # - git clone https://github.com/discourse/discourse-solved.git # - git clone https://github.com/discourse/discourse-adplugin.git # - git clone https://github.com/communiteq/discourse-sitemap.git # - git clone https://github.com/discourse/discourse-bbcode-color.git ## Remember, this is YAML syntax - you can only have one block with a name run: - exec: cd: $home cmd: - rm -fr public/assets - sudo -E -u discourse bundle exec rake assets:precompile - mkdir -p public/community - cd public/community && ln -s ../uploads && ln -s ../backups - replace: global: true filename: /etc/nginx/conf.d/discourse.conf from: proxy_pass http://discourse; to: | rewrite ^/(.*)$ /community/$1 break; proxy_pass http://discourse; - replace: filename: /etc/nginx/conf.d/discourse.conf from: etag off; to: | etag off; location /community { rewrite ^/community/?(.*)$ /$1; } - replace: filename: /etc/nginx/conf.d/discourse.conf from: $proxy_add_x_forwarded_for to: $http_fastly_client_ip global: true - exec: echo "End of custom commands" on browser: [17%20PM] I have disabled all the plugins in the YML config, but its 404 error on assets. In the app container, the folder “community” is already created. Any suggestions?

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

I made the below changes to the config but did not help. run: - exec: cd: $home cmd: - mkdir -p public/community - cd public/community && ln -s ../uploads && ln -s ../backups - replace: global: true filename: /etc/nginx/conf.d/discourse.conf from: proxy_pass http://discourse; to: | rewrite ^/(.*)$ /forum/$1 break; proxy_pass http://discourse; - replace: filename: /etc/nginx/conf.d/discourse.conf from: etag off; to: | etag off; location /community { rewrite ^/community/?(.*)$ /$1; } - replace: filename: /etc/nginx/conf.d/discourse.conf from: $proxy_add_x_forwarded_for to: $http_your_original_ip_header global: true

update: there are 2 folders in /public/community i.e. “backup” and “uploads”. I tried changing the version from tests-passed to stable again but the issue remains the same i.e. no javascript or CSS files and giving 404 error… I also tried to change the permission for the “uploads” folder in community and symlinked assets folder in community but did not help.

Downgrading isn’t possible, if you’re on tests-passed you can’t rebuild on a lower version (beta/stable). You would need to stay on the current tests-passed release until Stable or Beta catches up. Subfolder installs are considered an advanced topic and we really can’t support them here because of all the problems which arise. There are pages and pages of topics detailing the types of problems found when installing against a subfolder. In 2019 there’s really no good reason to use a subfolder install, all of the SEO claims have been debunked, and the added complexity really adds nothing of value. Even on CDCK hosting, subfolder installs are only available to enterprise customers, with an additional fee. I would suggest reverting to a subdomain, or opening a topic on #marketplace to engage with a consultant.

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 if you’re interested.

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?

[תמונה] 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, probably in the external Nginx config. You want to figure it out with the latest version.

[תמונה] john3: Currently, I am trying a fresh installation first, A complete fresh install following Serve Discourse from a subfolder (path prefix) instead of a subdomain is not working?

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.

404 errors (assets) on Subfolder installation

תמיכה

john3 (Johnny) 26 ביוני,‏ 2019,‏ 12:29pm 5

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?

נושא		תגובות	צפיות
Serve Discourse from a subfolder (path prefix) instead of a subdomain Self-Hosting docker , subfolder , how-to , advanced-setup	30	45013	14 באפריל,‏ 2026
Blank Page After installing Discourse on Subfolder Self-hosting	8	1713	31 באוגוסט,‏ 2018
Setup wizard emoji wrong in subfolder install Bug subfolder	38	3731	24 ביולי,‏ 2018
Upgrade doesn't work when installed with subfolder Bug	5	1705	6 ביוני,‏ 2017
Discourse Assets Missing Self-hosting unsupported-install	17	2487	22 בפברואר,‏ 2020

404 errors (assets) on Subfolder installation

נושאים קשורים