this post was submitted on 20 Jul 2023
8 points (90.0% liked)
Lemmy Support
4654 readers
15 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is the server you're trying to deploy in a local network? Have you setup your ISP router to route ports 80 and 443 to your server? Or are you using Cloudflare Tunnel?
As for reverse proxy, it's usually Caddy or nginx-proxy to get a SSL certificate (for HTTPS) for your service.
I am using digital ocean.
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:
Look in /etc/nginx/nginx.conf, it probably
include
s ./sites-available/*.conf, look in there forssl_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 thelisten
directives too.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?
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.