Tips to get 1.6.0 running after updating from 1.5.x

Technical Support
  • Hi guys, here some tips for who experimented problems after 1.5.x -> 1.6.0 upgrade.

    Symtoms client-side:

    • .jst generated only after a page refresh
    • .jst not generated at all
    • "Uncaught SyntaxError: Unexpected token < " message in browser console.
    • Various failures messages in browser console loading from /assets/... routes.
    • General requirejs errors like "require.js:34 GET net::ERR_ABORTED".
    • JS modules loading errors like "tag_assistant_compiled.js:119 GET 503 (Service Unavailable)".

    After various attempts and settings, I've identified that problems comes from NGINX settings. Reading nginx logs, in particular the error.log file, I found a clue.

    The settings suggested in documentation or here in the forum doesn't work for me, some modifications and adjustments are required.

    The key change is the adding of this to rules:

     proxy_headers_hash_bucket_size  64;
     proxy_headers_hash_max_size  512;

    and other little modification was the re-arrangement of configuration blocks that now looks like:

    # HTTPS server
    server {
    	listen 80;
    	root /path/to/NodeBB;
    	index index.html index.htm;
    	return         302 https://$server_name$request_uri;
    server {
    	listen 443 ssl spdy;
    	ssl_certificate /etc/nginx/ssl/cert_chain.crt;
    	ssl_certificate_key /etc/nginx/ssl/server.key;
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	ssl_ciphers 'AES128+EECDH:AES128+EDH';
    	ssl_prefer_server_ciphers on;
    	# This rules was moved here from location object 
    	proxy_set_header X-Real-IP $remote_addr;
    	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    	proxy_set_header X-Forwarded-Proto $scheme;
    	proxy_set_header Host $http_host;
    	proxy_set_header X-NginX-Proxy true;
    	proxy_redirect off;
    	# New fixes. Values are powers of 2, this works for me, you can increase.
    	proxy_headers_hash_bucket_size  128;
    	proxy_headers_hash_max_size  1024;
    	# Socket.IO Support
    	proxy_http_version 1.1;
    	proxy_set_header Upgrade $http_upgrade;
    	proxy_set_header Connection "upgrade";
    	location @nodebb {
    	location ~ ^/assets/(.*) {
    		root /path/to/NodeBB/;
    		try_files /build/public/$1 /public/$1 @nodebb;
    	location /plugins/ {
    		root /path/to/NodeBB/build/public/;
    		try_files $uri @nodebb;
    	location / {

    Hopings this helps someone of you.

    Pura Vida!

  • I have the same issue.

    I will give this a shot and see if this works.

  • @Adam-Poniatowski: You might want to check browser-console-errors-after-v1-6-0-upgrade as well. I had the same issue, and I could solve it with a fix in nodebb.

  • @frgilb I'm not using cloudflare though (mentioned in the other thread you posted).

    I haven't gotten around to doing this fix yet... but I will try it, when I have the time. work, work, work 😞

Suggested Topics