Erros 404 (assets) na instalação em subpasta

john3 · Junho 20, 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 · Junho 22, 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 · Junho 26, 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 · Junho 26, 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 · Junho 26, 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 · Junho 26, 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 · Junho 26, 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 · Junho 27, 2019, 6:19pm

Atualmente, estou tentando uma instalação limpa primeiro, como você pode ver na primeira postagem, até a página de registro não está funcionando corretamente. Já tentei assets:precompile, mas não houve efeito. Existe alguma maneira de tentar instalar uma versão mais antiga do Discourse Docker?

pfaffman · Junho 27, 2019, 6:33pm

A menos que você queira usar este fórum por uma ou duas semanas e depois excluí-lo, você realmente, realmente, realmente não quer fazer isso.

Minha suposição é que você pulou algum passo minúsculo em algum lugar que está causando o problema, provavelmente na configuração externa do Nginx. Você quer descobrir isso com a versão mais recente.

Falco · Junho 27, 2019, 6:43pm

Uma instalação limpa completa seguindo Serve Discourse from a subfolder (path prefix) instead of a subdomain não está funcionando?

john3 · Junho 27, 2019, 8:35pm

Sim, não está funcionando. É por isso que estou travado em erros 404: os arquivos JavaScript não estão sendo carregados e retornando erro 404, conforme mostrado na primeira postagem.

john3 · Junho 27, 2019, 8:36pm

esta é minha configuração externa para o proxy reverso 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 · Junho 27, 2019, 9:07pm

Mas o arquivo yml que você tem acima não parece com o que está em Serve Discourse from a subfolder (path prefix) instead of a subdomain.

john3 · Junho 27, 2019, 9:20pm

Isso ocorre porque aquele arquivo de configuração não funcionava no passado, então o que estou usando agora foi sugerido por @neil aqui e funcionou anteriormente. Atualmente, também tentei o arquivo de configuração enviado lá, mas ele também não funcionou.

Falco · Junho 27, 2019, 9:46pm

Bem, acabei de comprar um novo droplet e configurei aqui: https://subfolder.muito.ninja/forum, seguindo o Serve Discourse from a subfolder (path prefix) instead of a subdomain

Está funcionando bem para mim.

Então, temo que seu proxy reverso esteja causando o problema…

Ivan_Rapekas · Junho 27, 2019, 9:46pm

Olá @john3, a instalação em subpasta é dolorosa

Comparei minha configuração (esquerda) e a sua (direita), dê uma olhada na linha 12, provavelmente você esqueceu de alterar a palavra forum. Em seguida, tenho um bloco extra replace, linhas 22-29:

O final:

Proxy externo:

location /discuss {

## Este é o ProxyPassReverse para 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; #Linha importante para nosso objetivo de registro

## Fim do ProxyPassReverse para 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 · Junho 28, 2019, 7:36pm

Você poderia compartilhar comigo sua configuração de proxy reverso?

john3 · Junho 28, 2019, 7:49pm

Fiz as alterações e continua igual. Minhas configurações estão abaixo. Estou usando CentOS 7 com overlay2 como driver de armazenamento de dispositivos.

Proxy reverso Nginx:

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; #Linha importante para nosso objetivo de log

## Fim, isso é ProxyPassReverse para 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 "Fim dos comandos personalizados"

Poderia me enviar a última parte da sua configuração YML, ou seja, -exec…?

Falco · Junho 28, 2019, 7:49pm

Isso depende de qual software você está usando para fazer o proxy reverso.

Estou usando o Caddy e seguindo Use Caddy instead of NGINX as your reverse proxy

A única mudança em relação ao guia é adicionar a pasta no Caddyfile:

subfolder.muito.ninja

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

john3 · Junho 28, 2019, 8:00pm

Entendi… Estou usando um Droplet da Digital Ocean com CentOS 7 e o driver de armazenamento overlay2. Nginx como servidor web e SSL do Let’s Encrypt.

Tópico		Respostas	Visualizações
Serve Discourse from a subfolder (path prefix) instead of a subdomain Self-Hosting docker , subfolder , how-to , advanced-setup	30	43353	14 de Abril de 2026
Blank Page After installing Discourse on Subfolder Self-hosting	9	1551	5 de Setembro de 2018
Setup wizard emoji wrong in subfolder install Bug subfolder	39	3239	25 de Julho de 2018
Upgrade doesn't work when installed with subfolder Bug	6	1545	6 de Junho de 2017
Discourse Assets Missing Self-hosting unsupported-install	17	2306	22 de Fevereiro de 2020

Erros 404 (assets) na instalação em subpasta

Tópicos relacionados