Issues with 2nd NodeBB installation

[cagatay]

@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]

@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]

@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]

@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]

@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]

@cagatay I already started it

[cagatay]

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

[phenomlab]

@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]

@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]

@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]

@phenomlab now yes; was flexable

[phenomlab]

@cagatay Thought so.

Now we have to deal with the invalid cert

[cagatay]

@phenomlab sorry for small detail

[phenomlab]

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

[cagatay]

@phenomlab setted

[phenomlab]

@cagatay Working now

[cagatay]

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

[phenomlab]

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

[cagatay]

@phenomlab may i use iframely for 2 domains also in the one machine?
answer- yes worked thank you

[phenomlab]

@cagatay yes, that will be fine. Just watch for potential caching conflicts as you will have two sites writing to the one instance of iframely.