• 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. armageddon
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 9
    • Best 1
    • Controversial 0
    • Groups 0

    armageddon

    @armageddon

    1
    Reputation
    314
    Profile views
    9
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    armageddon Unfollow Follow

    Best posts made by armageddon

    • RE: Max allowed file size setting not respected

      Edit: I just tried again, and everything is working as expected. Thx anyway! 🙂

      //
      The file (mp3) is part of a post, not a profile picture.

      posted in Technical Support
      A
      armageddon

    Latest posts made by armageddon

    • RE: Max allowed file size setting not respected

      Edit: I just tried again, and everything is working as expected. Thx anyway! 🙂

      //
      The file (mp3) is part of a post, not a profile picture.

      posted in Technical Support
      A
      armageddon
    • RE: Max allowed file size setting not respected

      Please correct me if i am wrong.. but i think i did..
      unless Maximum File Size in settings > uploads relates to something else?!

      posted in Technical Support
      A
      armageddon
    • [nodebb-plugin-audioplayer] time bubble missing z-index

      Hi, the sliding time bubble is cut of in FF.. probably due to incorrect z-index.
      It's not showing at all in Chrome.

      posted in NodeBB Plugins
      A
      armageddon
    • Max allowed file size setting not respected

      Hi guys,

      Trying to upload 6M file returns: Maximum allowed file size is 4096 kB - please upload a smaller file

      Nginx client_max_body_size 12M;
      NodeBB Maximum File Size: 12288

      posted in Technical Support
      A
      armageddon
    • RE: Category showing in backend but not in frontend

      Solved

      Turned out systemd could not write redis' pid file, hence the crashes/restarts.
      The missing category is probably a result of that.
      Reinstalled and everything is fine.

      Thx, keep up the good work! 🙂

      posted in Technical Support
      A
      armageddon
    • RE: Category showing in backend but not in frontend

      It's constantly crashing/losing connection/restarting.. oh, well.. I'm just gonna reinstall and get back to you if this happens again.

      Console:

      mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create nodebb.min.js:9:25710
      getPreventDefault() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen defaultPrevented. nodebb.min.js:2:0
      GET https://domain.tld/socket.io/ [HTTP/1.1 101 Switching Protocols 330ms]
      
      posted in Technical Support
      A
      armageddon
    • RE: Category showing in backend but not in frontend

      The category is there, I can access it manually (/category/8/2014)

      Syslog

      Apr 17 23:32:22 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc.
      Apr 17 23:32:22 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: This program comes with ABSOLUTELY NO WARRANTY.
      Apr 17 23:32:22 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: This is free software, and you are welcome to redistribute it under certain conditions.
      Apr 17 23:32:22 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m:
      Apr 17 23:32:22 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: Time: Sun Apr 17 2016 23:32:22 GMT+0200 (CEST)
      Apr 17 23:32:22 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: Initializing NodeBB v1.0.3
      Apr 17 23:32:23 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-plugin-emoji-one not found, skipping dependency check.
      Apr 17 23:32:23 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-plugin-emoji-extended not found, skipping dependency check.
      Apr 17 23:32:23 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-plugin-spam-be-gone not found, skipping dependency check.
      Apr 17 23:32:23 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-theme-lavender not found, skipping dependency check.
      Apr 17 23:32:23 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-theme-vanilla not found, skipping dependency check.
      Apr 17 23:32:32 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: NodeBB Ready
      Apr 17 23:32:32 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: Enabling 'trust proxy'
      Apr 17 23:32:32 vps69999 nodebb[372]: 17/4 23:32 [372] - #033[32minfo#033[39m: NodeBB is now listening on: 0.0.0.0:4567
      Apr 17 23:33:42 vps69999 systemd[1]: redis-server.service start operation timed out. Terminating.
      Apr 17 23:33:42 vps69999 redis[368]: User requested shutdown...
      Apr 17 23:33:42 vps69999 redis[368]: Calling fsync() on the AOF file.
      Apr 17 23:33:42 vps69999 redis[368]: Saving the final RDB snapshot before exiting.
      Apr 17 23:33:42 vps69999 redis[368]: DB saved on disk
      Apr 17 23:33:42 vps69999 redis[368]: Removing the pid file.
      Apr 17 23:33:42 vps69999 redis[368]: Redis is now ready to exit, bye bye...
      Apr 17 23:33:42 vps69999 systemd[1]: Failed to start Redis Datastore Server.
      Apr 17 23:33:42 vps69999 systemd[1]: Unit redis-server.service entered failed state.
      Apr 17 23:33:42 vps69999 redis[405]: You requested maxclients of 10000 requiring at least 10032 max file descriptors.
      Apr 17 23:33:42 vps69999 redis[405]: Redis can't set maximum open files to 10032 because of OS error: Operation not permitted.
      Apr 17 23:33:42 vps69999 redis[405]: Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
      Apr 17 23:33:42 vps69999 redis[405]: Redis 3.0.7 (00000000/0) 64 bit, standalone mode, port 6379, pid 405 ready to start.
      Apr 17 23:33:42 vps69999 redis[405]: WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
      Apr 17 23:33:42 vps69999 redis[405]: Server started, Redis version 3.0.7
      Apr 17 23:33:42 vps69999 redis[405]: DB loaded from append only file: 0.022 seconds
      Apr 17 23:33:42 vps69999 redis[405]: The server is now ready to accept connections on port 6379
      Apr 17 23:35:12 vps69999 systemd[1]: redis-server.service start operation timed out. Terminating.
      Apr 17 23:35:12 vps69999 redis[405]: User requested shutdown...
      Apr 17 23:35:12 vps69999 redis[405]: Calling fsync() on the AOF file.
      Apr 17 23:35:12 vps69999 redis[405]: Saving the final RDB snapshot before exiting.
      Apr 17 23:35:12 vps69999 redis[405]: DB saved on disk
      Apr 17 23:35:12 vps69999 redis[405]: Removing the pid file.
      Apr 17 23:35:12 vps69999 redis[405]: Redis is now ready to exit, bye bye...
      Apr 17 23:35:12 vps69999 systemd[1]: Failed to start Redis Datastore Server.
      Apr 17 23:35:12 vps69999 systemd[1]: Unit redis-server.service entered failed state.
      Apr 17 23:35:13 vps69999 nodebb[372]: 17/4 23:35 [372] - #033[31merror#033[39m: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED 127.0.0.1:6379
      Apr 17 23:35:13 vps69999 nodebb[372]: at Object.exports._errnoException (util.js:890:11)
      Apr 17 23:35:13 vps69999 nodebb[372]: at exports._exceptionWithHostPort (util.js:913:20)
      Apr 17 23:35:13 vps69999 nodebb[372]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1059:14)
      Apr 17 23:35:13 vps69999 systemd[1]: nodebb.service: main process exited, code=exited, status=1/FAILURE
      Apr 17 23:35:13 vps69999 nodebb[412]: kill: invalid argument S
      Apr 17 23:35:13 vps69999 nodebb[412]: Usage:
      Apr 17 23:35:13 vps69999 nodebb[412]: kill [options] <pid> [...]
      Apr 17 23:35:13 vps69999 systemd[1]: nodebb.service: control process exited, code=exited status=1
      Apr 17 23:35:13 vps69999 systemd[1]: Unit nodebb.service entered failed state.
      Apr 17 23:35:13 vps69999 nodebb[412]: Options:
      Apr 17 23:35:13 vps69999 nodebb[412]: <pid> [...] send signal to every <pid> listed
      Apr 17 23:35:13 vps69999 nodebb[412]: -<signal>, -s, --signal <signal>
      Apr 17 23:35:13 vps69999 rsyslogd-2007: action 'action 17' suspended, next retry is Sun Apr 17 23:35:43 2016 [try http://www.rsyslog.com/e/2007 ]
      Apr 17 23:35:13 vps69999 nodebb[412]: specify the <signal> to be sent
      Apr 17 23:35:13 vps69999 nodebb[412]: -l, --list=[<signal>] list all signal names, or convert one to a name
      Apr 17 23:35:13 vps69999 nodebb[412]: -L, --table list all signal names in a nice table
      Apr 17 23:35:13 vps69999 nodebb[412]: -h, --help display this help and exit
      Apr 17 23:35:13 vps69999 nodebb[412]: -V, --version output version information and exit
      Apr 17 23:35:13 vps69999 nodebb[412]: For more details see kill(1).
      Apr 17 23:35:13 vps69999 redis[416]: You requested maxclients of 10000 requiring at least 10032 max file descriptors.
      Apr 17 23:35:13 vps69999 redis[416]: Redis can't set maximum open files to 10032 because of OS error: Operation not permitted.
      Apr 17 23:35:13 vps69999 redis[416]: Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
      Apr 17 23:35:13 vps69999 redis[416]: Redis 3.0.7 (00000000/0) 64 bit, standalone mode, port 6379, pid 416 ready to start.
      Apr 17 23:35:13 vps69999 redis[416]: WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
      Apr 17 23:35:13 vps69999 redis[416]: Server started, Redis version 3.0.7
      Apr 17 23:35:13 vps69999 redis[416]: DB loaded from append only file: 0.010 seconds
      Apr 17 23:35:13 vps69999 redis[416]: The server is now ready to accept connections on port 6379
      Apr 17 23:35:23 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc.
      Apr 17 23:35:23 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: This program comes with ABSOLUTELY NO WARRANTY.
      Apr 17 23:35:23 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: This is free software, and you are welcome to redistribute it under certain conditions.
      Apr 17 23:35:23 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m:
      Apr 17 23:35:23 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: Time: Sun Apr 17 2016 23:35:23 GMT+0200 (CEST)
      Apr 17 23:35:23 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: Initializing NodeBB v1.0.3
      Apr 17 23:35:24 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-plugin-emoji-one not found, skipping dependency check.
      Apr 17 23:35:24 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-plugin-emoji-extended not found, skipping dependency check.
      Apr 17 23:35:24 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-plugin-spam-be-gone not found, skipping dependency check.
      Apr 17 23:35:24 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-theme-lavender not found, skipping dependency check.
      Apr 17 23:35:24 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[33mwarn#033[39m: [meta/dependencies] Bundled plugin nodebb-theme-vanilla not found, skipping dependency check.
      Apr 17 23:35:34 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: NodeBB Ready
      Apr 17 23:35:34 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: Enabling 'trust proxy'
      Apr 17 23:35:34 vps69999 nodebb[419]: 17/4 23:35 [419] - #033[32minfo#033[39m: NodeBB is now listening on: 0.0.0.0:4567

      posted in Technical Support
      A
      armageddon
    • RE: Category showing in backend but not in frontend

      @yariplus

      Version: 1.0.3

      NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc.
      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).
      
      17/4 02:42 [407] - ^[[32minfo^[[39m: Time: Sun Apr 17 2016 02:42:13 GMT+0200 (CEST)
      17/4 02:42 [407] - ^[[32minfo^[[39m: Initializing NodeBB v1.0.3
      17/4 02:42 [407] - ^[[32minfo^[[39m: [plugins/emoji-one] Initial startup detected. Downloading emojione assets...
      17/4 02:42 [407] - ^[[32minfo^[[39m: NodeBB Ready
      17/4 02:42 [407] - ^[[32minfo^[[39m: Enabling 'trust proxy'
      17/4 02:42 [407] - ^[[32minfo^[[39m: NodeBB is now listening on: 0.0.0.0:4567
      17/4 02:42 [407] - ^[[32minfo^[[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      17/4 02:42 [407] - ^[[32minfo^[[39m: [app] Database connection closed.
      17/4 02:42 [407] - ^[[32minfo^[[39m: [app] Web server closed to connections.
      17/4 02:42 [407] - ^[[32minfo^[[39m: [app] Shutdown complete.
      [cluster] Child Process (407) has exited (code: 0, signal: null)
      
      NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc.
      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).
      
      17/4 02:45 [353] - ^[[32minfo^[[39m: Time: Sun Apr 17 2016 02:45:02 GMT+0200 (CEST)
      17/4 02:45 [353] - ^[[32minfo^[[39m: Initializing NodeBB v1.0.3
      17/4 02:45 [353] - ^[[32minfo^[[39m: [plugins/emoji-one] Initial startup detected.     Downloading emojione assets...
      17/4 02:45 [353] - ^[[32minfo^[[39m: NodeBB Ready
      17/4 02:45 [353] - ^[[32minfo^[[39m: Enabling 'trust proxy'
      17/4 02:45 [353] - ^[[32minfo^[[39m: NodeBB is now listening on: 0.0.0.0:4567
      17/4 02:48 [353] - ^[[32minfo^[[39m: [app] Shutdown (SIGTERM/SIGINT) Initialised.
      17/4 02:48 [353] - ^[[32minfo^[[39m: [app] Database connection closed.
      17/4 02:48 [353] - ^[[32minfo^[[39m: [app] Web server closed to connections.
      17/4 02:48 [353] - ^[[32minfo^[[39m: [app] Shutdown complete.
      [cluster] Child Process (353) has exited (code: 0, signal: null)
      

      That's the full output.log
      Please tell me if you need anything else

      posted in Technical Support
      A
      armageddon
    • Category showing in backend but not in frontend

      Hi guys,

      the title says it all.

      I added a subcategory but it is not showing up in the frontend though it's visible in the backend.

      Thanks in advance!

      posted in Technical Support
      A
      armageddon

    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