@svetlana It looks like it is a problem of either v1.0 itself or incompatible plugins. I reverted openshift-nodebb README to 0.9.x. You can try fresh install with 0.9.x, and later, when things cool down a bit and plugins are updated, you can update to 1.0.

AFAIK you can have up to 3 "servers" on OpenShift for free. And since you already know the drill, it should be easy to make another instance of NodeBB just for testing :).

@svetlana Thanks for the info. I'll test that. I just tested with plugin mentioned in example of the guide and it too just hanged there. I'll check it some more and let you know.

Yes, you should always wait for plugin to be ready for the version of NodeBB you're using. Unless you want to test and let devs know about the results :). But in that case, be sure to test on installation that is "expendable".

@svetlana Did you try that ./nodebb start locally, or after logging in to OpenShift through SSH? Because there's a c:\ path there in your log, which makes me believe you tried to run it locally.

Can you write which plugin did you try to add?

@Nisthar Process of creating the snapshot downloads it to local directory:
https://developers.openshift.com/en/managing-backing-up-applications.html

Hi,

@nhl-pl sent me link to this topic. I've just tested 0.8.x branch: installation and starting up both went smooth and i could login, visit administration panel, etc...

I followed steps described here: https://github.com/ahwayakchih/openshift-nodebb, just changed 0.7.x to 0.8.x in commands.

I tested only Redis installation, no plugins yet or anything more specific yet - just visited page, looked around and logged in.

update: uploading images to topic and as category image works ok too.

Hope it helps :).

It probably help authors of those modules, or at least "emailer-local", if you could find what's different in settings in database. Maybe it's just a tiny option, that could be added to emailer-local and it would work in both cases?

Looking into both modules package.json and index.js it looks like https://github.com/NodeBB/nodebb-plugin-emailer-local/ does not install "nodemailer-smtp-transport" like https://github.com/erlgo/nodebb-plugin-emailer-ssl-smtp does by default. Maybe it was just a case of missing dependency?

As for sending mail, emailer-ssl-smtp adds secure: true when setting up transport, but that does not seem to be stored anyway, so shouldn't be used by emailer-local.
Also transport initialization is done a bit differently, but that too shouldn't matter because it's not "shared" in any way between modules.

Glad you found workaround. Still, its strange that you cannot use nodebb-plugin-emailer-ssl-smtp module (or the other one) alone.

@Hägar please check this pull request: https://github.com/erlgo/nodebb-plugin-emailer-ssl-smtp/pull/1

It tells you what has to be changed in template file to prevent that error.

I had similar problem with this plugin, but after restarting application it started working, i.e., settings page is visible and works.

I have a working https://www.npmjs.com/package/nodebb-plugin-emailer-ssl-smtp plugin on NodeBB 0.7.x-dev on OpenShift.
I'm not sure if it's the same problem, but in my case, plugin (or, to be more exact, part of node.js internals) could not verify SMTP server's certificate.

Adding following line, somewhere at the head of nodebb-plugin-emailer-ssl-smtp/index.js should help in such case, but please keep in mind, that it makes sending mails (and any outgoing connections made from the application) unsecure:

process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = '0';

Which means, it should be done ONLY for testing.

If you would like to get a better error report from the plugin, you can try to modify line 48 of nodebb-plugin-emailer-ssl-smtp/index.js file, to look like this:

winston.warn('[emailer.smtp] Unable to send `' + data.template + '` email to uid ' + data.uid + '!!', err);

That should output full error data from node.js to your logs/console, which should help to find out why the plugin could not send e-mail.

Thanks! I just signed it.

@Baerrus same here, i tried to sign CLA, but it keeps erroring out :(.

Hi,

It looks like rhc app create nodebb nodejs-0.10 command did not create nodebb directory.

Please make sure, that you're running commands on your own computer, not through ssh on OpenShift side.

Try to remove nodebb from your OpenShift account and start from scratch.

Calling git init may seemed like it helped, but it created local only repository, which was not connected with any of the others (OpenShift, NodeBB and openshift-nodebb). That is why git push origin master did not work - origin remote was not configured.