Community

requests to a certain admin url results in 504 gateway timeout

Unsolved Technical Support
  • Teresa-Hale-DHQT

    The url is /admin/manage/admins-mods.
    I'm behind a reverse proxy (nginx), if that helps.
    In /var/log/nginx/error.log I see:

    2022/10/31 17:08:56 [error] 605264#605264: *1157 upstream timed out (110: Connecti
on timed out) while reading response header from upstream, client: ::1, server: ,
request: "GET /forum/admin/manage/admins-mods HTTP/1.1", upstream: "http://127.0.0
.1:4567/forum/admin/manage/admins-mods", host: "localhost:4000"

    nodebb is 2.5.7
    node is 18.6.0

    0
  • barisB

    How many categories do you have? Are there any categories that might me mistakenly creating cycles as in parent A => parent B => parent A that would cause a lockup.

    Teresa-Hale-DHQT 1 Reply
    0
  • Teresa-Hale-DHQT

    @baris well, when I went to check, nothing appears.

    cb541ec6-4b7e-4abe-9d27-10b9beae1fc7-image.png

    There's also nothing helpful in the log;

    2022-11-01T16:39:48.177Z [41gKFtogHYuTLgtmff2zbx9hk7DWS8VB612gDjf1YFPsfT66jV4UFCBNJSsUKKBpwf9y4CunA1UoucxSkm8NLtmRFxDFATcas of v1.15.3, and slated for removal in v2.1.0. Please use response:router.page instead. The following plugins are still listening for this hook:
  * nodebb-plugin-write-api
2022-11-01T16:39:48.248Z [4567/13736] - info: [session-sharing] Settings OK
2022-11-01T16:39:48.254Z [4567/13736] - info: [plugins/spam-be-gone] Settings loaded
2022-11-01T16:39:48.344Z [4567/13736] - info: [api] Adding 0 route(s) to `api/v3/plugins`
2022-11-01T16:39:48.369Z [4567/13736] - info: [router] Routes added
2022-11-01T16:39:48.416Z [4567/13736] - info: 🎉 NodeBB Ready
2022-11-01T16:39:48.418Z [4567/13736] - info: 🤝 Enabling 'trust proxy'
2022-11-01T16:39:48.431Z [4567/13736] - info: 📡 NodeBB is now listening on: 127.0.0.1:4567
2022-11-01T16:39:48.448Z [4567/13736] - info: 🔗 Canonical URL: https://www.url.com/forum
    0
  • barisB

    Is your forum public so we can take a look? Can you access individual categories with this url /admin/manage/categories?cid=<replace with category id>?

    Teresa-Hale-DHQT 1 Reply
    0
  • Teresa-Hale-DHQT

    @baris strangely enough, the category list loads now! And it doesn't look like there's any circularness in the list.

    1c811ac6-83ea-4dd2-b1d9-3af633f45e90-image.png

    Still, trying to manage the admin group via /admin/manage/groups/administrators or /admin/manage/admins-mods results in a gateway timeout. I've also enabled verbose logging, which displays this upon visiting either of these two urls:

    x.x.x.x - - [01/Nov/2022:17:12:10 +0000] "GET /forum/admin/manage/admins-mods HTTP/1.1" - - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0"

    Now there's no response code. Strange.

    1

Suggested Topics

  • D

    Azure WebSockets + NodeBB + Node.js Proxy

    Technical Support
    0 Votes
    6 Posts
    667 Views
    julianJ

    Definitely would appreciate updates to our documentation so you can help others facing similar problems! 😄 Glad you're on your way.

  • setkyarS

    Looks like your connection to NodeBB was lost, please wait while we try to reconnect.

    Technical Support
    0 Votes
    4 Posts
    2346 Views
    julianJ

    The common causes for a session mismatch error are usually one of the following:

    1. Mis-configured URL parameter in your config.json file

    If you have a misconfigured url value in your config.json file, the cookie may be saved incorrectly (or not at all), causing a session mismatch error. Please ensure that the link you are accessing your site with and the url defined match.

    2. Improper/malformed cookieDomain set in ACP

    Sometimes admins set this value without realising that they probably don't need to set it at all. The default is perfectly fine. This is what the config looks like:

    Cookie Domain setting

    If this is set, you'll want to revert the setting by editing your database directly:

    Redis: hdel config cookieDomain
    MongoDB: db.objects.update({ _key: "config" }, { $set: "cookieDomain": "" });

    3. Missing X-Forwarded-Proto header from nginx/apache

    If you are using a reverse proxy, you will need to have nginx pass a header through to NodeBB so it correctly determines the correct cookie secure property.

    In nginx, you will need to add the directive like so:

    location / { ... proxy_set_header X-Forwarded-Proto $scheme; ... }
  • M

    "Failed login attempt, please try again. Invalid User Data" when attempting login as admin

    Technical Support
    1 Votes
    21 Posts
    5903 Views
    ?

    @Joykiller there is no issue setting NodeBB up as root. I always do it like that and later chown the installation to another user. Then I start NodeBB over Supervisoe from that non-root user.

    Update:
    All issues resolved. 😛
    Re-setup everything.

  • Robin BR

    login forbidden, even for admin

    Technical Support
    0 Votes
    7 Posts
    2809 Views
    Robin BR

    now the error is gone but my complete forum is down 😞

    nodebb is running (no errors only a few plugin warnings) nodebb is up2date redis is running nginx is running fine (all other sites on server are running fine as well)

    when i check my site it says: 502, bad gateway
    when i check ip:4567 (no connection)

    ranning out of ideas here 😞

  • P

    nodebb and wordpress problems

    General Discussion
    0 Votes
    5 Posts
    2975 Views
    A

    @Rahul-Ramesh said:

    /her. 👯

    I blame the Avatar. 😆

Copyright © 2023 NodeBB | Contributors