Looks like your mautic containers causes a database reset on restart. you likely need to add a volume to persist configuration.

Unfortunately, there isn't much we can do as this on the application level.

That's exactly what happened, but that should be standard, right?

anyway, I had to leave Railway and change hosts to avoid this anymore

and now I have another problem with a Ruby on Rails project, locally my storage pointing to Cloudflare works perfectly, but in production on Railway it has an error

FATAL -- : [10a3023e-b0dc-4c15-a7f5-285f5100d4bb]

Mar 19 20:32:52

[10a3023e-b0dc-4c15-a7f5-285f5100d4bb] Seahorse::Client::NetworkingError (SSL_connect returned=1 errno=0 peeraddr=172.66.1.46:443 state=error: certificate verify failed (unable to get local issuer certificate)):

I've already tried using Google Cloud and it gives the same error, so it's something on Railway, 2 brutal errors in the week, unfortunately only disappointment, I'll have to remove all my projects after this

https://stackoverflow.com/questions/46892135/ruby-rails-paperclip-seahorseclientnetworkingerror-ssl-connect-returned-1-e

I've already tried using Google Cloud and it gives the same error, so it's something on Railway

Can you share why you think it's an issue on Railway if you're having the same issues on another cloud?

another cloud in terms of storage

I use Firebase Storage to store files, and it worked locally, then I put it into production on Railway, and this error occurred, so I changed the host in terms of storage only, I used Cloudflare's R2, and the same error occurred on Railway, but localhost works perfectly, so it seems to be something that Railway

Please read the Stackoverflow link I shared. That's an issue with your application; configuration in production may be different from local, and "works on localhost but not on cloud" is typically an issue on your end with configuration instead of the cloud.