Cloudron Forum

@Joseph , I have upgrade to Cloudron 10.0.4. Any pointer or advice for how to configure maxMemoryPolicy ?

I poked around Cloudron --> System --> Services --> the three dots ... --> Configure but don't see anything that would let me configure maxMemoryPolicy.

@Joseph , yes, waiting for Cloudron 10 makes sense in this case, thank you!

@Joseph , you make a good point and I have follow up on this topic at https://community.nodebb.org/topic/19410/csrf-invalid-login-issue-with-nodebb-4.14.5/

That said, one suggestion received from there is to "check your redis config and make sure it has an eviction policy set to something like volatile-lru" ... for this, it seems I need to come back and ask a question here because I don't seem able to find my redis.conf file in the usual places like /etc/redis.conf or /etc/redis/redis.conf, so I come back here to ask if maybe the folks who "package" up NodeBB for Cloudron can clue me into where I can find redis.conf in the NodeBB package for Cloudron. Thanks in advance!

Update: Flushing Redis worked ... now the system allows logins again. The cost is everyone needs to re-login (not ideal, but tolerable).

Now I would like to investigate what caused Redis' memory to fill up in the first place.

One working theory is that we're being targeted by bots, but the number of logins I can see are rather modest and there has been no "spike" in those stats. We do have "guess visitors" and "guess page views" (also no "spike" on those stats) ... so if any one here knows the answer, my question now is this:

• Does NodeBB generate new Redis entries for "guess visits" or "guess page views"?
• Anything else you can think of that would cause NodeBB to add entries to Redis?

@Joseph , my list of "enabled" plagins below:

# ./nodebb plugins | grep enabled
        * @nodebb/nodebb-plugin-reactions@3.0.1 (installed, enabled)
        * nodebb-plugin-btn-spoilers@0.4.1 (installed, enabled)
        * nodebb-plugin-composer-default@11.0.8 (installed, enabled)
        * nodebb-plugin-dbsearch@7.0.0 (installed, enabled)
        * nodebb-plugin-embed@3.0.19 (installed, enabled)
        * nodebb-plugin-emoji@6.0.14 (installed, enabled)
        * nodebb-plugin-emoji-android@4.1.1 (installed, enabled)
        * nodebb-plugin-markdown@13.2.6 (installed, enabled)
        * nodebb-plugin-mentions@5.0.0 (installed, enabled)
        * nodebb-plugin-twitter-netdata@1.0.0 (installed, enabled)
        * nodebb-rewards-essentials@1.0.3 (installed, enabled)
        * nodebb-theme-harmony@3.1.9 (installed, enabled)
        * nodebb-widget-essentials@8.0.4 (installed, enabled)

@James , yes, I see the line "trust-proxy" : true in my config.json file.

Another suspect is some sort of Redis "memory full" condition preventing new logins from happening. When I check Redis memory usage, I see these two lines:

used_memory:257978864
maxmemory:257949696

used_memory seems to have exceeded maxmemory a bit; but at this point I do not know what's filling up Redis memory.

Hello, I am seeing "error=csrf-invalid" with a NodeBB installation recently upgraded to 4.14.5.
The installation is NodeBB 4.14.5 (package version 2.31.5) running in Cloudron 9.2.0 on Ubuntu 24.04.4.
Existing sessions continue to work; observed issues are:

• All attempts to login result in "error=csrf-invalid" and the message "Login Unsuccessful // We were unable to log you in, likely due to an expired session. Please try again"
• NodeBB users with "admin" privilege cannot actually get to the admin panel (clicking on the "admin" icon takes the user to the /user/admin page rather than the /admin page)

Simple things like "(on the server side) let's restart the app and see what happens" and "(on the client side) let's clear all browser cache/cookies/history/data" and "let's try this on different browsers (Safari/Brave/Chrome)" have been tried to no avail.

Any advice for what else I should try?

Newbie questions here ...

1. How do I file ticket for this issue?
2. How/what do I monitor to know when this issue is resolved (such that I can reenable Auto-Update again)?

I am observing similar issue after upgrading to NodeBB package version 2.14.x.
Among error logs I am seeing are "ERR!" logs about not being able to resolve the nodebb-plugin-emoji plugins, and the application being "not responding."

Had to downgrade to NodeBB package version 2.13.4 to resolve the error and get the application back up and running.

Funny thing is, if I "upgrade" only to package version 2.14.0, I get only "WARN" logs about not being able to resolve the nodebb-plugin-emoji plugins, and the application will eventually get up and run. But if I take one more step to upgrade to 2.14.1, then the "ERR!" logs come back and the application will be stuck "not responding" again. Downgrading from 2.14.1 back to 2.14.0 did not help -- I get the same "ERR!" logs as mentioned above and the application remains "not responding." I have to downgrade back to 2.13.4 to get out of this hole.

For now, I will disable auto-update and hope that smarter people figure this out and put out a revised NodeBB 2.14.x package that won't have the same or similar issue. (Not really sure how this works ... if 2.14.0 and 2.14.1 really have issues, I'm hoping they will be removed such that auto-update will skip over them and move on to a working update when one becomes available.)