Tom Riddleff
Posts
-
Permissions issue. -
Is it possible to reset privileges?Now I'm trying to figure out how to fix it through interference into Redis.
-
Is it possible to reset privileges?Ou! Hi @Julian!
I'm so glad you answered.
Regarding the issue.
Yea. I'm kinda hacked myself. How? have no clue.
Related thread: https://community.nodebb.org/topic/3709/permissions-issue
With the screenshots and details. -
Is it possible to reset privileges?Is it possible some how to reset privileges either programatically or withit the Admin dashboard facility?
Apparently I've broke up my admin account and can't post messages, manage users...so almost anything.And try to find out the solution how to make it work.
-
Permissions issue.@a_5mith Thank you for advise.
But unfortunately list of User Groups in "Category" >> "Access" is empty
I don't even have a clue how could I broke it.In Groups I have 2 groups: Administrators and dummy 'Test group'. Both of them are not editable for admin.
Can't create a new group as well.
Please help[Update] I'm using 0.6.x version
-
Permissions issue.I don't know how I did it. But now neither Admin nor users can't post messages, chat, add topic in the forum.
Could you please help me to solve it or direct me to the right place?Now Admin has no permissions to manage the categories, users, ets. At least he can enter the admin dash board.
-
[SOLVED]socket.io - websocket custom portThank you for your note, @julian
I acctually found what I were need.
Adding an appropriate string to config.json - solved my problem."socket.io": { "address": "http://myforum.com:8000" }
Thus websocket will use port 8000 on establishing the connection.
One of openshift's bottleneck, that held me up.
Done -
[SOLVED]socket.io - websocket custom portHi guys!
A question appeared regarding the websockets.
When I deployed app on server - I permanently get 400 Bad request on websocket connection request.
It uses port :80 by default. However 'polling' works well.
ws://mysite.com/socket.io/?EIO=3&transport=websocket&sid=Bmp017bUrGU9UVQTAAABIs it possible to some how force websockets to use another port than '80'?
e.g. ws://mysite.com:8080/socket.io/?EIO=3&transport=websocket&sid=Bmp017bUrGU9UVQTAAAB -
openshift deploymentI assume I did some mistake during the setup.
This step of tutorial is not quite clear. Cuz Setup doesn't require you to provide 'IP or Hostname to bind to'. Probably it applies for the old versions. I use 0.6.x
'''
IP or Hostname to bind to: Enter what your $OPENSHIFT_NODEJS_IP value holds here found in >step 4.
'''Here is setup data I used:
- URL used to access this NodeBB (http://nodebb-XXXXXX.rhcloud.com)
BTW should I add a port to the URL?
-
Please enter a NodeBB secret (9d810ea3-f957-4d1f-aeeb-XXXXXXXXXX)
-
Host IP or address of your Redis instance (127.10.126.130)
-
Host port of your Redis instance (16379)
-
Password of your Redis database
-
Which database to use (0..n) (0)
24/1 06:22 [22832] - info: Configuration Saved OK
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No description
npm WARN package.json [email protected] No description
[email protected] node_modules/connect-redis
āāā [email protected] ([email protected])[email protected] node_modules/redis
24/1 06:23 [22832] - info: Populating database with default configs, if not already set...
24/1 06:23 [22832] - info: Previous theme detected, skipping enabling default theme
24/1 06:23 [22832] - info: Administrator found, skipping Admin setup
24/1 06:23 [22832] - info: Categories OK. Found 4 categories.
24/1 06:23 [22832] - info: Enabling default plugins
24/1 06:23 [22832] - info: Beginning database schema update
24/1 06:23 [22832] - info: [2014/10/31] Applying newbiePostDelay values skipped
24/1 06:23 [22832] - info: [2014/11/6] Updating topic authorship sorted set skipped
24/1 06:23 [22832] - info: [2014/11/7] Renaming sorted sets skipped
24/1 06:23 [22832] - info: [2014/11/11] Upgrading permissions skipped
24/1 06:23 [22832] - info: [2014/11/17] Updating user email digest settings skipped
24/1 06:23 [22832] - info: [2014/11/29] Updating config.json to new format skipped
24/1 06:23 [22832] - info: [2014/12/2] Removing register user fields skipped
24/1 06:23 [22832] - info: [2014/12/12] Updating teasers skipped
24/1 06:23 [22832] - info: [2014/12/20] Updating digest settings skipped
24/1 06:23 [22832] - info: [upgrade] Schema already up to date!A couple warnings, nothing serious. Overall Setup status OK. Right?
It should work but it doesn't. -
openshift deployment@Mega Thank you for your feedback!
Unfourtunately it doesn't help.Here is the log with the caught error:
24/1 05:43 [372716] - info: NodeBB v0.6.0 Copyright (C) 2013-2014 NodeBB Inc.
24/1 05:43 [372716] - info: This program comes with ABSOLUTELY NO WARRANTY.
24/1 05:43 [372716] - info: This is free software, and you are welcome to redistribute it under certain conditions.
24/1 05:43 [372716] - info:
24/1 05:43 [372716] - info: Time: Sat Jan 24 2015 05:43:51 GMT-0500 (EST)
24/1 05:43 [372716] - info: Initializing NodeBB v0.6.0
24/1 05:44 [372716] - error: Error: listen EACCES
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1020:19)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at module.exports.listen (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/src/webserver.js:136:18)
at /var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:656:23
at fn (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:641:34)
at Object._onImmediate (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:557:34)
at processImmediate [as _immediateCallback] (timers.js:330:15)
Error: listen EACCES
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1020:19)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at module.exports.listen (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/src/webserver.js:136:18)
at /var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:656:23
at fn (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:641:34)
at Object._onImmediate (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:557:34)
at processImmediate [as _immediateCallback] (timers.js:330:15)
24/1 05:44 [372716] - error: Error: listen EACCES
at errnoException (net.js:901:11)
at Server._listen2 (net.js:1020:19)
at listen (net.js:1061:10)
at Server.listen (net.js:1135:5)
at module.exports.listen (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/src/webserver.js:136:18)
at /var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:656:23
at fn (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:641:34)
at Object._onImmediate (/var/lib/openshift/54c26f0f5973ca552000011f/app-root/runtime/repo/node_modules/async/lib/async.js:557:34)
at processImmediate [as _immediateCallback] (timers.js:330:15) -
openshift deploymenthi guys!
I'm getting stuck with the launching nodebb on openshift. on the final stage when I do start the app - I get the error listening EACCES, despite I strictly follow the steps.
has anyone experience same issue?
could you please advice how can I solve it?