just updated my instance to current and they still work.
1579617f-7dc9-47f9-93fa-ae1c18fed158-image.png
95300b7c-a57e-4724-bf66-ba5a25a78edf-image.png

If I click on the MangoLassi.it header or the unread button the screen goes black. Nothing shows below the header.

@gjacobse said in Why do we have a downvote limit?:

While I'll defer to @scottalanmiller, it's likely to reduce some 'personal' opinion level votes. I'd rate them at 'vengeance' votes.

^ this.
If left unchecked, things can get nasty and really sour the place.

Also, obligatory xkcd:

https://imgs.xkcd.com/comics/duty_calls.png

They don't display for me. When checking the browser console, I'm seeing an HTTP response of 403.

GEThttps://mangolassi.it/uploads/files/ml/16.06.29-Colo-NTG-Ad1.jpg [HTTP/1.1 403 Forbidden 0ms]

@scottalanmiller Thanks! It had me in a sad state for weeks....

@gotwf said in Setup NodeBB on Fedora 33 with PostgreSQL and Nginx with HTTPS only:

@JaredBusch So... now that you've had this up and running for a while, care to report on how that is going? Inquiring minds are curious. Particularly w.r.t. resource utilization comparison, performance differences, etc. comparatively. I think you were on Mongo previously, correct? Cuz I am right there with you on the license bullshit. All it takes is one bump in the road, merger, and wham, history repeats and next major version changes license again - only this time to something closed. Have no interest in betting on community to fork and continue. Need a safer bet. It would appear that percona may have already done so w/their percona mongodb offering but I wonder if that would continue as a full fork if/when upstream became closed source.

TIA-- o/

Well 2 years in, i do not run any NobeBB instances with heavy traffic so performance is not even something I look at. I have like 5 of these running for tiny personal projects that people I know have asked for my help with.

@scottalanmiller said in Deploying NodeBB 1.14 on CentOS 8 with MongoDB 4.2:

By default, NodeBB uses the REDIS NoSQL database,

By default, in 1.15.x it uses Mongo

I'm pretty sure it did in the last version I installed also. But that was months ago and I do not recall clearly.

I know this topic is not for NodeBB.eu, but for consistency I will post it last time here.

I failed hard on the last deadline, the last 5 months I spend just on learning about TAX/VAT, Invoices, because i want to generate them automatically and i want to be also right with General Data Protection Regulation so need to do some changes to db, and everything is taking time. I set another deadline but wont share it here, i will create new post when it will be ready (about 5-8 months).

@JaredBusch said in Deploying NodeBB 1.13 on CentOS 8 with MongoDB 4.2:

You can only remove this line if you are going to host the reverse proxy on the same instance.

No reverse proxy needed if you are going to just look at it locally without going over the network.

@scottalanmiller said in Ask as question does not work on new topic creation:

I just noticed that like yesterday but thought that it was me.

been broke for months. i never got around to reporting it

@jmoore said in NodeBB 1.11.2 Error Connect EMFILE:

@scottalanmiller Is that why the site fails to load at times then?

Not every time, but a few times.

@bnrstnr said in Deploying NodeBB 1.11.1 on CentOS 7 with MongoDB 4:

What specific reasons for the CentOS recommendation here?

Revisiting a little...

Basically the three main Linux releases supported by MongoDB are CentOS, Ubuntu, and Debian. CentOS and Ubuntu here are mostly six of one. But CentOS 8 Stream I like a little more than the Ubuntu LTS options. We use Ubuntu a little more often than CentOS today, but in this case I feel that CentOS is slightly better for us. But really, all three options are perfectly fine. We just have to pick one.

@DustinB3403 , indeedily doodily

Sorry, ignore me. I got this figured out. I was being really dumb and had the wrong config.json file open and didn't know what I was looking at. Just ignore. Yes, the socket.io settings were missing, but were on my screen so I was sure that they were there.

Oops, we didn't not resolve this and moved to CentOS and there was no further issue.

@scottalanmiller said in NPM Errors on NodeBB Install on Amazon Linux:

@DustinB3403 said in NPM Errors on NodeBB Install on Amazon Linux:

Have you tried as root?

Everything was done as root. Amazon is all root by default.

yeah, the default user for centos is centos with your KMS or privatekey they create. For Ubuntu is Ubuntu.

Command was...

nvm use 0.10.8, as it was already installed here, just not in use.