Hello,
We are introducing In Browser VPN for collaborators who doesn’t have full organisational account.
This means that the following link;
https://ood.org.uk/
has now become;
https://vpn.org.uk/https/ood.org.uk/pun/sys/dashboard
The dashboard access looks fine. I can start Jupyter Lab. However the Shell access seems to be broken, if i access this way, and I can’t find any logs to see whats going on.
The Shell access without in-broswer VPN is accessible at;
https://ood.org.uk/pun/sys/shell/ssh/login.org.uk
and with in-browser VPN;
https://vpn.org.uk/https/ood.org.uk/pun/sys/shell/ssh/login.org.uk
When Shell app is launched, it doesn’t shows any error/info message, just a white screen.
Best,
Arif
I don’t know how the In Browser VPN works, but it appears to have mangled the URL because there are 2 hostnames (the actual hostname ood.org.uk and the login hostname login.org.uk) in it and it likely uses a regular expression to extract them.
That is - login.org.uk in the PATH of the URL is somehow being recognized as the hostname. I assume this because it turns into https/ood.org.uk seemingly prepending the HTTPS scheme to the path?
It does prepend https/ood.org.uk to the path, however Jupyter App has no issues with this one and is accessible via same scheme, following link works.
https://vpn.org.uk/https/ood.org.uk/node/compute-12-02.org.uk/28094/lab?
Whereas, Shell app seems to act differently. I believe In browser app is introducing another layer of proxy, but can’t seem to find where its failing for Shell. Log file /var/log/ondemand-nginx/arif/error.log, doesn’t seems to throw any error messages.
Yea my comment may be disregarded, I think I see now what’s going on.
apache logs should at least indicate the URL you’re trying to access.