Lemmy Support

4675 readers

14 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

[email protected]

Please, need help deploying a lemmy instance... (self.lemmy_support)

submitted 1 year ago* (last edited 1 year ago) by ZMonster to c/[email protected]

47 comments fedilink hide all child comments

I have tried the docker, ansible, and scratch methods. I have been troubleshooting for a month now. I have gotten nowhere. I need someone to help walk me through how to deploy a lemmy server because the guides are absolute trash.

Please help. I'm wasting money running this VPS and for literally nothing.

Edit: So, I've tried the ansible method, but I can't access my server this way. It just keeps saying "UNREACHABLE". I have generated a dozen keys, none of them work. I have NO PROBLEMS with ssh in Putty. I can use Putty all day. Putty works fine using my ssh key. Ansible does not. No amount of new keys has made any difference. I have countless keys in my stupid droplet because of this hacky garbage.

you are viewing a single comment's thread
view the rest of the comments

[–] ZMonster 2 points 1 year ago (2 children)

Okay, so it looks like nginx is a reverse proxy. That is the step I was on. It doesn't work. Last thing I did was to modify the docker-compose.yml file and change the port from 80 to 1236. I was told to do that by someone who has been trying to troubleshoot with me for 2 weeks now. It doesn't say to do that anywhere, but they told me to so I did. Then they said to "add this to my upstream" but I haven't a fucking clue what that means so I don't know what to do next. There is a config file in etc/nginx/sites-enabled/nginx.conf that the guide directed me to edit. This is the guide that I was directed to use to set up nginx. I was on the step where it requests the nginx status and mine just says "inactive". I promise, I am following these guides PRECISELY. I don't know what I am doing wrong, but all the solutions that I have received are things that the guide DOES NOT say to do. So I don't know where I am. I am happy to start fresh. You just let me know.

[–] [email protected] 1 points 1 year ago (1 children)

In my opinion its best not to touch the nginx that's set up by Lemmy and it's better to have another reverse-proxy in front of it.

I'll try to come up with an solution later in the day, gotta do my daily at work.

[–] ZMonster 1 points 1 year ago

No problem at all. Thanks for getting back to me. I really do appreciate it!!!! I have a busy day today too but I'll try to be vigilant about responding.

[–] [email protected] 1 points 1 year ago (1 children)

It doesn't tell you to actually run nginx, it assumes it will automatically run when installed. I don't know why, that sounds like dumb behaviour even if it were correct. You are right about the guides being trash.

I recommend getting used to package manager (apt, dpkg) and system daemon/init system (systemd - accessed via systemctl) and then ignoring that guide. Installing and running nginx isn't complex enough to warrant a guide; installing packages and running services, in general, are just. Configuring nginx, however... If you know the concepts, it's pretty easy. The concepts are hard.

[–] ZMonster 1 points 1 year ago (1 children)

It doesn’t tell you to actually run nginx

That may be so, but the link that they give references a digital ocean guide that DOES (it's literally step 2). So, am I just ignoring that part? How do I figure out which parts of a guide should be followed and which ones shouldn't?

running nginx isn’t complex enough to warrant a guide

I haven't gotten it to work yet so I disagree.

[–] [email protected] 1 points 1 year ago

How do I figure out which parts of a guide should be followed and which ones shouldn't? If ignoring a part makes the guide work better then it's a bad guide and you should find a better one.ツ

I haven't gotten it to work yet so I disagree. If you systemctl start nginx, can you access localhost:80? If so, success, you've run nginx. Very simple.