@PitaJ said in Syntax error when ./nodebb upgrade:
@oplik0 that's entirely incorrect. git fetch does literally nothing to local files, and even if it did, ./nodebb upgrade only affects the database and files that aren't handled by git.
Oh, possible. It probably fixed things for me because my problems were mostly due to me messing with NodeBB files. It seemed to reset the upgrade then, but that probably was because it didn't get to actually changing anything while I broke it.
Old, i know but still relevant.
One important thing to consider is not to use mongodb. I don't know if Azure has a strange config that doesn't go well with nodebb's standard config or if it's just a bug in their current version (they use 3.2, current is 3.6 on Ubuntu, 4.2 on Windows).
It works with redis (at least connection from my VM succeeded).
Also julienstroheker managed to get an older version of nodebb running in an azure App Service. So basically there is a way
Unfortunately the old link is not available anymore, but I found the new instructions here: http://sharp.pixelplumbing.com/en/stable/install/#freebsd
Just in case that it's going down again, here are the short instructions which are missing in the FreeBSD install documentation of NodeBB ( https://docs.nodebb.org/installing/os/freebsd/ )
pkg install -y pkgconf vips
cd /usr/ports/graphics/vips/ && make install clean
I had to add DISABLE_VULNERABILITIES=yes to the end of the last command, because of some outdated dependency in the port. AFAIK the vips package is only used during installation or upgrade of NodeBB, so that shouldn't be any security issue.
Thanks @PitaJ, ok now nodebb is running by systemd and restart from admin panel is working.
the following : https://community.nodebb.org/topic/14306/default-installation-and-looking-the-log-file
A close feature or resolved can be cool
Email is email, so this has nothing to do with NodeBB specifically. So this answer is a pure "general IT" response...
At the end of the day, it is impossible to control email going into someone's spam folder, what does and doesn't go into that folder is at their discretion. It's like asking "how can I guarantee that someone will read my letter that I mail to them?" You can't. Once you deliver the letter, you have to just hope that they will open it and read it, you can't force them.
But there are many things that you can do to encourage email not being seen as spam. First, make sure you are using an enterprise email service. No amount of "good behaviour" from small time email services will get the delivery reliability of the big boys, and even those get marked as spam often.
You can ask your users to whitelist you. But that's just asking them not to let you go to spam, it's up to them.
Make sure you have proper SPF and DKIM records, and that your IP is not on any blacklists, and that you aren't sending any spam or anything that looks like spam from your system. Make sure your domain URL isn't blacklisted. Some incompetent shops check PTR records, too, which is total BS, but as some incompetent people do that, it can help to have a "proper as they incorrectly see it" PTR set for your email server, too.
That's about all that you can do, all anyone can do. For any email, for any purpose.
@julian said in Make cookies opt-in?:
@scottalanmiller I agree, but I don't want to find out what would happen were it to be challenged in a court of law
True, but the court case in question is about a pre-checked cookie box (implicit acceptance) rather than an explicit acceptance. Different than what is being discussed here.
While trying to install nodebb on Heroku i am having problems to connect to postgres databases provided by Heroku add-ons - "Standard 0" and up. Connecting to lower performance Heroku postgres add-ons, like "Hobby dev" and "Hobby basic", works.
I found the recommendation to add a ssl param to the connection string when connecting to postgres via node.js apps but did not found the right place in the nodebb code to add an additional param (https://devcenter.heroku.com/articles/connecting-to-heroku-postgres-databases-from-outside-of-heroku).
Can anyone give me a hint?
@signal15 documentDB is not compatible with NodeBB. It is supposed to be a drop in replacement for MongoDB but the clients that we have that tried using it ran into some issues
Otherwise if you run into issues with FarGate, do post here and we'll work through them
@julian said in Google Recaptcha v3 not working:
As far as I know ReCAPTCHA v3 should be working, I'll let @bentael know if there's been a change.
@oplik0 said in Google Recaptcha v3 not working:
v3 is not just "a better reCAPTCHA" and it is not replacing v2.
v3 only offers "invisible" reCAPTCHA, but even if Spam Be Gone supported that (it doesn't yet) it still wouldn't work because it passes different data.
reCAPTCHA v2 is binary - either user is a robot or not.
v3 doesn't just pass "true||false" but instead passes a score from 0.0 to 1.0 and it's up to the application to determine what score is a success. It also never shows user a challenge as it's not supposed to interrupt the user in any way.
So to sum it up: for Spam Be Gone to support v3 would mean changing the way it handles reCAPTCHA and I'm not even sure if it's a good idea. v3 is supposed to continuously chceck if user is a bot without interruptions, so it's best used for frequent user actions like posting or login, not for things like registration that happen once per user and it's not a big deal if it interrupts user with a challenge. So I'd say it'd be better for Spam Be Gone to extend its functionally to use v3 on login and posting, and leave v2 on the registration page.
That convinced me Thanks a lot.
Unfortunately I'm not a developer and do not know how to develop a plugin, but I'll highly appreciate if it's developed by anyone (NodeBB team or another mate).
You were right about the nginx
The ico issue persists though, recently upgraded to 1.12.2 and uploading ico files still fails despite whitelisting them in the extensions field.
After disabling the isImage check (in src/controllers/uploads.js), then it works flawlessly. I suppose this isn't a big issue since we don't need the size checks and all that stuff on image uploads.
But it would be nice if uploading .ico files could work without having to edit the source.