Errori 404 (asset) su installazione in sottocartella

john3 · 20 Giugno 2019, 1:50pm

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:

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?

john3 · 22 Giugno 2019, 8:42am

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

john3 · 26 Giugno 2019, 3:51am

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.

Stephen · 26 Giugno 2019, 4:50am

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.

john3 · 26 Giugno 2019, 12:29pm

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?

Stephen · 26 Giugno 2019, 12:58pm

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.

pfaffman · 26 Giugno 2019, 1:42pm

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.

john3 · 27 Giugno 2019, 6:19pm

Attualmente sto provando prima un’installazione pulita, come puoi vedere nel primo post, persino la pagina di registrazione non funziona correttamente. Ho provato assets:precompile, ma senza alcun effetto. Esiste un modo per provare a installare una versione precedente di Discourse Docker?

pfaffman · 27 Giugno 2019, 6:33pm

A meno che tu non voglia usare questo forum per una settimana o due e poi eliminarlo, non vuoi assolutamente farlo, davvero, davvero, davvero.

Immagino che tu abbia saltato qualche piccolo passaggio da qualche parte che sta causando il problema, probabilmente nella configurazione esterna di Nginx. Devi risolverlo con l’ultima versione.

Falco · 27 Giugno 2019, 6:43pm

Un’installazione completamente pulita seguendo Serve Discourse from a subfolder (path prefix) instead of a subdomain non funziona?

john3 · 27 Giugno 2019, 8:35pm

Sì, non funziona, ed è per questo che sono bloccato con errori 404: i file JavaScript non vengono caricati e restituiscono un errore 404, come mostrato nel primo post.

john3 · 27 Giugno 2019, 8:36pm

Questa è la mia configurazione esterna per il reverse proxy Nginx.

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/community;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

pfaffman · 27 Giugno 2019, 9:07pm

Ma il file yml che hai sopra non sembra essere quello in Serve Discourse from a subfolder (path prefix) instead of a subdomain.

john3 · 27 Giugno 2019, 9:20pm

Questo perché quel file di configurazione non funzionava in passato, quindi quello che sto usando ora è stato suggerito da @neil qui e ha funzionato in passato. Attualmente ho anche provato il file di configurazione caricato lì, ma anche quello non ha funzionato.

Falco · 27 Giugno 2019, 9:46pm

In realtà, ho appena acquistato un nuovo droplet e l’ho configurato qui: https://subfolder.muito.ninja/forum, seguendo la guida Serve Discourse from a subfolder (path prefix) instead of a subdomain

Per me funziona perfettamente.

Quindi temo che il tuo reverse proxy stia causando il problema…

Ivan_Rapekas · 27 Giugno 2019, 9:46pm

Ciao @john3, l’installazione in sottocartella è dolorosa

Ho confrontato la mia configurazione (a sinistra) e la tua (a destra), dai un’occhiata alla riga 12, probabilmente hai dimenticato di cambiare la parola forum. Inoltre, ho un blocco extra replace, righe 22-29:

La fine:

Proxy esterno:

location /discuss {

## Questo è ProxyPassReverse per Nginx
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $remote_addr;

proxy_set_header X-Forwarded-Proto $scheme;

proxy_read_timeout     3600;
proxy_connect_timeout  240;
proxy_set_header Host $host;
proxy_set_header X-RealIP $remote_addr; #Riga importante per il nostro obiettivo di logging

## Fine di questo è ProxyPassReverse per Nginx

proxy_pass http://192.168.1.2$request_uri;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

john3 · 28 Giugno 2019, 7:36pm

Potresti condividere con me la tua configurazione del reverse proxy?

john3 · 28 Giugno 2019, 7:49pm

Ho apportato le modifiche ma il problema persiste. Di seguito sono riportate le mie configurazioni. Sto utilizzando CentOS 7 con overlay2 come driver di archiviazione dei dispositivi.

Nginx reverse proxy:

location /community {
                pagespeed  off;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $remote_addr;

proxy_set_header X-Forwarded-Proto $scheme;

proxy_read_timeout     3600;
proxy_connect_timeout  240;
proxy_set_header Host $host;
proxy_set_header X-RealIP $remote_addr; #Riga importante per il nostro obiettivo di logging

## Fine: questo è ProxyPassReverse per Nginx

proxy_pass http://127.0.0.1:25654$request_uri;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

app.yml

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 ^/(.*)$ /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: 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 "Fine dei comandi personalizzati"

Potresti inviarmi l’ultima parte della tua configurazione YML, ovvero -exec…?

Falco · 28 Giugno 2019, 7:49pm

Questo dipende dal software che stai utilizzando per il reverse proxy.

Sto usando Caddy e seguo Use Caddy instead of NGINX as your reverse proxy

L’unica modifica rispetto alla guida è l’aggiunta della cartella nel Caddyfile:

subfolder.muito.ninja

proxy /forum unix:/sock/nginx.http.sock {
  transparent
}

john3 · 28 Giugno 2019, 8:00pm

Capisco… Sto utilizzando un droplet di Digital Ocean con CentOS 7 e il driver di archiviazione overlay2. Nginx come server web e SSL di Let’s Encrypt.

Argomento		Risposte	Visualizzazioni
Serve Discourse from a subfolder (path prefix) instead of a subdomain Self-Hosting docker , subfolder , how-to , advanced-setup	30	43342	Aprile 14, 2026
Blank Page After installing Discourse on Subfolder Self-hosting	9	1550	Settembre 5, 2018
Setup wizard emoji wrong in subfolder install Bug subfolder	39	3237	Luglio 25, 2018
Upgrade doesn't work when installed with subfolder Bug	6	1545	Giugno 6, 2017
Discourse Assets Missing Self-hosting unsupported-install	17	2306	Febbraio 22, 2020

Errori 404 (asset) su installazione in sottocartella

Argomenti correlati