Happy to share my notes.
Holding off for a bit though. The changes I made seemed to move me forward but I’d like to confirm that my changes at least work for me before I start recommending them to anyone else :)
Well hot damn. It worked!
Thanks.
Now I’m off to follow the rest of the steps. Wish me luck.
Thank you. I tried that and got:
curl: (7) Failed to connect to localhost port 80 after 0 ms: Couldn’t connect to server
When I put the port number back in:
I get the same 404 errors, with different time stamps.
journalctl -u lemmy
shows the same thing. Entries like:
Sep 27 20:26:04 ip-172-31-44-10 lemmy_server[12299]: 2023-09-27T20:26:04.726387Z INFO actix_web::middleware::logger: 127.0.0.1 ‘HEAD /api/v3/site HTTP/1.1’ 404 0 ‘-’ ‘curl/7.88.1’ 0.000054
I assume that /ap/v3/site is dynamically generated and there isn’t a location I can look at in the file system to make sure that everything is correct there, right?
The instructions have you create /usr/bin/lemmy, /etc/lemmy/lemmy.hjson (outside of stuff you download to the user directory) so I don’t think there is.
Can you elaborate on that? I’m not at all familiar with nginx configuration.
That was merged into lemmy-ansible on June 22. The instructions say to run:
curl https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx.conf --output /etc/nginx/sites-enabled/lemmy.conf # put your actual domain instead of example.com sed -i -e 's/{{domain}}/example.com/g' /etc/nginx/sites-enabled/lemmy.conf sed -i -e 's/{{lemmy_port}}/8536/g' /etc/nginx/sites-enabled/lemmy.conf sed -i -e 's/{{lemmy_ui_port}}/1234/g' /etc/nginx/sites-enabled/lemmy.conf nginx -s reload
Do you mean that I need to also do something like: