this post was submitted on 01 Jun 2023
4 points (100.0% liked)

Lemmy Support

4634 readers
2 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

I have a debian linux host with docker installed on it. I followed the guide here: https://join-lemmy.org/docs/en/administration/install_docker.html

Changes that I made:

  • I used a sub folder called lemmy in my containers area rather than /lemmy
  • I copied the nginx.conf file from https://github.com/LemmyNet/lemmy/blob/main/docker/nginx.conf to my lemmy folder and ran a docker-compose up.
  • I changed the proxy service ports to 17008 (other service runs on 80) and 17003 (instead of 443).

I changed absolutely nothing else. No hostnames, no passwords. Nothing. The docker logs show it up and running.

Docker ps shows the instance fine too:

I've tried accessing http://<hostname>:17008, https://<hostname>:18003. I've tried setting my local hosts file for hostname "lemmy" to that server IP and accessing via http://lemmy:17008 and https://lemmy:18003

Is there something obvious that I'm missing?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] A1kmm@lemmy.amxl.com 2 points 1 year ago (1 children)

Also the default nginx forward proxy configuration runs nginx on port 1236, not 80, inside the container, and doesn't have any kind of TLS configuration.

I think most people likely have another layer of proxy (e.g. on the host) in front of it, instead of directly exposing the forward proxy from Docker Compose - that's what I do - and that's where I do TLS with a LetsEncrypt certificate.

[โ€“] NotOptionalAnymore@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

Ya, I have my own reverse proxy in front of all of that. I just wanted to try and get a very basic setup working first. Thanks for the great info, I'll do some research! No IPTables.