worldcitizen101

Thank you!

Weirdly enough, it works correctly after a reinstall. Here's what I did, if it helps anyone:

1. Delete the virtual server at Hetzner
2. Create a new virtual server
3. Ensure SSH still works
4. Run the Ansible playlist
5. Open the site and configure the new Lemmy instance
6. Do not disable federation
7. Create a new community and initial comment, run the curl commands noted above (I can't see this being valuable except as a confirmation that everything is working)
8. Block lemmygrad.ml and enable federation debugging
9. Search for a community on another server (I used !fountainpens@sopuli.xyz), open it up, then subscribe

I'm hesitant about a solution that involves reinstalling, but I'm new enough at managing virtual environments that I'm not going to look a gift horse in the mouth.

After some digging, I found the nginx config in the lemmy-ansible file structure: templates > nginx.config

However, this is highly abstracted because it's part of the Ansible install. I'm pretty sure I shouldn't edit it.

One possible clue - so far, I've been enabling federation from the UI. There's a bit in the configuration documentation that says that the lemmy.jhson needs to be updated with a federation block: https://join-lemmy.org/docs/en/administration/configuration.html

I don't have this file in the lemmy-ansible directory.

I also tried troubleshooting the federation setup again after reinstalling the instance from scratch.

All four CURL commands now return proper JSON:

• curl -H "Accept: application/activity+json" https://your-instance.com/u/some-local-user
• curl -H "Accept: application/activity+json" https://your-instance.com/c/some-local-community
• curl -H "Accept: application/activity+json" https://your-instance.com/post/123 # the id of a local post
• curl -H "Accept: application/activity+json" https://your-instance.com/comment/123 # the id of a local comment

Would this be a better question for the Ansible Github?

Thank you for sharing!

I'm trying to figure this out and I'm stuck at creating the file to save the API key. Where did you put the file in the lemmy-ansible setup?

Now you need to specify your credentials (use apikey as username and an API Key as password) in the separate file /etc/postfix/sasl_passwd (you'll likely need to create it):

I'm also working on this - thanks to this tip, I found that Hetzner also blocks port 25 by default. Apparently you can have it unblocked by going to the network tab -- but it's greyed out until you've paid them something.

Check out https://sopuli.xyz/c/fountainpens

Sailing - it seems like a high bar and expensive.