Skip to content

Issues with 2nd NodeBB installation

Solved General
22 2 2.7k 1
  • @MadWay NodeBB is in fact based on NodeJS so doesn’t use PHP at all.

    @phenomlab there is some problem with my second installation of NodeBB the same machine. NodeBB installed
    Db created
    SSL done
    All confings are done
    But website not opening the problem is ERR_TOO_MANY_REDIRECTS

  • @phenomlab there is some problem with my second installation of NodeBB the same machine. NodeBB installed
    Db created
    SSL done
    All confings are done
    But website not opening the problem is ERR_TOO_MANY_REDIRECTS

    @cagatay Can you provide more detail as to the steps you took to install the second instance of NodeBB - for example

    1. Directory location
    2. NGINX config

    etc…

    Thanks

  • phenomlabundefined phenomlab marked this topic as a question on
  • @cagatay Can you provide more detail as to the steps you took to install the second instance of NodeBB - for example

    1. Directory location
    2. NGINX config

    etc…

    Thanks

    @phenomlab
    Added new user as nojor
    NodeBB installed this path
    Mangodb created db and user
    NodeBB confing.js fixed
    sites-avalieble added as below
    What i should do more?

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
    	
    	
    	ssl_certificate /etc/ssl/nojorcert.pem;
        ssl_certificate_key /etc/ssl/nojorkey.pem;
    	ssl_client_certificate /etc/ssl/cloudflare.crt;
    	
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	
        server_name www.uzayyolu.org;
    
        location / {
            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_pass http://127.0.0.1:4418;
            proxy_redirect off;
    
            # Socket.IO Support
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
        }
    	
    
        real_ip_header CF-Connecting-IP;
    	set_real_ip_from 103.21.244.0/22;
    	set_real_ip_from 103.22.200.0/22;
    	set_real_ip_from 103.31.4.0/22;
    	set_real_ip_from 104.16.0.0/12;
    	set_real_ip_from 108.162.192.0/18;
    	set_real_ip_from 131.0.72.0/22;
    	set_real_ip_from 141.101.64.0/18;
    	set_real_ip_from 162.158.0.0/15;
    	set_real_ip_from 172.64.0.0/13;
    	set_real_ip_from 173.245.48.0/20;
    	set_real_ip_from 188.114.96.0/20;
    	set_real_ip_from 190.93.240.0/20;
    	set_real_ip_from 197.234.240.0/22;
    	set_real_ip_from 198.41.128.0/17;
    	set_real_ip_from 2400:cb00::/32;
    	set_real_ip_from 2606:4700::/32;
    	set_real_ip_from 2803:f800::/32;
    	set_real_ip_from 2405:b500::/32;
    	set_real_ip_from 2405:8100::/32;
    	set_real_ip_from 2c0f:f248::/32;
    	set_real_ip_from 2a06:98c0::/29;
    	
    	add_header X-Frame-Options "SAMEORIGIN";
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Content-Type-Options "nosniff";
    }
    
    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
    	
    	
    	ssl_certificate /etc/ssl/nojorcert.pem;
        ssl_certificate_key /etc/ssl/nojorkey.pem;
    	ssl_client_certificate /etc/ssl/cloudflare.crt;
    	
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	
        server_name uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
    server {
        listen 80;
        listen [::]:80;
    	
    	server_name uzayyolu.org www.uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
    
    
  • @phenomlab
    Added new user as nojor
    NodeBB installed this path
    Mangodb created db and user
    NodeBB confing.js fixed
    sites-avalieble added as below
    What i should do more?

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
    	
    	
    	ssl_certificate /etc/ssl/nojorcert.pem;
        ssl_certificate_key /etc/ssl/nojorkey.pem;
    	ssl_client_certificate /etc/ssl/cloudflare.crt;
    	
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	
        server_name www.uzayyolu.org;
    
        location / {
            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_pass http://127.0.0.1:4418;
            proxy_redirect off;
    
            # Socket.IO Support
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
        }
    	
    
        real_ip_header CF-Connecting-IP;
    	set_real_ip_from 103.21.244.0/22;
    	set_real_ip_from 103.22.200.0/22;
    	set_real_ip_from 103.31.4.0/22;
    	set_real_ip_from 104.16.0.0/12;
    	set_real_ip_from 108.162.192.0/18;
    	set_real_ip_from 131.0.72.0/22;
    	set_real_ip_from 141.101.64.0/18;
    	set_real_ip_from 162.158.0.0/15;
    	set_real_ip_from 172.64.0.0/13;
    	set_real_ip_from 173.245.48.0/20;
    	set_real_ip_from 188.114.96.0/20;
    	set_real_ip_from 190.93.240.0/20;
    	set_real_ip_from 197.234.240.0/22;
    	set_real_ip_from 198.41.128.0/17;
    	set_real_ip_from 2400:cb00::/32;
    	set_real_ip_from 2606:4700::/32;
    	set_real_ip_from 2803:f800::/32;
    	set_real_ip_from 2405:b500::/32;
    	set_real_ip_from 2405:8100::/32;
    	set_real_ip_from 2c0f:f248::/32;
    	set_real_ip_from 2a06:98c0::/29;
    	
    	add_header X-Frame-Options "SAMEORIGIN";
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Content-Type-Options "nosniff";
    }
    
    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
    	
    	
    	ssl_certificate /etc/ssl/nojorcert.pem;
        ssl_certificate_key /etc/ssl/nojorkey.pem;
    	ssl_client_certificate /etc/ssl/cloudflare.crt;
    	
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	
        server_name uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
    server {
        listen 80;
        listen [::]:80;
    	
    	server_name uzayyolu.org www.uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
    
    

    @cagatay The redirect loop is being caused by this (which I have commented out)

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
    	
    	
    	ssl_certificate /etc/ssl/nojorcert.pem;
        ssl_certificate_key /etc/ssl/nojorkey.pem;
    	ssl_client_certificate /etc/ssl/cloudflare.crt;
    	
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	
        server_name uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
    server {
        listen 80;
        listen [::]:80;
    	
    	server_name uzayyolu.org www.uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
  • @cagatay The redirect loop is being caused by this (which I have commented out)

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
    	
    	
    	ssl_certificate /etc/ssl/nojorcert.pem;
        ssl_certificate_key /etc/ssl/nojorkey.pem;
    	ssl_client_certificate /etc/ssl/cloudflare.crt;
    	
    	ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    	
        server_name uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    
    server {
        listen 80;
        listen [::]:80;
    	
    	server_name uzayyolu.org www.uzayyolu.org;
    	return 301 https://www.uzayyolu.org$request_uri;
    }
    

    @phenomlab so if i add this codes will be work normally? by the way this is same conf like in efelsefe. it works but uzayyolu not interesting.

  • @phenomlab so if i add this codes will be work normally? by the way this is same conf like in efelsefe. it works but uzayyolu not interesting.

    @cagatay If you compare the nginx.conf between the two sites, they aren’t the same - you are missing the final block on the newer site which is causing the loop. I’ve changed your NodeBB listening port also in both config.json and nojor.conf as the proxy_path doesn’t seem to work and currently just serves the default nginx page.

    Checking this now.

  • @cagatay If you compare the nginx.conf between the two sites, they aren’t the same - you are missing the final block on the newer site which is causing the loop. I’ve changed your NodeBB listening port also in both config.json and nojor.conf as the proxy_path doesn’t seem to work and currently just serves the default nginx page.

    Checking this now.

    @phenomlab now there is problem with ./nodebb start as below;

    Starting NodeBB
      "./nodebb stop" to stop the NodeBB server
      "./nodebb log" to view server output
      "./nodebb help" for more commands
    
    Error: kill EPERM
        at process.kill (internal/process/per_thread.js:210:13)
        at /home/nojor/nodebb/loader.js:215:14
        at /home/nojor/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16
        at FSReqCallback.oncomplete (fs.js:180:23)
    /home/nojor/nodebb/loader.js:228
                                            throw err;
                                            ^
    
    Error: kill EPERM
        at process.kill (internal/process/per_thread.js:210:13)
        at /home/nojor/nodebb/loader.js:215:14
        at /home/nojor/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16
        at FSReqCallback.oncomplete (fs.js:180:23) {
      errno: -1,
      code: 'EPERM',
      syscall: 'kill'
    }
    
    
  • @phenomlab now there is problem with ./nodebb start as below;

    Starting NodeBB
      "./nodebb stop" to stop the NodeBB server
      "./nodebb log" to view server output
      "./nodebb help" for more commands
    
    Error: kill EPERM
        at process.kill (internal/process/per_thread.js:210:13)
        at /home/nojor/nodebb/loader.js:215:14
        at /home/nojor/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16
        at FSReqCallback.oncomplete (fs.js:180:23)
    /home/nojor/nodebb/loader.js:228
                                            throw err;
                                            ^
    
    Error: kill EPERM
        at process.kill (internal/process/per_thread.js:210:13)
        at /home/nojor/nodebb/loader.js:215:14
        at /home/nojor/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16
        at FSReqCallback.oncomplete (fs.js:180:23) {
      errno: -1,
      code: 'EPERM',
      syscall: 'kill'
    }
    
    

    @cagatay I already started it 🙂

  • @cagatay I already started it 🙂

    @phenomlab then why i do not see forum at web site? just opening nginx welcome page

  • @phenomlab then why i do not see forum at web site? just opening nginx welcome page

    @cagatay It’s a configuration issue which I am looking at now. You’ll see the instance running if you go to http://<ipaddress>:4568

  • @cagatay It’s a configuration issue which I am looking at now. You’ll see the instance running if you go to http://<ipaddress>:4568

    @phenomlab oh i see. thank you Mark. Thank you so much.

    i think the most important point that second nodebb installed other domain name which nojor.com. so we are trying to change name of it also to uzayyolu.org.

    maybe its also caused the problem @phenomlab
    i think clearly way that re-install all for uzayyolu.org?

  • @phenomlab oh i see. thank you Mark. Thank you so much.

    i think the most important point that second nodebb installed other domain name which nojor.com. so we are trying to change name of it also to uzayyolu.org.

    maybe its also caused the problem @phenomlab
    i think clearly way that re-install all for uzayyolu.org?

    @cagatay No, I don’t think so. I think this is related to SSL enryption. In Cloudflare, can you set the SSL encryption for this domain to full ?

  • @cagatay No, I don’t think so. I think this is related to SSL enryption. In Cloudflare, can you set the SSL encryption for this domain to full ?

    @phenomlab now yes; was flexable 😞

    99a171fb-10bb-44a3-91d2-8db8e68fdf52-image.png

  • @phenomlab now yes; was flexable 😞

    99a171fb-10bb-44a3-91d2-8db8e68fdf52-image.png

    @cagatay Thought so.

    9fee9491-b960-4c29-8688-de5cbd2e8a41-image.png

    Now we have to deal with the invalid cert

  • @cagatay Thought so.

    9fee9491-b960-4c29-8688-de5cbd2e8a41-image.png

    Now we have to deal with the invalid cert

    @phenomlab sorry for small detail 😞

  • @phenomlab sorry for small detail 😞

    @cagatay No problem - can you set it to full and not Full (Strict)

  • @cagatay No problem - can you set it to full and not Full (Strict)

    @phenomlab setted

  • @cagatay Working now 🙂

  • @phenomlab yes i see but i delete all of forums and post how can i do it?

  • cagatayundefined cagatay has marked this topic as solved on
  • @phenomlab yes i see but i delete all of forums and post how can i do it?

    @cagatay You’d need to delete these manually or reinstall with a blank database.


Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • NodeBB v4.0.0

    General nodebb sudonix version 4
    28
    4 Votes
    28 Posts
    2k Views
    @Panda said in NodeBB v4.0.0: the workings of World aren’t intuitive Its not easy to get World populating when a forum is new to it This is a good point and one I’ve considered also. It’s a little confusing to be honest.
  • Is my Mongodb installation correct?

    Solved General mongodb
    27
    4
    13 Votes
    27 Posts
    6k Views
    [image: 1711303116154-yuuuuu.png]
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    578 Views
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Fresher in Nodebb install

    General nodebb
    24
    15 Votes
    24 Posts
    4k Views
    @Hari I’ve been reading a lot about APO. Looks impressive.
  • NodeBB v2.4.0

    Solved General nodebb version error
    3
    1
    2 Votes
    3 Posts
    686 Views
    @phenomlab As always…Thank you. Worked for me.
  • 2 Votes
    4 Posts
    772 Views
    @qwinter it’s workable I think, but not perfect - then again, unless you write a specific plugin to perform such a task, what is. As you pointed out, you have versioning of sorts with the historical access to reach post.
  • Discord Login - OAuth2 - NodeBB

    Solved General discord nodebb plugins
    32
    11 Votes
    32 Posts
    5k Views
    @Galaxian hi, and welcome to Sudonix Can you check your config.json file and ensure that your forum URL doesn’t have a trailing backslash or forward slash in it ? This was the issue @Sampo2910 had.
  • NodeBB Blog Comments

    General nodebb blog
    3
    1 Votes
    3 Posts
    641 Views
    @kurulumu-net Not specifically, but you should review this post from the very large thread as it will save you a lot of time. There’s significant customisation on the Ghost side of things, but not in NodeBB https://community.nodebb.org/post/86022