I mean, the whole k/v thing was weird to me from the start. I think writing a wrapper around the database stuff and then in the future maybe being able to do npm i nodebb-database-redis, npm i nodebb-database-mongo, npm i nodebb-database-postgresql, etc. would be awesome. Also because everyone could help writing these wrappers for new databases etc.

@teh_g Yep, should still work and there is also the option that you don't have to set up camo manually thanks to @yariplus

@julian nope, it is being compiled down to ES5 with babeljs IIRC

EDIT: Yes, it indeed is: https://github.com/minora-oss/nodebb-plugin-camo/blob/master/package.json#L50-L60

@exodo you can now totally remove the whole configuration and let it run over your main domain as CloudFlare has enabled WebSockets for free.

@yoyimc9 Yes. @yariplus found out about this too. We know what the problem is and are discussing if we can add it to the NodeBB master or if we need to do a plugin for that, even though I think that may be overkill. Basically the problem is that the session cookie for NodeBB is set to something.domain.tld, or in your case paralocos.org. It should be *.domain.tld or *.paralocos.org so that the live.domain.tld can authorize with the cookie too.

@AOKP are there any errors I could take a look at?

@L33t Yes, that is normal. An established WebSocket connection is not "closed" until you close the tab. That's why it shows up with so many seconds. You can happily ignore that

@yariplus yep, the SSL config was probably too strong for older NGINX or OpenSSL versions. I simplified it a bit.

Simplify NGINX config to reduce the chance of errors · yariplus/nodebb-plugin-camo@61224db

Route NodeBB images through camo. Contribute to yariplus/nodebb-plugin-camo development by creating an account on GitHub.

GitHub (github.com)

@ThingBreaker this seems like an issue with your SSL configuration. Did you maybe provide wrong paths to your certificates? It would be helpful if we could get your subdomain for camo too so that we can check and test some things ourselves.

@AOKP I can create a more easier to understand tutorial later, but here is how it looks for Minora at the moment. (Which is what I think you mean)

Here are our current config files, just copied it out. I think the needed information is in there, don't worry about the includes. That's just part of our structure.

NGINX: https://git.minora.io/snippets/1
NodeBB: https://git.minora.io/snippets/2

@hieudang I understand what you are trying to say, even though CloudFlare does provide all of these 3 things for free. But I don't want to turn this into a Incapsula vs. CloudFlare topic, I think we could create a new one for this in the Discussion category

@hieudang Even though this seems to work, it definitely makes no sense to create what you did. Everything is going to CloudFlare anyway in your case. The only difference is that there is one more middleman where CloudFlare get's the data for your website from. There will be no speed improvement if you do this.

@trevor yep, works now!

@yariplus good finding! Yep, minora.io is trusted for me! @trevor just replace cert.pem with fullchain.pem in your server config (you seem to use apache, so I can't help you more specific, sorry)

@yariplus not sure, seems like a common issue:

Search results for 'android' - Let's Encrypt Community Support

Let's Encrypt Community Support

(community.letsencrypt.org)

I am going to try minora which has the fullchain, let's see.

@yariplus @trevor @jarey same here. Certificate Authority invalid.

@jarey oh, interesting. Wait. I have a old Android laying around somewhere. Let me check.

@trevor for me everything works. Also the SSL certificate. @jarey Let's Encrypt still has problems with Windows XP, any chance that you are using it? They will fix it in the near future letsencrypt.org/upcoming-features/

Also @trevor your status on convoe is always flashing to green every 5 seconds and then going back to offline. Seems like a bug to me.

@yariplus true, edited accordingly.

@charles, @accalia and @qgp9

nodebb-plugin-camo just got released which should make this whole issue a lot easier to solve. You can find the explanation post here.