Reverse proxy SSL connections for vLab

[dgapinski]

Hello,

It looks like the Veeam vLab appliance is awesome at presenting insecure connections, but cannot reverse proxy an SSL connection for the purpose of allowing some web server testing. Has anyone had success with using a free Kemp for this purpose? It would mean that the subnets on both Kemp vNICs would be the same, unless I introduce some extra routing to appease what I bet would be a rather inflexible configuration in that regard. Thanks for your thoughts!

Thanks,
Dan

[dellock6]

The vlab appliance should just re-route the port you configure, what is the error message you are seeing?
Or simply the connection times out?

[dgapinski]

Yes you are correct, it will re-route the port, but won't do any cert handling, hence the Kemp Loadbalancer (I'm trying to make things as simple as possible for my users).

[dellock6]

But the cert is still handled by the original application like a web server, this is by far the most simple option.
If the issue is the cert not being validated because the SSL thumbprint is built with the original ip/hostname, you can just ignored the cert warning since it's a lab. If instead the cert is managed by an SSL reversed proxy, then you need to have also this machine in the lab to reproduce the production environment.

[skrause]

Just an FYI, you don't have to have two vNICs on the Kemp (even though it has two in the initial image).

And I don't see why you couldn't do what you are asking by putting the certificates on the Kemp and then forwarding it to the virtual lab IP/port.