yuuuuu.png
Issues with 2nd NodeBB installation
-
@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
-
@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
-
@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
? -
@phenomlab now yes; was flexable
-
@cagatay Thought so.
Now we have to deal with the invalid cert
-
@phenomlab sorry for small detail
-
@cagatay No problem - can you set it to
full
and notFull (Strict)
-
@phenomlab setted
-
@cagatay Working now
-
@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.
-
@phenomlab may i use iframely for 2 domains also in the one machine?
answer- yes worked thank you -
@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.