Comment on Running ejabberd behind a reverse proxy
adam@discuss.tchncs.de 1 year agoThe vps communicates with the rpi through a vpn.
I have not heard of duck dns nor lstio, but I’ll check it out when I get home.
Comment on Running ejabberd behind a reverse proxy
adam@discuss.tchncs.de 1 year agoThe vps communicates with the rpi through a vpn.
I have not heard of duck dns nor lstio, but I’ll check it out when I get home.
thelastknowngod@lemm.ee 1 year ago
Istio is a service mesh. You basically run proxies on the vps and the rpi. The apps make calls to localhost and the proxy layer figures out the communication between each proxy.
Duck dns is just a dynamic dns service. It gives you a stable address even if you don’t have a static ip.
adam@discuss.tchncs.de 1 year ago
How would I use that in this situation? I don’t get it. I already have a vpn set up to communicate between the two devices, and have been successfully running multiple services in this configuration for about a month. It’s just XMPP that I’m having trouble with.
thelastknowngod@lemm.ee 1 year ago
It auto discovers machines/instances/VMs/containers in the mesh and figures out the secure routing on the fly. If you couldn’t ensure a consistent IP from the home address it wouldn’t matter… The service mesh would work it out.
It is probably overkill for this project though… Something to think about…