Community

Heroku deployment: Internal Server Error (no idea what's going on)

Technical Support

Suggested Topics

  • C

    Browser console error

    Technical Support
    0 Votes
    2 Posts
    222 Views
    barisB

    @flarum-türkiye said in :

    https://domain.ltd/plugins/nodebb-plugin-markdown/styles/railscasts.css

    Seems like the file is missing on your installation, did you run ./nodebb build and try again? That url should return the correct css ie https://community.nodebb.org/plugins/nodebb-plugin-markdown/styles/railscasts.css

    The error you are seeing happens because our core 404 handler is returning text/plain when it can't find the css file.

  • N

    All links under Admin->Manage don't work

    Technical Support
    0 Votes
    12 Posts
    441 Views
    scottalanmillerS

    @nmeadows said in All links under Admin->Manage don't work:

    @gotwf I have found the culprit, and it has nothing to do with NodeBB, so I'm sorry to have bothered you.
    It ended up being our security team turned on web filtering rule on our load balancer that filters out certain URL paths that have admin/manage/etc in the path. The idea being to filter our administration pages and force the use of VPN to get to those paths. It's a fine idea, but I was not informed of that change.

    Thank you for your help.

    Better to bother us and get it fixed than to not bring it up and not 🙂 Glad that you got it figured out.

  • H

    NodeBB v1.0.3 won't start, error: undefined

    Technical Support
    0 Votes
    2 Posts
    938 Views
    H

    @h7 tried on a different Debian 7 (Wheezy) server, to make sure this is a common issue:

    Node.js v4.2.2 Redis server v=3.2.11 NodeBB v1.0.3

    NodeBB installs again, without errors but the log comes back with the exact same [2458] - error: undefined

    npm rm nodebb-plugin-emoji-one npm install [email protected]

    fixed that error, now:

    info: Time: Sun Oct 08 2017 04:59:32 GMT+0300 (MSK) info: Initializing NodeBB v1.0.3 [outdated] nodebb-plugin-emoji-one installed v1.1.4, package.json requires 1.1.0 warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them: warn: ./nodebb upgrade [cluster] Child Process (6503) has exited (code: 0, signal: null)

    OK, removing the plugin npm rm nodebb-plugin-emoji-one and ./nodebb start worked, NodeBB v1.0.3 running, still can't log-in:

    warn: [meta/dependencies] Bundled plugin nodebb-plugin-emoji-one not found, skipping dependency check. [minifier] file not found, node_modules/socket.io-client/socket.io.js [minifier] file not found, node_modules/socket.io-client/socket.io.js info: NodeBB Ready info: Enabling 'trust proxy' info: NodeBB is now listening on: 0.0.0.0:4567 error: /login invalid csrf token error: /login invalid csrf token

    using older versions of socket.io:

    npm remove socket.io npm remove socket.io-client npm install [email protected] npm install [email protected]

    did the trick, NodeBB v1.0.3 running and ready for myBB to NodeBB transition

  • M

    How to auto start nodebb on ubuntu server reboot

    Technical Support
    0 Votes
    12 Posts
    3038 Views
    A

    In nodebb's case it will just need the A (or E... which will be nginx. Don't ask me why the E stands for nginx, as that is how they named the stack. Maybe because it is pronounced engine-x) and the M... for mongodb

  • Moritz FriedrichM

    CSRF error when logging in after URL change

    Technical Support
    0 Votes
    6 Posts
    3163 Views
    julianJ

    @Moritz-Friedrich said:

    Weird enough, I just realized that at the old subdomain (as a CNAME) logging in is still possible...

    Default this is not set to anything, so this doesn't need to be set... afaik

Copyright © 2023 NodeBB | Contributors