Community

Thank you very much! I was able to use the Admin user that was created in this authentification

Open an issue on Github, please. We can more easily track things there.

Hi all,

I realize this is an old topic, but given that I'm dealing with exactly the same problem, I figured it would be sensible to reply here. Essentially, I've followed the advice of @pichalite and created a simple IIS forward proxy for my NodeBB server. Unfortunately this solution does not yield the desired result, as many requests for resources are not being made to the correct directory - instead, requests are being made to the root level of the IIS Web server (e.g., GET http//website.ca/stylesheet.css?4210ebb0-9225-4237-b2ad-87d88b61756b), and not to the specified port where NodeBB is being hosted (e.g., http://website.ca:4567 or http://localhost:4567).

Any ideas? I've played around with reverse proxies and outbound rules to route all outgoing traffic from http://localhost:4567 to the same URL I've specified for the proxy rule (e.g., http//website.ca/associates-hub) to no avail... If more info or screenshots are needed, they can be provided. I've been banging my head against the wall trying to cycle through all possible solutions to this problem. Any insight would be GREATLY appreciated.

Thanks,

Cam

@jinx glad to hear you got it working :).

Fixed by reinstalling redis-server.

Solved: upgrade to NodeBB v0.7.0.

Something went wrong with setting up connection to MongoDB. Could you please provide some more information about your configuration?

@pitaj said:

@Master-Antonio add your domain in the config.json file which sits in the NodeBB main directory.

Did, but don't work.

I've managed to reproduce the issue on Win2k8R2. It's coming from ImageMagick not being installed/configured correctly.

reproduced.png

These are the steps I took to fix the issue:

Go out and install the latest version of ImageMagick

After running the installer make sure that you close the command prompt from which you are running NodeBB.

Open a new command prompt and rerun node app.js

The problem should be fixed! 🙂resolved.png

@velderia said:

So... As far as npm install I'm having issues pretty much the same here: https://community.nodebb.org/topic/540/-nodebb-theme-lavender-lavender-theme-for-nodebb/73 (at the bottom) but I'm not sure how to reinstall npm on the stack or if that would even help.

I guess I should be developing Node.js on linux but so far I've been dual booting and I'm thinking about investing in like a Gigabyte Brix and having two monitors side by side (or even a KVM switch). I use Windows for graphics and I like Ubuntu for developing stuff and it's kind of my dream setup to begin with.

Edit: After rolling around in bed and drinking some coffee, I manually inserted the lavender theme in the node_modules folder, removed it from the npm-shrinkwrap.json file (created a npm-shrinkwrap-backup don't worry), and tried npm install again. It seemed to work up until "[email protected]" saying "no repository field" as a warning. I had to ctrl-C because it was literally stuck there. Now I have a bunch of nice modules installed in the node_modules folder but I'm assuming not all of them to be able to get NodeBB up and running.
Tl;Dr: npm is really not liking .tgz I think

Edit 2: I screwed up the entire NodeBB installation by typing node app too early and rushing everything. I'm going to take a break and probably upgrade the Ubuntu partition I have and do everything on there. 😞

Hmm... What's the problem you're having exactly. I've been running nodebb on a windows bitnami mean stack for a long time without any issues whatsoever. Just make sure you pick the latest BITNAMI version (sometimes they hide them in favour of older more stable releases), install git and you're off to the races 🙂