Technical Support

Just linking this related issue.

I think it would be cool, but might take a little bit, if you made it so that admins could make custom skins by just changing the colors, and setting if it is a round or square skin, so like the Cerulean skin VS. the Cosmo theme. I know ...

GitHub (github.com)

yeah, no issues here either running node v4.4.5LTS with nodebb 1.0.3
I wonder if it is maybe a plugin causing it?

@pichalite That fixed it. Thanks for your help!

Link to that forum disabled for now 😄

Problem was solved by leaving blank the Cookie Domain field in Admin -> Settings -> Advanced

@Alexander-Craggs MongoDB, version 2.6 or greater is required

Thanks, I'll work on it and report here.

I think I got it pushed to the Heroku app because it did the building process it does with my own app, and I can see nodeBB in the Heroku logs starting up, but it crashes right away now. I am thinking it might have something to do with the MongoDB connection? (It's a Sandbox MongoLabs connection, but it works for my other app and when I run NodeBB locally it makes changes to to the online MongoLab DB as confirmed through their administrative tools)

These are my Heroku logs:
2016-06-15T00:00:56.420459+00:00 app[web.1]:
2016-06-15T02:54:01.203018+00:00 app[web.1]: > [email protected] start /app
2016-06-15T02:54:01.203024+00:00 app[web.1]: > node loader.js
2016-06-15T02:54:03.280111+00:00 heroku[web.1]: Process exited with status 0

I might have done something horribly wrong when building but I am at a loss for what it could be. After cloning the NodeBB from your git, and then trying to push it to my app with a fresh repo clone, it tells me what the srcref for master isn't there when I try "git push heroku master", however if I try what the tutorial says "git push -u heroku v1.x.x:master" it says that it's up to date instead and nothing gets pushed. This is when I tried setting my git heroku branch to master and pushing anyway (it uploaded and the app crash)

EDIT: I am going to try and do a fresh clone later when I get back from work and create a new Heroku app to attempt this from Step 1, and I will detail my process for you guys so that you have a better understanding of what I might be doing wrong.

Thats nice, support in native language is good 🙂

solved

can anyone add it to official documentation?
https://docs.nodebb.org/en/latest/configuring/proxies/apache.html

Thanks

Thanks, guys! I got it to work.

Fixed in latest master, the labels were swapped, so "Access" was actually controlling "Create", and vice versa.

@yariplus said in NGINX config problem ?:

If a location is defined by a prefix string that ends with the slash character, and requests are processed by one of proxy_pass, fastcgi_pass, uwsgi_pass, scgi_pass, or memcached_pass, then the special processing is performed.

... this explains so much 😓

Hi, have you guys tried using the master branch to see if this has been resolved already? It sounds.. familiar

Note: The mail form I speak about is located on my frontpage at https://www.jenkler.se. (Page bottom!)

@pichalite Yes. I have tested that if the user is not currently online, the user is able to receive email from executing the above code.

Threw something quick together based on nodebb-plugin-spoilers, I also looked into extending the existing markdown plugin using the extension support the parser has, but didn't really succeed. Would be great if we could just add markdown-it extensions in the admin panel to extend the syntax, cuz there are plenty existing ones

@frissdiegurke No no, root was actualy that user I was sudo in. The forum runs as a non privilged user. I created that symbolic link but mails aren´ t sent. 😞

Sending mails from the cli with the user www-data works also.

I clicked restart forum and the forum is still dead. It's been 5 minutes.
Usually restart only takes 10 secs before the site is back up.
I don't really have a development background so this might be a dumb question... help please...!

edit
its been ~40 minutes I'm still getting the 502... should I give up...

@pichalite said in How to delete all topics from a Category ?:

delete/purging topics from the client side does not remove the category

You are right....so I am left with a 'fake' category which I disable anyway