I’ve been thinking about this lately as i was intending to build a 3 node cluster with proxmox. I still need to understand what happens when one node fails and how tbe othes handle exposing services. If the ip changes, bookmarks wont work. So i thought an inter al domain would be the sol ution?
Comment on OPNSense Reverse Proxies and Giving Internal Services Domain Names?
xavier666@lemmy.umucat.day 5 days ago
If you don’t mind the warning “Woah, I don’t trust this website”, you don’t need to buy any domains. Just use local certificates.
Sample caddyfile that I use
#------------- general options { local_certs } #------------- services service.server.lan { reverse_proxy <INTERNAL SERVER IP>:<INTERNAL SERVER PORT> }
However, you need to have a DNS entry which points *.server.lan to the correct server.
You can now visit https://service.server.lan/ which should point correctly.
Best of luck!
trilobite@lemmy.ml 5 days ago
melroy@kbin.melroy.org 5 days ago I also still want a 3 node setup for high availability as well! With the recent ram prices etc. I postponed it.
However the idea is simple. You setup a ceph cluster so the vm storage etc is shared across the cluster or your nodes. Then you can configure for each vm where it should start and where it can fallover to. Eg. Start a vm on node 1, but also allow it to start on either node 2 or 3 in case node 1 is down. Ceph cluster takes care of the rest.
Imaginary_Stand4909@lemmy.blahaj.zone 2 days ago
I’m not too worried about lack of tls/https for my websites rn, I just want to get working concept lol.
But thanks for the caddyfile, although I’m not sure I can use it since OPNsense seems to like to auto generate the config based on the settings in the UI.
I’ve narrowed down my issue a little more with the help of frongt@lemmy.zip, and I’ve established that:
Pinging immich.homelab.internal gets a response from the correct IP. When typing immich.homelab.internal or immich.homelab.internal:2283 in browser I get an ERR_NAME_NOT_RESOLVED page.
If I curl immich.homelab.internal, I get:
curl: (7) Failed to connect to immich.homelab.internal port 80 after 6 ms: Could not connect to serverIf I curl immich.homelab.internal:2283, I do get the html of the site at least.
Through some digging through other people’s forum posts, I made sure to turn off https redirects (auto_https disable_redirects).
I definitely know that it’s failing because Caddy isn’t redirecting my services from port 80 to their upstream port (2283, 8006, etc.), but I don’t know why it won’t redirect, even when looking at logs…
Redirection errors, as per my my experience, can be due to
I have used caddy with immich but I didn’t require any modified redirection options.