I am stuck with the same problem and I am on uberspace, too. You can set up a socket.io address in the config.json, but I did not yet find the correct setup to get it to work with https
![spicewiesel spicewiesel](https://i.imgur.com/7qGEkeL.jpg)
spicewiesel
Posts
-
Where can I change the websocket port -
[solved] mobile page does not work with v1.1.2both hints helped. My nodebb did not load pages like themes/skins properly, so I tried to get websockets to work. I bypassed my shared hoster env by using an self compiled nginx on a non-privileged port and ssh tunnel (to prevent firefall changes) on that system, and that way I got websockets. Now I was able to load the theme page and so I switched to another theme, restarted and switched back to my current theme. Afterwards I stopped my temporary nginx-ws-tunnel-solution and the mobile page works for me now.
Next step: Find a solution for a permanently working websocket setup on my hosters systems.
thanks!
-
[solved] mobile page does not work with v1.1.2@PitaJ thanks! that might be because I am on uberspace, a shared hoster. Is there a way I can check if websockets work? Then I could play with the config and check the results.
-
[solved] mobile page does not work with v1.1.2Unfortunately I still have this problem.
I set up a fresh 1.4.2 installation and only used the database of my old installation and the menu bar is still broken in the mobile view.Would be great if anyone has an idea or could take a look. The Page is https://community.berlinreds.de
Thanks!
-
[solved] mobile page does not work with v1.1.2Hi there.
One of the most admired features of NodeBB was the great mobile page, my users loved it. Since an update to v1.1.x it no longer works correctely. The menu button is not respondand and so no user can navigate on the system. I cannot tell which upgrade broke it, but we are on v1.1.2 now.
thanks in advance!
TilPS:
I opened a github issue for this: https://github.com/NodeBB/NodeBB/issues/5026
-
upgrade always fails with "has no method 'map'"thanks, I will reset all plugins for the next update to test which one causes the trouble.
-
nodebb crashes with node 4,5,6 while listing pluginsHi there,
I got a nodebb v.1.1.2 running on node v.0.10.43 and everything is fine that far.
But for nodebb-plugin-calender I need node v4+, so I switched my environment.
NodeBB starts fine now but as soon as I click on the Plugin page on my admin panel nodeBB crashes and shows me this:TypeError: Cannot assign to read only property 'id' of < at Object.Plugins.normalise (/home/spicewiesel/bin/nodebb/src/plugins.js:266:20) at Request._callback (/home/spicewiesel/bin/nodebb/src/plugins.js:257:12) at Request.self.callback (/home/spicewiesel/bin/nodebb/node_modules/request/request.js:187:22) at emitTwo (events.js:87:13) at Request.emit (events.js:172:7) at Request.<anonymous> (/home/spicewiesel/bin/nodebb/node_modules/request/request.js:1044:10) at emitOne (events.js:77:13) at Request.emit (events.js:169:7) at IncomingMessage.<anonymous> (/home/spicewiesel/bin/nodebb/node_modules/request/request.js:965:12) at emitNone (events.js:72:20) at IncomingMessage.emit (events.js:166:7) at endReadableNT (_stream_readable.js:913:12) at nextTickCallbackWith2Args (node.js:442:9) at process._tickCallback (node.js:356:17)
Everything is fine as soon as I switch back to my old v.10.43 and even a fresh installation with node v4+ leads to the same result.
What can I do now?
thanks
spice -
upgrade always fails with "has no method 'map'"Every single update I did within the last weeks failed like that
$ git fetch remote: Counting objects: 1214, done. remote: Compressing objects: 100% (103/103), done. remote: Total 1214 (delta 826), reused 819 (delta 819), pack-reused 292 Receiving objects: 100% (1214/1214), 522.88 KiB | 0 bytes/s, done. Resolving deltas: 100% (878/878), completed with 408 local objects. From https://github.com/NodeBB/NodeBB ff70f36..c0a4bf9 v1.x.x -> origin/v1.x.x b3b2d81..8a107c8 master -> origin/master * [new branch] user-flairs -> origin/user-flairs 7646170..69f9c7f weekly -> origin/weekly * [new tag] v1.1.2 -> v1.1.2 * [new tag] v1.1.3-auto.0 -> v1.1.3-auto.0 $ git reset --hard v1.1.2 HEAD is now at c0a4bf9 Incremented version number $ ./nodebb upgrade 1. Bringing base dependencies up to date... OK 2. Checking installed plugins for updates... OK TypeError: Object <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.10.0</center> </body> </html> has no method 'map' at Request._callback (/home/marqualy/bin/nodebb/nodebb:155:25) at Request.self.callback (/home/marqualy/bin/nodebb/node_modules/request/request.js:187:22) at Request.emit (events.js:98:17) at Request.<anonymous> (/home/marqualy/bin/nodebb/node_modules/request/request.js:1044:10) at Request.emit (events.js:95:17) at IncomingMessage.<anonymous> (/home/marqualy/bin/nodebb/node_modules/request/request.js:965:12) at IncomingMessage.emit (events.js:117:20) at _stream_readable.js:944:16 at process._tickCallback (node.js:458:13)
I then have to start from scratch by checking out the release, installing deps and so on. Which is annoying but in the end I can use my old files and database and get a working setup. But what is wrong here?
thanks in advance!
spice