follow up from: https://lemm.ee/post/9562431
I ended up starting over on a t2.medium with Ubuntu and Lemmy 0.18.5.
Still following: https://join-lemmy.org/docs/administration/from_scratch.html
I had to make a few adjustments but that got me as far as:
nginx -s reload
But when I try to point a browser at my host, I don’t get a config screen, just a JSON doc. I haven’t been able to find anything in the logs that seems suspicious.
The only thing I did notice was that “id”, “inbox”, and “outbox” all have the wrong value. They all use:
https://lemmy.[mydomain]
instead of
https://lemmytests.[mydomain] (which is the correct name)
@rikudou@lemmings.world Was super helpful on my last post. I hope I can invoke their favor again.
Maybe some rules in nginx.conf has been delegated to nginx-internal.conf.
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 reloadDo you mean that I need to also do something like:
curl https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx_internal.conf
–output /etc/nginx/sites-enabled/lemmy_internal.conf
I aim to do some bug fixes and feature adds come winter when I’m bored, so by all means please submit improvements to the docs as you go 🙏🙂
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 :)
