Cloudron Forum

@sponch said in Problems with new NC 31.01: when uninstalling Talk app it appears again after Nextcloud restart. . you can disable turn . https://docs.cloudron.io/apps/#turn

there are also some posts from @d19dotca a while back about fine tuning spam rules

@sponch I seem to have chosen HLS over on https://uniteddiversity.tv and everything is playing fine for me there [image: 1738869030667-screenshot_20250206-190914_firefox.png] I'd guess I've got the same settings over on https://bridport.tv too

working now. thx

omg....just checked the DNS again.... the "webmail" record wasn't by cloudron.... it's directing to the hoster's web mailer (same that cloudron uses).... So for me: without installing a webmail app from the cloudron appstore this doesn't work, right? As I'm on free (at least with that instance) I've no free app anymore. Sorry...my mistake

Does upstream have any documentation on how to do this? If this would require to change app code as such, we would likely not support this, as it will break tested updates.

Good workflow! @Kubernetes said in AGH, Hetzner Firewall and Dynamic IP: I have whitelistet my ISP IP and update it manually when it changes. I think this is where the API will help if your IP changes a lot. I don't know if it applies to @sponch but in my home, the VPS only changes IP within a specific subnet. In the firewall, I just whitelist the subnet instead of a specific IP.

working great! Thanks @girish

Problem solved with 7.0 update (without interaction Full DL Speed now

The version difference may just be the issue then, as plugins may only be compatible with specific versions. Maybe you can try to use the versions from the working one on the other.

@johannesjom me too

@marcusquinn Sorry missed that part

@leantime thanks for that offer, I have sent an email from support@cloudron.io now

Yes it´s possible. Watch the video!

here we go Using a private bucket on Hetzner. S3_ENABLED=true S3_BUCKET=NameOfYourBucket AWS_ACCESS_KEY_ID=xxxxxxxx AWS_SECRET_ACCESS_KEY=xxxxxxxxxxxxxxxx S3_REGION=eu-central-1 S3_PROTOCOL=https S3_HOSTNAME=NameOfYourBucket.fsn1.your-objectstorage.com S3_ENDPOINT=https://NameOfYourBucket.fsn1.your-objectstorage.com

No, I mean just reinstall your Mastodon and start over with your account. As long as the account you want to have named correctly was only ever created on your own instance, reinstalling that instance should reset that username. If you move it, you won't be able to change it (I think).

thanks - that did the trick

@girish Ah okay... Thanks.

Worthwhile reads - ``Reply-To'' Munging Considered Harmful and Reply-to-List, or Reply-to-All?