Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Problem with IIS8 proxy

General Discussion

2250

I
Insanee last edited by

Hi,

I've installed nodeBB and configured IIS8 with port 80 as proxy so I'm able to use
forums.{page}.eu for the nodeBB board.

The problem is, when I try to use the forum (e.g posting), this error appears: (it's in german)
Firefox kann keine Verbindung zu dem Server unter ws://forums.{page}.eu/socket.io/?EIO=3&transport=websocket aufbauen.
-> Firefox was not able to connect to the server at ws://forums.....
1 Reply Last reply
Reply Quote 0

Suggested Topics

X

nginx reverse proxy
General Discussion • • xenofilodotcom

5

0
Votes

5
Posts

3203
Views

X

well. thx so much for all reply, the nginx .conf works for me. and i found you should put 0.0.0.0 before the port 80. so it would look like

server {
listen 0.0.0.0:80;
server_name forum.example.org; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass http://127.0.0.1:4567/; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }
}
Problem to reach replied/original post in paginated forum
Bug Reports • bug • • crazycells

3

0
Votes

3
Posts

204
Views

@baris said in Problem to reach replied/original post in paginated forum:

What version of NodeBB are you using? This seems to be fixed in 1.11.0 https://github.com/NodeBB/NodeBB/issues/6948

Thanks a lot. Yes, ours is older than 1.11 but we will be upgrading soon to the latest 1.12
Good to hear that will resolve the issue.
M

Shoutbox problem with time
General Discussion • • Master

1

0
Votes

1
Posts

383
Views

M

Hi!

As you can see in the images, shoutbox shows wrong time.

https://github.com/Schamper/nodebb-plugin-shoutbox

0_1528148526892_SHU_wpDakG.png

0_1528148528127_SHU_g6VDdG.png

0_1528148532188_SHU_z5pNW1.png
Problem with WEBSOCKET - SSL
General Discussion • • Master-Antonio

4

0
Votes

4
Posts

1955
Views

I had this problem with Safari only. Chrome and Firefox don't see to mind it as long as you turn the orange cloud to grey. Also I setup a pagerule to disable all acceleration and caching but I'm still using strict SSL and don't get the polling errors anymore. (except in safari.. sigh)
Looks like your connection to NodeBB was lost, please wait while we try to reconnect.
Technical Support • nginx nodebb connection lost error • • setkyar

4

0
Votes

4
Posts

1917
Views

The common causes for a session mismatch error are usually one of the following:
1. Mis-configured URL parameter in your config.json file
If you have a misconfigured url value in your config.json file, the cookie may be saved incorrectly (or not at all), causing a session mismatch error. Please ensure that the link you are accessing your site with and the url defined match.
2. Improper/malformed cookieDomain set in ACP
Sometimes admins set this value without realising that they probably don't need to set it at all. The default is perfectly fine. This is what the config looks like:

Cookie Domain setting

If this is set, you'll want to revert the setting by editing your database directly:

Redis: hdel config cookieDomain
MongoDB: db.objects.update({ _key: "config" }, { $set: "cookieDomain": "" });
3. Missing X-Forwarded-Proto header from nginx/apache
If you are using a reverse proxy, you will need to have nginx pass a header through to NodeBB so it correctly determines the correct cookie secure property.

In nginx, you will need to add the directive like so:
location / { ... proxy_set_header X-Forwarded-Proto $scheme; ... }