Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
A

Axtremus

@Axtremus
Unfollow Follow
About
Posts
8
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • CSRF-Invalid error Cannot Login after upgrade to package 2.31.5
    A Axtremus
    NodeBB

    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?


  • CSRF-Invalid error Cannot Login after upgrade to package 2.31.5
    A Axtremus
    NodeBB

    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?

  • CSRF-Invalid error Cannot Login after upgrade to package 2.31.5
    A Axtremus
    NodeBB

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


  • CSRF-Invalid error Cannot Login after upgrade to package 2.31.5
    A Axtremus
    NodeBB

    @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. 🤷

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search