Create ssh tunnel to Kubeflow UI running on private network

I’m trying to access the Kubeflow UI at url: 10.64.140.43.xip.io. Kubeflow is enabled on microk8s and I can access the dashboard via web browser on my server. I have enabled ssh so that I can connect from my laptop using ssh <my-user>@<network-server-ip>

What I wanted to try and do is use the following to access said web server from my laptop:

1. Set up a tunnel to the network server:

ssh -N -L 8080:10.64.140.43.xip.io:80 <my-user>@<network-server-ip> -v

1. Opened my browser and went to localhost:8080

This is where I am not sure what to do next. The url seems correct in that it changes to: http://10.64.140.43.xip.io/dex/auth?client_id=authservice-oidc&redirect_uri=http%3A%2F%2F10.64.140.43.xip.io%3A80%2Foidc%2Flogin%2Foidc&response_type=code&scope=profile+email+groups+openid&state=MTU5MDU5MzUyM3xFd3dBRURaSGJrdFBOMkUyVjJWSVdGaFNRV2M9fM2iV1_uauuIdMtwNarE5ypZQTX2MfNw6Cd0M0FzkUBM

Am I using tunneling correctly? This may be a better question for stack overflow but it seems more related to authentication and the specific web server configuration than to general port forwarding.

[knkski]

@Svendegroote91: Apologies for the slow response. In Firefox, you can do this by going to Preferences, then scrolling all the way down in the General tab and clicking on the Network Settings > Settings button. From there you can configure Firefox’s proxy settings like this:

[knkski]

With that method, you’ll run into an issue where you’re connecting to localhost:8080, and the hostname that Kubeflow is responding to is 10.64.140.43.xip.io. I’d recommend connecting like this instead:

ssh -D9999 <username>@<network-server-ip>

And then telling your browser to use a SOCKS5 proxy at localhost, port 9999. Then, you can go to 10.64.140.43.xip.io in your browser