I would like to access my dev vcenter server via Caddy.
But i cannot get it to work.
Since it uses redirects after the 192.168.1.34/ui sso and many more (Witch I don’t know but there are many)
This is something you’ll have to try to configure in your vCenter, since Caddy isn’t the one issuing those redirects.
You might look into using http.filter to modify the response body to change links from 192.168.1.34 to vcenter.domain.com, but I don’t know if it works on headers (e.g. Location).
I actually had the same idea yesterday.
Yet not nor all the different Ports/URL but for the webclient.
This is running on Port 9443/vsphere-client
My Problem: I can’t get the proxy with the transparent option to run.
It changes the URL to the proxy-vm (different VM, different network) and just adds the port and /vsphere-client in the browser. Which can’t work since the port is not open from outside this network.
Any ideas on how to the a real transparent proxy working with caddy?
Or at least, where is my thinking wrong?
I dont’t want to change the URL from the browser who is accessing the proxy.
I want the proxy in between the browser and the vcenter and all traffic has to go through it…
Because only the proxy has a public accessible url/ip
As long as vCenter doesn’t issue redirects to its own IP address, Caddy should handle that configuration just fine.
vcenter.example.com {
proxy / 192.168.1.2:9443
}
If it does do absolute redirects, you’ll need to find a way to combat that (such as using http.filter or configuring it to use relative redirection instead), or it won’t work with any reverse proxy software.