@girish I've disabled backups for now as I try and work out why there is an issue with it. My Linode backs up daily at the moment so worst case I recover the whole system.

@dxciBel said in New external users sometimes don't receive confirmation mails: Not that I know of. User management was left to the app during install. Phew. I think you should be OK then! Ignore me.

https://www.reddit.com/r/Mastodon/comments/yzp1qz/mastodon_server_hardware_requirements/ This is a discussion on Reddit about what it takes to host a Mastodon instance (Mastodon uses the ActivityPub protocol). The requirements are quite high. One large instance with 29,000 users is hosted on this hardware: 2 AMD 5950 16c/32thread 128GB ram with nvme ssds running sidekiq jobs 1 AMD 5950 16c/32thread 128GB ram with nvme ssds running elasticsearch and redis 1 AMD 5950 16c/32thread 128GB ram with nvme ssds running Postgres DB 2 AMD 5950 16c/32thread 128GB ram with nvme ssds running PUMA (mastodon web app) and nginx (only one is currently powered on - other is being reworked 1 AMD Epyc 32c/64th 400GB ram with 10TB of nvme ssd acting as a s3 storage provider and another nginx/PUMA web front end This is a total of 96 CPU cores! Another person with 500 users says, "For those interested in a data point, I am running an instance with nearly 500 users. Currently running on an AWS Lightsail instance with 4GB Ram, 2 vCPU, for $20/month, and an S3 instance for media storage (1TB - nearly full) for $3/month. I am constantly monitoring resources - as the system is running well but nearly topped out. I will likely be moving to 8GB RAM, 4 vCPU instance, and 2TB S3 in the coming weeks." These requirements are quite high. I also recently learned that bandwidth is a continuous 1-2 Gbits/s. No wonder Mastodon is having trouble keeping up with the influx of Twitter users!

@alwynispat you've got DB_POOL specified twice I'm doing: [image: 1673203938259-be945764-0726-41d0-8886-d387d17c123a-image.png]

@b2breporter Oh - not totally sure, but I think we figured it out. We were originally trying to post images that were much larger in file size.

@alwynispat do you mean nginx? How is NPM involved here? edit: oh, maybe you mean your nginx proxy manager?

Unfortunately mastodon is not really designed much to change the domain and the user handles there. Some info on that is at https://docs.cloudron.io/apps/mastodon/#federation

okay, update looks easy. But reading this now https://github.com/cybrespace/cybrespace-meta/blob/master/s3.md

Thanks for the hint, I have update the docs to indicate that registration is only disabled by default when Cloudron authentication is used.

@marcusquinn said in "Searching toots by their content is not enabled on this Mastodon server.": Wordpress search using the ElasticPress plugin. I guess to make searching on the woocommerce supplements shops you run work well/ fast?

@johannesjom generally the permissions are basically everyone can do everything on hetzner cifs storage, in this particular case the changing of permissions from the app startup script fails. So apps which do not require this, will likely work just fine.

@nebulon It was still a problem until the most recent update. Server reboot was super quick! Thanks!

https://github.com/mastodon/mastodon/discussions/21916 is the upstream discussion for future reference.

@ScottyMojo right, if you read the linked docs it says you need to start the app manually keeping recovery mode.

@doodlemania2 Seaweed FS may be what you're looking for to cache/gateway object storage. https://forum.cloudron.io/post/56024

@shanelord01 you can ignore them. It's just logs from the box code trying to handle well known first before it hits mastodon.

@nebulon Yep - seems to be due to insufficient processes and threads in config.sh I'm playing with: #!/bin/bash # Setup scaling related environment variables here - https://docs.joinmastodon.org/admin/scaling/ # Puma export WEB_CONCURRENCY=10 # number of worker processes export MAX_THREADS=20 # the number of threads per process # Streaming API export STREAMING_CLUSTER_NUM=2 # number of worker processes # Sidekiq export SIDEKIQ_THREADS=80 export DB_POOL=100 # must be at least the same as the number of threads at the moment and it seems to be catching up.

@pauljacobson ah yes, the fix for haraka is coming. I recently submitted a patch upstream for this which has now been merged - https://github.com/haraka/Haraka/pull/3104 .

@jdaviescoates just visit mastodon.social and saw this in action