• HOME
    • PRODUCT
    • PRICING
    • ABOUT
    • COMMUNITY
    Menu
    • HOME
    • PRODUCT
    • PRICING
    • ABOUT
    • COMMUNITY
    Get in touch
    Get in touch
    Menu
    • HOME
    • PRODUCT
    • PRICING
    • ABOUT
    • COMMUNITY
    • Sign in
    • Start free trial
    • Get in touch
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups
    • Documentation
      • Home
      • Read API
      • Write API
      • Plugin Development
    1. Home
    2. _axe
    _
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 13
    • Best 2
    • Controversial 0
    • Groups 0

    _axe

    @_axe

    2
    Reputation
    569
    Profile views
    13
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    _axe Unfollow Follow

    Best posts made by _axe

    • Redis server outdated, is actually v3.0.3

      whenever i try to start my nodebb installation, i get this:

      [email protected]:~/nodebb$ ./nodebb log

      Type Ctrl-C to exit

      This program comes with ABSOLUTELY NO WARRANTY.
      This is free software, and you are welcome to redistribute it under certain conditions.
      For the full license, please visit: http://www.gnu.org/copyleft/gpl.html

      Clustering enabled: Spinning up 1 process(es).

      21/7 11:25 [4530] - info: Time: Tue Jul 21 2015 11:25:33 GMT-0400 (EDT)
      21/7 11:25 [4530] - info: Initializing NodeBB v0.7.1-dev
      21/7 11:25 [4530] - error: Your Redis version is not new enough to support NodeBB, please upgrade Redis to v2.8.9 or higher.
      [cluster] Child Process (4530) has exited (code: 0, signal: null)

      i've downloaded redis and compiled/installed it from the website, and when i check for the version:

      [email protected]:~/nodebb$ redis-server -v
      Redis server v=3.0.3 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=619f7d62cb8790fc

      version 3.0.3 is definitely higher than v2.8.9...anyone know the issue?

      originally, i had used the redis-server package that came pre-loaded onto my dedicated server, and i had thought that to be the issue.

      posted in Technical Support
      _
      _axe
    • RE: Redis server outdated, is actually v3.0.3

      it's fixed! thanks for the help @julian 🙂

      posted in Technical Support
      _
      _axe

    Latest posts made by _axe

    • RE: [nodebb-plugin-minecraft-integration] Minecraft Integration!

      @yariplus said in [nodebb-plugin-minecraft-integration] Minecraft Integration!:

      @_axe said in [nodebb-plugin-minecraft-integration] Minecraft Integration!:
      Any chance you can add support for prefixes that players get from groups they're in? I'm running PermissionsEx and the only prefix that went through is the custom one that was set manually.

      Hmm, they should get all PEX prefixes automatically, have they relogged after linking their account? The prefixes are updated when the player logs in to the server next.

      also I can't seem to get the widgets to appear, any ideas/troubleshooting you can give me?

      Are they appearing correctly in the admin panel? If so, there may have been an error writing to the database. Check the browser console and nodebb logs.

      They're mostly working now, thanks 🙂 the PEX was just that the person with the custom prefix happened to be the only person who relogged, haha. Server status and top players are working fine now, but TPS graph isn't working... the only thing in ./nodebb log is a bunch of "Got socket request", any ideas why it specifically wont work?

      posted in NodeBB Plugins
      _
      _axe
    • RE: [nodebb-plugin-minecraft-integration] Minecraft Integration!

      Any chance you can add support for prefixes that players get from groups they're in? I'm running PermissionsEx and the only prefix that went through is the custom one that was set manually.

      also I can't seem to get the widgets to appear, any ideas/troubleshooting you can give me?

      thanks for an awesome plugin 🙂

      posted in NodeBB Plugins
      _
      _axe
    • RE: [nodebb-plugin-minecraft-integration] Minecraft Integration!

      @yariplus Works great!! thank you. I ended up having to use localhost:4567 because they're on the same machine.

      posted in NodeBB Plugins
      _
      _axe
    • admin panel doesn't scroll properly

      does anyone know how to fix this?
      image

      posted in General Discussion
      _
      _axe
    • RE: [nodebb-plugin-minecraft-integration] Minecraft Integration!

      what do i set the socketio address as? nothing i try works. I get EngineIOException: xhr poll error. thanks

      posted in NodeBB Plugins
      _
      _axe
    • RE: [nodebb-plugin-rss] RSS Feed plugin

      hey, i've installed the plugin on my nodebb v1.0.3 and reloaded and restarted the forum, but it's not showing up in my Plugins list. help?

      Edit: OK, i downgraded to 0.3.8 and now it shows. bug, maybe?

      Edit Edit: Any way to "force" refresh the feed to test it?

      posted in NodeBB Plugins
      _
      _axe
    • RE: [nodebb-plugin-custom-pages] Custom Static pages for NodeBB

      How would I upload a javascript file (typed.js) to use in a custom page?

      posted in NodeBB Plugins
      _
      _axe
    • is there an option to change ownership of guest posts?

      i know this is a vague question, and one that's probably solved by me re-importing my forum; however, I was wondering if there is a good way for me to claim ownership of the "Guest" posts from nodebb (or changing the database in redis!).

      I recently imported my forum from Discourse and everything works great, and my users have already started using nodebb--i'd hate to have to flush it and re-import it again just so I can re-claim ownership of my posts. None of the other posts have problems, I'm guessing because of my existing admin account.

      I'm willing to mess around with redis and write a script or small java application with jedis (the latter would be easier for me) to circumvent a reset of my forum. However, I am a complete noob with redis 😖

      Can someone lead me on the right track?

      posted in Technical Support
      _
      _axe
    • RE: headers already sent

      aye, the first error that i had was causing the problem. i fixed the issue with redis, and everything else fell into place.

      posted in Technical Support
      _
      _axe
    • headers already sent

      i really can't find anything about this, so i'm posting a second question today... 😞

      I haven't been able to run nodebb yet, i go through the setup and then start it with ./nodebb start, but it doesn't start. anyone know how to fix this? 😁

      [cluster] Child Process (15747) has exited (code: 1, signal: null)
      [cluster] Spinning up another process...
      21/7 18:07 [15759] - info: Time: Tue Jul 21 2015 18:07:55 GMT-0400 (EDT)
      21/7 18:07 [15759] - info: Initializing NodeBB v0.7.1
      21/7 18:07 [15759] - info: NodeBB Ready
      21/7 18:07 [15759] - info: NodeBB is now listening on: 0.0.0.0:4567
      21/7 18:07 [15759] - error: /admin
      Error: MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.
      at ReplyParser.<anonymous> (/home/axel/NodeBB-NodeBB-65a349f/node_modules/redis/index.js:305:31)
      at ReplyParser.emit (events.js:95:17)
      at ReplyParser.send_error (/home/axel/NodeBB-NodeBB-65a349f/node_modules/redis/lib/parser/javascript.js:296:10)
      at ReplyParser.execute (/home/axel/NodeBB-NodeBB-65a349f/node_modules/redis/lib/parser/javascript.js:181:22)
      at RedisClient.on_data (/home/axel/NodeBB-NodeBB-65a349f/node_modules/redis/index.js:534:27)
      at Socket.<anonymous> (/home/axel/NodeBB-NodeBB-65a349f/node_modules/redis/index.js:91:14)
      at Socket.emit (events.js:95:17)
      at Socket.<anonymous> (stream_readable.js:748:14)
      at Socket.emit (events.js:92:17)
      at emitReadable
      (_stream_readable.js:410:10)
      21/7 18:07 [15759] - error: Error: Can't set headers after they are sent.
      at ServerResponse.OutgoingMessage.setHeader (http.js:689:11)
      at ServerResponse.header (/home/axel/NodeBB-NodeBB-65a349f/node_modules/express/lib/response.js:718:10)
      at ServerResponse.send (/home/axel/NodeBB-NodeBB-65a349f/node_modules/express/lib/response.js:163:12)
      at defaultFn (/home/axel/NodeBB-NodeBB-65a349f/src/middleware/middleware.js:304:10)
      at /home/axel/NodeBB-NodeBB-65a349f/src/middleware/middleware.js:351:7
      at /home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:160:6
      at /home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:180:4
      at Object.translator.load (/home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:209:5)
      at translateKey (/home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:178:14)
      at /home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:157:4
      Error: Can't set headers after they are sent.
      at ServerResponse.OutgoingMessage.setHeader (http.js:689:11)
      at ServerResponse.header (/home/axel/NodeBB-NodeBB-65a349f/node_modules/express/lib/response.js:718:10)
      at ServerResponse.send (/home/axel/NodeBB-NodeBB-65a349f/node_modules/express/lib/response.js:163:12)
      at defaultFn (/home/axel/NodeBB-NodeBB-65a349f/src/middleware/middleware.js:304:10)
      at /home/axel/NodeBB-NodeBB-65a349f/src/middleware/middleware.js:351:7
      at /home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:160:6
      at /home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:180:4
      at Object.translator.load (/home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:209:5)
      at translateKey (/home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:178:14)
      at /home/axel/NodeBB-NodeBB-65a349f/public/src/modules/translator.js:157:4
      21/7 18:07 [15759] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      21/7 18:07 [15759] - info: [app] Database connection closed.
      21/7 18:07 [15759] - info: [app] Web server closed to connections.
      21/7 18:07 [15759] - info: [app] Shutdown complete.
      3 restarts in 10 seconds, most likely an error on startup. Halting.

      posted in Technical Support
      _
      _axe

    Get Started

    • Product
    • Pricing

    Resources

    • Demo Site
    • Answers
    • Docs
    • Bug Bounty

    Company

    • About
    • Blog
    • Contact
    Start Free Trial
    Github Facebook Instagram Twitter
    © 2014 – 2022 NodeBB, Inc. — Made in Canada.
    • Terms
    • Privacy
    • GDPR
    • DMCA
    • Contact
    Menu
    • Terms
    • Privacy
    • GDPR
    • DMCA
    • Contact