Lemmy Support

4657 readers

2 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... (lemmy.world)

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

53 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

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (2 children)

I am using digital ocean.

Have you setup your ISP router to route ports 80 and 443 to your server?

I don't know what that is. What is an ISP router? Is that a config file on my server? You really need to spell it out. I am following the guides. That is what I know. If you have a better guide that uses this verbiage then please send it. I am happy to learn.

And during the docker method, I was trying to set up nginx and the status is inactive. It will not start.

Here is the status message:

 Starting A high performance web server and a reverse proxy server...
 nginx[29280]: nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/my_domain_name/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system>
 nginx[29280]: nginx: configuration file /etc/nginx/nginx.conf test failed
 systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
 systemd[1]: nginx.service: Failed with result 'exit-code'.
 systemd[1]: Failed to start A high performance web server and a reverse proxy server.

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

ISP = Internet Service Provider, so your Telco provider. By ISP router I was meaning the box you use at home to connect to the Internet as I presumed you were self-hosting at home. But since you are on Digital Ocean this is irrelevant.

I'm not familiar with Digital Ocean, do you have access to a standard Linux box with SSH or are you using some sort of Web UI like cPanel to manage it?

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

Oh, so my router, 🤣 lol, my bad.

And yes, I use Putty to access the server currently. root@IP with an RSA key. It works perfectly on Putty. Ansible just will not connect. No idea what to do there. It just says "UNREACHABLE". I have added and removed a dozen or so keys generated on the WSL Ubuntu Ansible local machine and none of them work.

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

Look in /etc/nginx/nginx.conf, it probably includes ./sites-available/*.conf, look in there for ssl_certificate(_key) that mentions that fullchain.pem, remove/comment(#) and restart nginx. It may still bitch about not having a cert for ssl, in which case take that out of the listen directives too.