@scottalanmiller @julian I'll try to remove that package. If it's not nodebb, how come that the server can render my website through nginx proxy with port 8080...

@scottalanmiller Below is the final output from the command

nodebb/node_modules/safe-buffer/README.md:server.listen(8080)
nodebb/node_modules/body/README.md:http.createServer(app).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/body/README.md:}).listen(8080)
nodebb/node_modules/secure-keys/package.json:  "_shasum": "f0c82d98a3b139a8776a8808050b824431087fca",
nodebb/node_modules/async-listener/test/core-asynclistener-nexttick-remove.simple.js:server.listen(8080, function() {
nodebb/node_modules/async-listener/test/core-asynclistener-only-add.simple.js:server.listen(8080, function() {
nodebb/node_modules/jimp/server.js:app.listen(8080);
nodebb/node_modules/jimp/server.js:console.log("Serving on http://127.0.0.1:8080");

@scottalanmiller I am on Ubuntu 16.04. Not sure if that's an issue though but I haven't encountered any reading issue until this update.

@scottalanmiller Thanks, I figured out the issue with the dashboard. In the error.log of nginx, it shows that

  /var/lib/nginx/proxy/8/83/0000000838" failed (13: Permission denied) while reading upstream

Even though the permission to this folder is valid, I am still not able to read the file. I have to rename the folder and restart the nginx according to Permission denied while reading upstream. But the port issue remains unresolved.

@scottalanmiller So previously, before updating, I ran the nodebb on 4567, 4568,4569 and pass the 443 proxy to these 3 with Nginx. Now, despite the config.json, I have to forward to 8080 which is the port that the NodeBB is on. I might try to initiate another AWS instance with the same setting to see how it goes.

tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3215/nginx      
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      2944/node       
tcp        0      0 127.0.0.1:21            0.0.0.0:*               LISTEN      608/vsftpd      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      928/sshd        
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1111/sendmail: MTA:
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      3215/nginx      
tcp        0      0 0.0.0.0:27017           0.0.0.0:*               LISTEN      1294/mongod     
tcp        0      0 127.0.0.1:587           0.0.0.0:*               LISTEN      1111/sendmail: MTA:
tcp6       0      0 :::22                   :::*                    LISTEN      928/sshd        
tcp6       0      0 :::9000                 :::*                    LISTEN      1049/hhvm       
udp        0      0 0.0.0.0:42932           0.0.0.0:*                           544/dhclient    
udp        0      0 0.0.0.0:68              0.0.0.0:*                           544/dhclient    
udp6       0      0 :::59961                :::*                                544/dhclient

@PitaJ I tried only initiate without SSL but the result was the same

@PitaJ The problem is that I am not able to view the site since Google prohibits user visiting site without https. Thanks for the suggestion, I'll delete the gzip and see how it goes. What makes it harder to debug is that the log doesn't show up any error.

@julian I am nodebb running on aws with nginx

@scottalanmiller the nodebb is running on 8080. For reason I don' know, the nodebb always runs on port 8080 despite the setting in config.json.

@PitaJ I did, I tried multiple times, rebuilt and restarted nodebb and Nginx. I even tried to reinstall nodebb and connect to the original database. I wonder if it's the issue with my nginx setting. I am on node -v10.15.3 , npm 6.9

     error_log /var/log/nginx/error.log crit;
     
     events{
     
             #worker_connections 4000;
     
             }
     
     http{
     
     server {
              listen       80;
             server_name  myurl.com;
     	return 302 https://$server_name$request_uri;
           }
     
     
     server {
         listen 443;
         ssl on;
         ssl_certificate /etc/nginx/ssl/cert_chain.crt;        
         ssl_certificate_key /etc/nginx/ssl/private.key;    
         server_name myurl.com;
      
     
       location / {
     
     
             proxy_pass         http://127.0.0.1:8080;
             proxy_set_header   Host $host;
             proxy_set_header   X-Real-IP $remote_addr;
             proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
             proxy_set_header   X-Forwarded-Host $server_name;
             proxy_set_header X-Forwarded-Proto $scheme;
             proxy_set_header Host $http_host;
             proxy_set_header X-NginX-Proxy true;
     
             proxy_redirect off;
     
             # Socket.IO Support
             proxy_http_version 1.1;
             proxy_set_header Upgrade $http_upgrade;
             proxy_set_header Connection "upgrade";
             }
     
             gzip on;
             gzip_vary on;
             gzip_min_length 10240;
             # gzip_proxied expired no-cache no-store private auth;
             gzip_types text/plain text/css text/xml text/javascript application/x-javascript application/xml;
             gzip_disable "MSIE [1-6]\.";
     
         }
     }

Below is the config.json

{
    "url": "myurl",
    "secret": "secret",
    "database": "mongo",
    "port": [
        "4567",
        "4568",
        "4569"
    ],
    "mongo": {
        "host": "127.0.0.1",
        "port": "27017",
        "username": "username",
        "password": "pass",
        "database": "db",
        "uri": ""
    }
}

Does anyone have any idea on this? I cannot find any error in log file. all the link become mydomain.com/admin#. User visiting data is not showing. Search tool is not working either.

hi, all the link in the admin page are not working after updating to version v.1.12.1.
all the link become mydomain.com/admin#.; whereas, the main page works as usual. All the emoji plugin and editing tool are broken as well.

After upgrading to 1.5.x version from 1.4.x, nodebb could only run on 0.0.0.0:8080 instead of port 4567 set in the config.json. I am pretty sure that there's no process listening on port 4567.

Here's the my config.json

  {
    "url": " mystieurl",
     "port":"4567",
     "secret": "secret number",
     "database": "mongo",
           "mongo": {
             "host": "127.0.0.1",
            "port": "27017",
           "username": "usr",
            "password": "pass",
          "database": "db"
        }
   }

@julian
Even though elasticsearch works, I still wonder why NodeBB doesn't support Chinese text search ? In order to build env for EasticSearch in AWS, the cost of hardware increases rapidly. Now I am seeking an alternative method.

@julian I did try contact him and also sent a merge request to him weeks ago but he did not respond to me yet.

here's the repository Nodebb-plugin-elasticsearch

Since the current nodebb search engine seems not to support Chinese-text search, I choose the elasticsearch as the content, post and topic, search engine.
I found nodebb-plugin-search-elasticsearch but the original author doesn't maintain it anymore. I made few modification of it.

Before doing searching, remember to start elasticsearch and import your data from the original Nodebb-supported database, mongodb/redis ,to elaseticsearch to build index by any plugin you use. (I am using mongo-connector.)