Never mind I was accidentally using the $ sign LOL. Was a long night.

@pitaj Followup to last message ... turns out Heroku does not allow access through any other port than the one it gives you. Is this an insurmountable obstacle and I should look into other hosting, or is there a workaround?

@sebastian-marinescu alternatively you could set defaultPlugins as an environment variable, then run ./nodebb setup [config json]. I'll re-add an actual option for passing in a set of default plugins.

@countach said in "NodeBB could not connect to your Mongo database" Error: @baris thats the thing I do not get that prompt to specify the DB, it attempts to connect automatically after ./nodebb setup is executed. Could it be the authentication settings? I have security authorization enabled in my mongod.conf ... If you had an existing config.json, it will only try to fill in blanks. Try moving your config.json out of the way and running it again. It will have prompts like this... 7/7 01:07:24 [3009] - info: Now configuring mongo database: Host IP or address of your MongoDB instance (127.0.0.1) Host port of your MongoDB instance (27017) MongoDB username Password of your MongoDB database

Thanks @PitaJ I installed Node manually this way which worked perfect. Then continued with NodeBB guide & NPM install worked curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.0/install.sh | bash Reboot machine . ~/.nvm/nvm.sh Determine what version of Node to install nvm install 6.10.3 check version is installed by running node -e "console.log('Running Node.js ' + process.version)" Thank you Todd

you have to run docker network inspect bridge the result will be : [ { "Name": "bridge", "Id": "a82774b4cc857b934ca5d3bba8f20a077aef3c117b9a390455466fb8785aea0f", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.17.0.0/16", "Gateway": "172.17.0.1" } ] }, "Internal": false, "Containers": { "64e285ed8b6a287c693df8244f4cf45c6e724e74e979734b823f14f19cb2a74b": { "Name": "node-bb-redis", "EndpointID": "869f51cfefb3d1d59b5f0cc881c16e6a127b423345704c7f17bc3f10c5061922", "MacAddress": "02:42:ac:11:00:02", "IPv4Address": "172.17.0.2/16", "IPv6Address": "" }, "7fd7885220b189427121102a9cf34e7b2259b5d1038b3f6a522f24e1e3ebd25b": { "Name": "node-bb", "EndpointID": "9d971bdd8675714ba96385c3832cf08a0ed6630cc40e8ac08d3666c42f0b9133", "MacAddress": "02:42:ac:11:00:05", "IPv4Address": "172.17.0.5/16", "IPv6Address": "" }, "8391d3e8f44f064e885e2cf754a59a7cc00d24ca5c2db13b4add0152308eb843": { "Name": "nginx-letsencrypt", "EndpointID": "0416947f3ff616fb063b17363ef4f5d282a0549bc15582a842f97155b9ede5c2", "MacAddress": "02:42:ac:11:00:04", "IPv4Address": "172.17.0.4/16", "IPv6Address": "" }, "a06b204eb61be007c093488aa1f3491407b784c48c4b3a069afcc967892b1522": { "Name": "nginx-proxy", "EndpointID": "6de08ad911df8e80b04f4600909b76c70d3dd99f26a586cc444bf5a2ec97e2ef", "MacAddress": "02:42:ac:11:00:03", "IPv4Address": "172.17.0.3/16", "IPv6Address": "" } }, "Options": { "com.docker.network.bridge.default_bridge": "true", "com.docker.network.bridge.enable_icc": "true", "com.docker.network.bridge.enable_ip_masquerade": "true", "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0", "com.docker.network.bridge.name": "docker0", "com.docker.network.driver.mtu": "1500" }, "Labels": {} } ] Find your redis IP and put it in your nodeBB config (in my case Redis IP is 172.17.0.2)

Well, damn. Didnt know that. Okay, Thanks for your phenomenal help, @pichalite. Gonna mess around with this proxying and nginx a bit now that everything is moving forward again.

Oh look right there in the manual that I stopped reading after the GUI was up... https://docs.nodebb.org/en/latest/configuring/config.html

I managed to fix this and thought I would post this here for posterity. I edited the file npm-shrinkwrap.json and replaced the code block on line 1159: "simple-recaptcha": { "version": "1.0.0", "from": "git://github.com/wzrdtales/simple-recaptcha.git#f408725106872df696436ff6a988923539ab80a6", "resolved": "git://github.com/wzrdtales/simple-recaptcha.git#f408725106872df696436ff6a988923539ab80a6" } with: "simple-recaptcha": { "version": "1.0.0", "from": "https://github.com/wzrdtales/simple-recaptcha/archive/v1.0.0.tar.gz", "resolved": "https://github.com/wzrdtales/simple-recaptcha/archive/v1.0.0.tar.gz" }

@julian Just do all the stuff from the scratch solve all the problem.

@julian I now get a 502 bad gateway message from Nginx (which I think is what I should be seeing). Thanks for all your help

Thank you @markkus and @jarey for your replies. I did what you suggested about re-installation and the problem persisted. I then discovered something... ...the installation manual may be outdated. The file in question on Step 7 is mongod.conf instead of mongodb.conf. Can @psychobunny or whoever in charge of the Doc double check this and make the proper correction?

You can automate it by using this guide. https://github.com/ahwayakchih/openshift-nodebb Or the one written by me. https://community.nodebb.org/topic/3866/guide-nodebb-0-6-1-on-openshift-for-windows-users-with-putty/1 Or use official NodeBB guide. https://github.com/NodeBB/nodebb-english/blob/master/installing/cloud/openshift.rst This is not a bug. You have used npm install command in the wrong folder. Use OpenShift Online in your browser to download NodeBB files to /app-root/runtime/repo and it will work as it should.

@pitaj said: @Master-Antonio add your domain in the config.json file which sits in the NodeBB main directory. Did, but don't work.

@a_5mith True, but honestly, it's easier to set up a quick Linux VM (and I say this as someone who is not at all a fan of Linux) and the support is far better.

@julian If that code still works, then yes, it should. I stacked 10toship with the $100 student code that a kind member offered me.

@Master-Antonio I still offer free NodeBB hosting right here: https://community.nodebb.org/topic/2291/offering-a-couple-nodebb-instances-for-free/11

@Ted said: If you'll start NodeBB and leave it running, I'll see if I can can connect to it and register a profile I can't this server is not open on internet, only in local.

Wow, thanks guys for the replies! I'll try it out after I had something to eat. I'm very excited to try out NodeBB. @frissdiegurke said: Greetings back from Germany PS: Great decision to use arch Yay, another German. And yes, we all love arch, don't we?