Cloudron Forum

@james
I have a Cloudron license, and that’s where I install and manage all our applications. Sorry for the confusion!

@james
Hi,
I’ve resolved the issue. I realized registration emails are sent via Sidekiq (background jobs), not via the test mail path. Checking the Sidekiq logs pointed me to the misconfiguration and I fixed it.

For reference, I used:

systemd:

sudo journalctl -u mastodon-sidekiq -f

Docker Compose:

docker-compose logs -f sidekiq

@james

Hi,
I configured the SMTP directly inside the app so that registration emails could be sent.
In the Mail FROM Address section, the app is configured to send mails using the address below and examplemail.com’s Outbound Email settings.

When I test with “Send test email” from the Mastodon admin panel, it works — I receive the test email successfully.
However, inside the application itself (for example, when a new user registers), the confirmation email is not sent.

So it seems that the SMTP settings work for the test function but not for real registration emails, which is why I tried setting it directly in .env.production.

Hi,
I’m running Mastodon on my server (Cloudron-based setup), and I’ve noticed that after every app update or container restart, the file
/app/data/.env.production — which I edit via nano — gets reset to its default values.

Because of this, all my custom mail server (SMTP) settings are lost each time the app restarts or updates.

Is there a way to make these environment variables persistent across updates and restarts in Mastodon?
Should I store them in another location (like cloudron.env) or configure them differently so they won’t be overwritten?

Thanks in advance for your help!

@james
Hi,

First of all, thank you very much for taking the time to respond to my question and provide a solution to my issue — I really appreciate it!

In the end, I managed to log in to Mastodon by manually creating an admin user.
Here’s the command I used inside the Mastodon directory:

RAILS_ENV=production bundle exec rails console << 'SCRIPT'
user = User.new(email: 'user@example.com', password: 'StrongPassword123!', password_confirmation: 'StrongPassword123!', agreement: true, confirmed_at: Time.now.utc)
user.account = Account.new(username: 'username')
user.save!
user.approve!
user.update(role: UserRole.find_by(name: 'Owner'))
puts "User created successfully: #{user.account.username} (#{user.email})"
SCRIPT

Only after creating the admin user this way, I was able to successfully access Mastodon.

Best regards,
Yossi

Hi everyone,
I’ve installed Mastodon through Cloudron, and everything seems to be running correctly — the app is healthy and accessible.
However, I’m unable to log in using the username and password that were created automatically by Cloudron during installation.

I’ve tried multiple troubleshooting steps (checking the domain setup, restarting the app, verifying the .env variables, clearing browser cache, and even creating new users), but nothing works — it feels like something is blocking all logins entirely.

Has anyone encountered this issue before?
Could there be a specific configuration or Cloudron permission that prevents Cloudron users from logging into Mastodon directly?

Thanks in advance for any help!