Error Forbidden

General Discussion
  • I have a user complaining that when he tries to post using iphone he gets "Error Forbidden" however when he does the same post on a laptop its no problem.

    1437cc61-b7b3-4a73-9881-3bdd7dae8129-image.png

    Previously to upgrading to 1.16.2 this user was able to post using his iphone without issue.

    I don't have an iphone so I can't test or try to reproduce this, anyone have any ideas what would cause this error when trying to post with iphone using 1.16.2 ?

  • @dcook can you ask him to log out and log back in? If that doesn't work have him clear his cookies and cache.

  • @pitaj I had another user complain about the same "Error Forbidden" message when trying to post using a mobile phone.

    I asked him to logout of the forum and then log back in to the forum on his phone and now he is able to post without issue.

    Question: Why is this happening now? I have never had this error in years using NodeBB, how can I prevent this from happening to other users?

    Is this a known bug with 1.16.2? Should I roll back to 1.15 ?

  • @dcook Perhaps some caching issue w/some script somewhere along the line not firing?

    @PitaJ Perhaps related to the worker.js script not firing when using ff mult-containers that I mentioned to @julian a couple days back?

    Maybe some web cache somewhere along the line caching a script it should not?

    fwiw,; Just a "me too", that I have been experiencing a bit of strangeness as well as of late. For e.g., I had to click on "Reply" repeatedly before the composer dialog launched. And had to "Shift Refresh" before it would, wh/I chalked up to multi-containers but maybe related, eh?

  • Things seem to be working more normally now. I'd turned multi-container add-on off for a few days. During that time, seems there may have been an update cuz all my custom containers were gone when I re-enabled. Or did something change nodebb server side?

    worker.js still does not fire on every reload unless you do a full refresh but at least avatars, etc. display properly once again.

    Just an updated data point, for whatever it may be worth. ymmv-- ✌

  • Ok I had similar happen a day or so ago, sans error message.

    I eventually had to discarded the post entirely and start again. That worked. No need to log out from NodeBB (1.16.2), this was on Safari iOS 14.3 on iPhone.


Suggested Topics


  • 0 Votes
    2 Posts
    224 Views

    I think that function was removed, you might have some old code that is still calling it. What is your NodeBB version and the rest of the stack trace?

  • 0 Votes
    15 Posts
    8k Views

    @vinjdw @Marc-Boisvert-Dupras Keep in mind Kerberos authentication is default off, so if the module does not compile, this does not stop MongoDB (or NodeBB) from functioning correctly.

  • 0 Votes
    18 Posts
    7k Views

    @Ted said:

    If you'll start NodeBB and leave it running, I'll see if I can can connect to it and register a profile

    I can't this server is not open on internet, only in local.

  • MongoDB Error

    General Discussion
    0 Votes
    7 Posts
    3k Views

    I am also getting this issue

    [ezra@kiwidev community]$ node app.js info: NodeBB v0.4.2 Copyright (C) 2013-2014 DesignCreatePlay Inc. info: This program comes with ABSOLUTELY NO WARRANTY. info: This is free software, and you are welcome to redistribute it under certain conditions. info: info: Time: Mon May 12 2014 06:31:33 GMT+0400 (MSD) info: Initializing NodeBB v0.4.2 info: * using configuration stored in: /var/www/alternative-gaming/community/config.json info: * using mongo store at 127.0.0.1:28900 info: * using themes stored in: /var/www/alternative-gaming/community/node_modules Failed to load c++ bson extension, using pure JS version error: auth failed

    config.json

    { "base_url": "http://community.ag-aus.org", "port": "4680", "use_port": false, "secret": "XXX", "bind_address": "127.0.0.1", "database": "mongo", "mongo": { "host": "127.0.0.1", "port": "28900", "username": "XXX", "password": "XXX", "database": "XXX" }, "bcrypt_rounds": 12, "upload_path": "/public/uploads", "relative_path": "" }
  • 0 Votes
    4 Posts
    2k Views

    No need for that here. But maybe a plugin in the future 🙂