Cloudron Forum

Yeah well TBH I'd wait until 4.0.1 (or 4.0.2...?) to roll out, seems some teething pains on 4.0.0 which isn't unexpected. Bleeding edge!

@girish Mastodon 4.0.0 is GA!

https://github.com/mastodon/mastodon/releases/tag/v4.0.0

Are packages auto-deployed across all app installations or requires opt-in?

@girish Ohhh hmmm, I thought for sure I was able to log into other Mastodon instances using username only, but I must have been mistaken and/or confused with the original Cloudron install setup I had. Preferred this way if this is standard/OOB Mastodon user auth setup, so thanks again.

@girish Oh, I guess I wasn't getting your original point that "for external users, they can only login with email" and that being an "upstream issue" which I assume you mean the packaging configuration? Because yes, I've re-installed the app with the "Leave user management to the app" option selected, but yes those users can only log in via email address (which isn't optimal for a more public server setup). Any way to manually tweak a config to allow for username-based login?

@girish Hmm OK, well I'm rebuilding the app for external app user management vs. Cloudron so that may be the way to go for the type of use case I'm looking for... Thanks.

@jdaviescoates Hmmm, yeah you're right, that's not ideal. Looks like some places indicate it's a 7-day cooldown period, so would not really work too well unless you want to stay in the new home for a week, then migrate back... Also indicates "Your toots will not be moved, due to technical limitations." - not sure if that's a blocker as well. Wonder if you can export your entire account, rebuild the Cloudron app, then restore the account with the new user management setting applied? I'm about to nuke and rebuild my app, but it was a fresh instance so not losing anything of value... Good luck mate!

@jdaviescoates Sounds like I'm going to need to do the same thing, i.e. reinstall without integrated LDAP. Re: losing followers, wonder if you can migrate your account to another server, re-build your Mastodon app, then migrate back?

@girish To your question, I believe it was installed with Cloudron user management.

@jdaviescoates I'm wondering the same thing re: change of user management, as I think I installed the same way, but for an externally-created user can only log in via email address (not username). Do you have the same issue? Hope there is a way to change this after the fact, vs. recreating the app instance (though I fear that is what may need to be done...).

@nebulon Under Access Control/User management it states "This app is configured to authenticate with the Cloudron User Directory. This setting controls who can log in and use the app." and set for "Allow all users from this Cloudron" - so perhaps I've chosen the wrong option on install (if I want to allow any users to sign up w/o registering in Cloudron)?

@nebulon Yeah I would have thought so, but it's giving an error with just username as well. Any config that would only allow for email address to be used?

On a new Mastodon Cloudron instance, I've created a new admin user through the web interface (well, new user via web, then promoted to admin using tootctl), but can only log in using the email address, not the username (have tried "username", "@username", and "@username@url" to no avail) - gives an "Invalid E-mail address or password" error (but doesn't mention username).

Never mind, after a bit of poking around it seems DigitalOcean does not allow for port 25 outbound (at least not that I could find), so needed to configure external SMTP service (via SendGrid). Maybe there's a better/cheaper way to do this, if anyone has guidance on that happy to take it!

I have a new Mastodon instance set up using Cloudron in a DigitalOcean droplet, and the site is running and I've got myself configured as admin, but when trying to register the first test user, the confirmation/registration email is not going out. Any suggestions how/where to trace this?