Cloudron Forum

Same here, it’s not responding after a while even with the cron command

@scooke said in Cannot make a user admin ("Allow this user to manage the server"):

At least one person did exactly this: selected a user, clicked the box for "Allow this user to manage the server", and it worked. HOWEVER, the new user they created was given the name "admin", the previous initial admin user having had it's name changed from "admin" to something else, thereby freeing up the name "admin", I guess.

That's not what happened to me. No new user was added. I have no user called "admin".

Perhaps that might've happened in a non-Cloudron set-up or an earlier version or something 🤷

@scooke said in Cannot make a user admin ("Allow this user to manage the server"):

A post here, https://jellyfin.org/docs/general/installation/truenas#users--permissions, mentions groups and users... I wonder if the User you want to make Manager needs to also be a Manager/Admin type within Cloudron, first, assuming the two overlap/are the same.

I don't think there is any overlap. My admin user isn't even a Cloudron user.

For now I'm just not going to worry about it. It would've made my life marginally easier if I could've had multiple admins, but it's no big deal if I can't (and, actually, the account I was trying to make an admin is the one the auto-logs-in to my tv, which the kids use, so I'm kinda sorta glad that didn't work!)

But thanks for investigating 🙂

I cleared browser data and now it's working again.

@girish said in Update App Store User Management filter to include Login with Cloudron OpenID:

@jdaviescoates do you mean to separate OIDC and LDAP ?

Yes

This is now fixed with https://git.cloudron.io/platform/box/-/commit/876fd218afb15c8e818aa6edc6386637611973d3

Latest app info is:

image.png

Right, when we moved to the new CI system, we had to unlist this. We could not manage to update the app. But the killer reason is that they moved everything now to Discord. There is no issue tracker or any channel . https://github.com/SickChill/SickChill?tab=readme-ov-file#important-notice . Unfortunately, this doesn't work for us from a maintenance pov. I will make a sticky here.

You can see it here - https://git.cloudron.io/apps/synapse-app/-/merge_requests/10 . The tests are failing, we have to investigate. The update won't work with Element X though, I am pretty sure 🙂

@jdaviescoates I should have been clearer... I meant the sliding sync webapp got obsoleted and the repo was archived. TBH, I don't really know if the protocol / implementation was merged in a compatible way.

In OpenID there is no well supported way to log out users from services which used the OpenID for authentication (in Cloudron case the apps). Those app have their own session and session handling. So there is mostly likely no way around this unless an app would start using OAuth2 access and refresh tokens (but implementation of that was spotty in the past which sparked OpenID connect in the first place)

For a start if you logout of the dashboard, subsequent app logins (from a state where the app has no login session) then Cloudron will prompt you to login with a username. If that is not happening the Oidc session was still alive.

The best way I found was to use container tabs in like firefox and probably other browsers, which maintain isolated sessions. This is also how I use other services like Digitalocean where we have multiple accounts with different roles.

You may have to create the /home/yellowtent/boxdata/custom_pages directory if it doesn't exist.

If anyone else is getting mildly annoyed by this I've just discovered that if you actually enter something into the Name field and save it then it stops happening (even if you then go and delete what is in that field and save again).

@andreasdueren yes exactly, that's the bug. They are yet to add OIDC support in the Element X apps . the one you linked is the iOS app, the one I linked earlier was for the android app.

@girish I'm not too sure of "how" you referral program had affected your Stripe account, however maybe you should look into the "affiliate program" side of things?

According to my experience I believe that your "referral program" had no attraction simply because of what you offered, in exchange to referring new clients.

Really, "referral or "affiliate or "partner marketing" is almost a 'science' and not something one should just guess. To make it really work one should know what one's talking about, and if not get advice and be informed on the subject. before any implementation.

Of course, any kind of 'MSP' or 'reseller' program or in the like, you name it, is also a viable way to go that goes along with the nature of the product. 🙂

@avatar1024 said in How to setup Hetzner Storage Box using SSHFS:

I've had no more issue restoring using sshfs

Good to know, thanks!

This was just a bug, sorry it slipped through! Already fixed for next release.

@jdaviescoates said in Post update to 8.0.3 one of my PeerTube instances is Not Responding:

But it's a bit odd that bridport.tv is still running fine (that also uses OIDC)

I guess the issue was actually an incompatibility with that plugin and other plugins, not with the OIDC plugin itself.

Because I managed to use to the File Manager to edit /app/data/storage/plugins/package.json to remove all references to other plugins and now uniteddiversity.tv is back up and running again! 🙂

I now only have this (which I copy/ pasted from the running bridport.tv) :

{ "dependencies": { "peertube-plugin-auth-openid-connect": "0.1.1" } }

(Although for some odd reason after editing the file the owner had changed from 'cloudron' to 'root' so I just changed that back to 'cloudron).

Stupidly I didn't make a copy of previous package.json to easily know which plugins I was previously using... if I had I could turn them on one by one to find the culprit... I guess I could extract that info out of a backup, but I doubt I'll bother now...

So, the mounting is handled by the kernel and Cloudron as such has nothing to do with stability of the mount. Cloudron is really just a user space program.

You can find the mount systemd file in one of the mount files in /etc/systemd/system/*.mount . Maybe you can look for hints in dmesg (but often unmount information logs is not there)