Ogólnie przydałoby się coś po Polsku, jednak problem z NodeBB jest taki, że wymaga on dość specyficznego środowiska - wymagany jest specjalny shared hosting lub swój VPS/dedyk co wymusza posiadanie nieco większej wiedzy (już na starcie) przy wdrażaniu. Stad nie jest on aż tak powszechny i tym samym taki support może mieć problem z przebiciem - choć jakby nie patrzeć byłoby to kolejne miejsce promocji dla silnika NodeBB
Not a NodeBB specific test, but a NodeJS one, and just an isolated example, but suggests that Node at least is far faster on Linux. Now keep in mind this is old so pretty much worthless as a test. I'm interested to do some real testing, though.
@julian said in Cannot start nodebb with systemd:
Hi julian, sorry for my delay response.
I changed the services as you suggested, essentially this was my first implementation.
I removed the file output.log, then I rebooted the system and started the services, when I went in the logs folder the file output.log was empty.
I used journalctl -fu nodebb.service to see the log of the service, and I discovered a nice thing:
UPDATE 2 [FIXED]
Okay, so after spending some times on this, I discovered what is the cause of the problem. Essentially, I have installed nodebb as root account (which is wrong, my bad), and the systemd service was configured to run nodebb as the user "sfarzoso", but that user was not the owner of nodebb folder, so when I started the service using systemd, a permission problem happen.
For fix this, I chowned the "opt" folder for "sfarzoso", which is the folder that I need to install nodebb, then I cloned the repo of nodebb and launched the setup again.
All works now.
Thanks for the attention, king regards.
@PitaJ said in email notifications for post queue:
Just so everyone knows, there's a search bar in the ACP, that searches the ACP. If you're looking for a setting that may be a good place to start.
Oh, I've never seen that. It's in all that "Dead space" way up top that I scroll past before it even loads because there is so much wasted space. Good to know that that is there.
Would be nice to see that area compressed a bit, so much empty space up there.
@PitaJ said in "csrf-invalid":
@PatheticMustan please try removing the config.json socket.io option. It's dangerous. More information here: https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins
Thanks for the tip! I have since removed it, and it still works
@PitaJ said in Private Git for install plugins:
@Joykiller there's no easy way to keep the links with npm, but yarn is better at not killing them.
Ah ok, well ill put up with it. Till I write some bash that checks to make sure the links there or something and if not replaces it after some trigger. I'll look into it later.
Finally found a topic with good explanation an answers:
Didn't expect the config.json would influence such requests.
In order to connect to the MongoDB of my VPS by means of MongoDB Community Compass installed on my PC, I need to provide authentication: username, password and authentication database. Which credentials may I set here? The username admin and the authentication database admin, or the username nodebb and the authentication database nodebb? Also, what must I do with the connection configuration options "SRV Record", "Read Preference" and "SSL"? May I set something here?
Néstor Llamas Llopis
Example here https://github.com/certbot/certbot/issues/5817
Got the same error, never got it before, using similar basic setups. Seems very common - Does anyone have any insight in how to get around or what to check?
FedericoBiccheddu created this issue in certbot/certbot
"Could not automatically find a matching server block." on custom nginx configuration
Look, I am from India. I really want to know how to start paid subscription
Give me ways to implement it
In india we have payu , razorpay , paytm .. but nodebb doesn't support any . So how can I proceed with this
@scottalanmiller Those are fair points. In this particular instance I'm less concerned about improving site performance than on capitalizing on CloudFront's other features, like WAF integration.
Sounds like I'm in a very small niche here.
Thanks for the answer.
Changing the mongodb params came from earlier posts on the forum
I take that I could as well include them directly in the config.sjon as parameters to the uri query.
Yes, I did spend hours on googling this and similar error messages.
No, you can't create any collection manually on admin on MongoDb Atlas.
Neither from CLI nor from web interface.
Have upgraded from M0 to M2 just to see if there would be any impact but it isn't.
The most interesting thing is that the collection socket.io on admin was not created on local instance in order to get the nodebb to run. I am able to create it locally but setup did not create it.