this post was submitted on 12 Nov 2023
1 points (100.0% liked)

Self-Hosted Main

502 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
1
advice for reverse proxy setup (alien.top)
submitted 10 months ago by drimago@alien.top to c/main@selfhosted.forum
2 comments fedilink hide all child comments
 

hello all,

I need some advice on how to proceed with my reverse proxy.

at the moment I have a proxmox lxc with Debian running nginx as a reverse proxy for some services like homeassistant, nextcloud jellyfin etc. I have a domain and everything works great with letsencrypt certificates.

since I started playing with frigate, I learned a bit more about docker and portainer and got a bit crazy with some more stuff like gitea, transmission, bookstack. now I have the following dilema: how do I use my current nginx with the new docker run services? is it just the usual way of proxy passing to the http://IP.address:port?

to make matters worse I have found out about nginx proxy manager and saw that it has the ability to easily add authentication to services which is interesting to me because of frigate. But with this one I have another dilema: if I switch from simple nginx to nginx proxy manager, how do I migrate my current setup (i.e. keys and configs)?

What is the best way to approach this mixed system? I forgot to mention that my current services are not run through docker and I don't plan to switch them over because I like them as they are now.

Sorry if this isn't the right place for this question!

you are viewing a single comment's thread
view the rest of the comments
[–] Ursa_Solaris@alien.top 1 points 10 months ago

There's nothing different. Just expose the ports using docker, and then point nginx at it like any other application. If it's running on the same server, you can just point it at localhost.

For nginx proxy manager, you can define custom configs easily, but for most usage you should be able to set up each redirect with a couple of clicks in the GUI. You should set it up to generate its own certs using the built-in tool though, but if you really want you can import certs manually through the GUI as well.