22

hey guys

I'm pretty new to this web-stuff

i got a vps where i'd like to install nextcloud. i want it to be reachable via cloud.example.com

i also have a homeserver with octoprint and stuff on it. i'd love to be able to access that with octoprint.example.com

that's what you pros use a reverse proxy for, right? but how do i do that?

install nextcloud with appache and use nginx as the proxy? i guess i could also use haproxy for that as well? what would you recomend as setup?

sadly nginx proxy manager is no option. but is there another easy to config method?

you are viewing a single comment's thread
view the rest of the comments
[-] Haystack@lemmy.world 5 points 5 months ago* (last edited 5 months ago)

I use Caddy V2 (running in Docker/Podman). Configuration can be even simpler than the below. It automatically sorts out the SSL certs from Let's Encrypt for you. If you use Cloudflare DNS challenge like I do, you can get SSL without the server having to be exposed to the internet.

cloud.example.com {
  encode zstd gzip
  tls {
    dns cloudflare {$CLOUDFLARE_API_TOKEN}
    resolvers 1.1.1.1 1.0.0.1
  }
  reverse_proxy nextcloud.my.local.domain:80
}

If you want it exposed then you can just use the default HTTP challenge.

cloud.example.com {
  encode zstd gzip
  reverse_proxy nextcloud.my.local.domain:80
}

And yes you can add any number of sites on subdomains like this and it will reverse proxy them to the correct server based on the domain name.

[-] fuzzy_feeling@programming.dev 2 points 5 months ago

that looks promising.

guess i'll take a look at caddy.

thank you very much.

this post was submitted on 03 Apr 2024
22 points (95.8% liked)

Selfhosted

39212 readers
594 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS