Community

@phit said in Invalid CSRF Token:

for the record for people finding this via search, for apache2 you have to set this somewhere in your nodebb vhost configuration

Thank you very much. This really made my day !!!

@FrankM said in Probmes with login after upgrading to 1.11.0:

But in config.json i have http://...... Edit it to https:// solved the problem.
Before version 1.11.0 i don't have this problem.

Thanks, that solved the problem for me as well, changing http to https. And as for you, I did not have this problem before 1.11.0

But then an other problem turned up: "Invalid CSRF Token"

Pls see this link https://community.nodebb.org/topic/9222/invalid-csrf-token

My solution for this was what is written in the end (I use Apache2)

for the record for people finding this via search, for apache2 you have to set this somewhere in your nodebb vhost configuration
with ssl

RequestHeader set X-Forwarded-Proto "https"

without ssl

RequestHeader set X-Forwarded-Proto "http"

you might have to enable mod_headers to do so!

So upgrading to 1.11.0 gave me a problem that had to be solved in 2 steps. First by changing in config.json, then I had to modify Apache2 settings.

After having installed 1.11.0 it appears an od thing when logging in.

• I go to the https://nodebbs.mysite.com and the login page appears as normal.
• Then I write my email and PW and clicks on the Log in -button
• Then a red frame turns up saying "The page is missing" and provides a link to the first page and that link works, it takes me to the first page that looks like normal when being looged in.

What is odd is that the page with the red frame and the text saying "The page is missing" has an URL like this

https://nodebbs.mysite.com/https://nodebbs.mysite.com

So the login button doubbled the URL !!! This must be a bug I suppose. Or ???

@baris said in Error after upgrading to 1.11.0:

NodeBB is on version 1.1.0 so the command should use v1.1.x.

1.11.0 worked fine for me.

@baris

Hi, Thank you, you are on the right track. I kept on searching and found a solution. Old processes where running so I had to kill them. Restart did not help.

EADDRINUSE means that you already have NodeBB running. Use ps utility to find and kill it.

Then

ps aux|grep nodebb, then note the process Id and use kill -9 <said id>

There were many prcesses running, so I found it easier just to restart the server. Now all is fine.

Thank you anyhow.

I tried my first upgrade today, to 1.11.0. I run

$ git fetch # Grab the latest code from the NodeBB Repository
$ git checkout v0.4.x # Type this as-is! Not v0.4.2 or v0.4.3, but "v0.4.x"!
$ git merge origin/v0.4.x

but when starting up it stops after a short while and the log gives:

2018-12-05T12:35:30.710Z [19247] - error: listen EADDRINUSE: address already in use 0.0.0.0:4567
Error: listen EADDRINUSE: address already in use 0.0.0.0:4567
at Server.setupListenHandle [as _listen2] (net.js:1294:14)
at listenInCluster (net.js:1342:12)
at doListen (net.js:1480:7)
at process.internalTickCallback (internal/process/next_tick.js:72:19) {"code":"EADDRINUSE","errno":"EADDRINUSE","syscall":"listen","address":"0.0.0.0","port":4567}
2018-12-05T12:35:30.710Z [19247] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
3 restarts in 10 seconds, most likely an error on startup. Halting.

What setting has changed to give this?
Error: listen EADDRINUSE: address already in use 0.0.0.0:4567

Under /admin/settings/post there are "Default Post Sorting" and "Default Topic Sorting"

The issue is that I would like to make these settings per categori. Some sorted Oldest to newest and others sorted Newest to oldest.

Is that possible to do, and if so, how to do it?

@PitaJ

Now it works as it should. It is OK if I click on the botton. I don't know what happend last time.

Many thanks, any how.

Hans

@PitaJ

Hi

I clicked on the Connect button, and "The site is in maintainance mode: Please come back later." showed up on the screen.

Hi

I've just successfully set up the site and is now fooling around to learn how it works. In Chrome I logged in as "admin" and set the site in maintainance mode. I then tried to log in as "admin" from Edge , but it is not possible, I just have the message that the site is in maintainance mode: Pls come back later.

So my conclusion is that if I log out from Chrome I will not be able to log in again as admin and then I can't reach the admin pages.

I find this odd. How do I log in as admin after having set the site in maitainance mode?

I have the latest versions of everything. I use Mongo and Apache2