Better wait for Yunohost to update the very old Lemmy version they currently have. In the current version this setting doesn't even exist anymore in the admin ui.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
While it would be cool to use the yunohost version, I also moved away and due to issues with image uploads.
Found I could get it running on latest lemmy with ansible and ubuntu vps
Were you able to migrate your database from an outdated YunoHost installation to a v18 Lemmy running in Docker? I like YunoHost but I'm considering the same move, as this old Lemmy version has a lot of incompatibilities and other issues.
1. Check Permissions: First, make sure that you have the right permissions to edit the lemmy.hjson file. You may need to use a command like sudo to edit it if you’re on a Unix-based system.
2. Save and Restart: Once you’ve edited the lemmy.hjson file, ensure that the changes are saved correctly, and then restart the Lemmy service for the changes to take effect. You can do this via the YunoHost admin interface, or using a command like systemctl restart lemmy on the command line.
3. SMTP Server: Double-check your SMTP server settings. These typically include the server’s address, the port number (often 465 for SSL or 587 for TLS), and your login credentials.
4. Email Verification: Lemmy requires a working SMTP setup for email verification during user sign up. If there’s an error with the SMTP setup, you’ll see an “email_send_failed” error.
5. Test SMTP: You mentioned that you’ve already tested the SMTP server with swaks and it’s working. That’s great! If you’re not seeing those settings reflected in the Lemmy admin interface though, the changes might not be taking effect.
6. SMTP Relay: If your SMTP server requires a relay, make sure you have configured it correctly. You said you’re using “brevo” as a relay. If “brevo” is the relay server, it should also be mentioned in your SMTP settings in lemmy.hjson.
7. Logs: Check the logs for any error messages. You can typically find these in a location like /var/log/lemmy/, though it may vary based on your installation.
Without logs, I can’t say much more. Sorry.
I'm not familiar with yunohost, but if your Lemmy instance is running under docker, then 127.0.0.1
loopback IP address will point to the docker container instead of your host computer.