Phoenix1

MAIL_USE_TLS=True in my current configuration...that's what's really strange about it. The exact same configuration in Docker doesn't work for the bare metal install. I've yet to figure out why that is, I'm just glad that it works in the Docker version!

Ah, my configuration looks very similar, the only difference is that I'm using Mailgun 😁 I am self-hosting and our IP does allow HTTP/HTTPS, but not SMTP for obvious reasons!

Thanks very much for the list of files that need to be modified, that makes it much more simple at least. It's possible to write out a text file with cat, in the event that an editor is not available, but it's not the most convenient thing. It works though!

If it would be possible for the developers to edit the scripts so that manually applying the fix is no longer possible in the future, that would be wonderful, but for now the error is gone at least!

From what I can tell, inside the Docker image, there is no Python virtual environment, so the script generates an error when it tries to activate one. Unfortunately there are several scripts that try to activate a virtual environment inside Docker, so there are a ton of these e-mails being generated. I guess it would be necessary to patch the line out of each script somehow, but how would one do that without access to a text editor?

Thank you, I tried this from my Docker version of the instance, mail seems to be sent as normal through that...I just need to figure out why it's happening with the non-Docker version, so I'll have to test that and check the logs once I get a chance. It's probably something in the "hard way" configuration that I didn't get right along the way!

Goodness, how do you handle password resets and the like? Unfortunately I won't be able to operate a PieFed server without SMTP support, but I haven't been able to figure out what the issue is like yourself.

I'd like to thank you very much for this, it's easy to follow and it explains each of the steps well! I will go about turning this into a script for cron!

I appreciate all of the advice, it's really just my inexperience that's a problem here. It sounds as if it would be a simple matter of dumping the database from the Docker image and backing up the appropriate directories, but I'm having a heck of a time figuring out how to do that exactly. I'll keep trying though, but if any system admin out there could provide some concrete examples, I'd really appreciate it!

Unfortunately I haven't been able to figure this out, I was able to write a script for Mastodon that automated the process of dumping the database, copying the system folder and so on, I was able to restore a test backup I made successfully as well. I only say that to indicate that I have at least some familiarity with the shell, but not much 😁 In the case of Mastodon it's running on "bare metal" so to speak rather than Docker, so this is probably much easier for someone who is familiar with Docker!

Thanks, that should be simple to figure out if it's just one step, although I've never dumped a database from a Docker image before...I'll have to do some searching and see if I can figure it out!