Cloudron Forum

Hi @james, yes, it is a custom internal Next.js app where I use proxyAuth as the auth wall. I am using proxyAuth to expose certain endpoints for webhooks and publicly accessible APIs. I don't currently have OIDC support in this app.

https://docs.cloudron.io/packaging/addons#proxyauth

Is there a way to specify multiple paths to include/exclude from the auth wall?

"proxyAuth": { "path": "!/webhooks,"!/api" }

OR

"proxyAuth": { "path": ["!/webhooks","!/api"] }

Hi @girish, please let me know if this is not what you expected, so I can work on giving you what you need. I also had a live deployment and wanted to send you credentials but this forum doesn't allow me to start a chat with you.

https://drive.google.com/file/d/1b6Dm5Nf9lThiifTS2akGgBgL1eq8gtKZ/view?usp=drive_link

Please download it from here. I was able to launch it as a cloudron app after npm install and creating a docker image. Please let me know if this works.

You can see the cloudron auth headers at: https://<cloudron app domain>/api/headers

@girish next.js does support RP initiated logout. Can I use this to log out the user from the dashboard, or clear the session? Thank you!

This is a custom app based I am packaging on react-admin. I am currently just redirecting the user to {app}/logout on clicking logout. Any way to enable it for just the custom app?

I'm using a custom Next.js app deployed on Cloudron and leveraging Cloudron's proxy auth for authentication. The challenge I'm facing is that when users log out of my app, they are not fully logged out of the Cloudron SSO session. As a result, they can get automatically logged back in without re-entering credentials because the Cloudron dashboard session is still active.

I tried to find a global logout endpoint for Cloudron to fully end the session but didn't have success with it. I'm looking for guidance on whether there's a proper Cloudron-supported way to handle a full logout (so that users really have to log in again) or if there's a recommended way to configure session timeouts or customize the login flow to avoid automatic re-logins.

@girish What is the latest on OIDC logout support?

I am seeing the same issue. How did you fix it?

@scooke hope you see this before @luckow deletes it tomorrow. lol

How about the ability to sort in the app store? So we can sort by date added or date stabilized or so. That would be useful when we just want to get up to date with what Cloudron staff has packaged recently.

Just curious. My forum with like 2 users and not much activity crashed due to OOM with 2GB memory, I am wondering for the Cloudron forum's activity, how much memory have you allocated?

I was able to fix this by deactivating all the plugins after the yarn remove from above and then restarting. So I guess its an upstream issue.

After I uninstall a package and restart NodeBB(from Cloudron), the plugin keeps reinstalling again.

On restart, these are the relevant logs:

nodebb-plugin-reactions
Nov 03 11:36:56
Nov 03 11:36:56
...
Nov 03 11:36:56" is active but not installed.

Output of ./nodebb plugins after restart:

 * nodebb-plugin-reactions@0.0.4 (installed, disabled)

Uninstall using the terminal:

/usr/local/bin/gosu cloudron:cloudron yarn remove nodebb-plugin-reactions

Also tried to reset first before uninstalling:

./nodebb reset -p nodebb-plugin-reactions

Is restarting the app through Cloudron the same as Rebuild and Restart?

@girish Sorry about this. I was using the backup from another app by mistake. Please close this.

@girish Already did, thank you. Sent from same email as on here.

@girish Cloudron version: v7.6.0 (Ubuntu 22.04.3 LTS)
I did see a post here about the timeout issue.
Yes, after scaling up mongodb, I tried to restart it and then import.

I tried with 2GB but still have the same issue. How do I verify that the memory limit is the issue? I don't see any error in MongoDB logs.