You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some institutions block outgoing requests to IP addresses in combination with non-standard ports. As a result, console access is required to get the head node DNS name, and then must be replaced in the DCV URL within the 15 seconds it takes for the token to expire. Can a configuration option be added to use the public DNS name over the IP address, as these work fine and are not blocked. Putting this as a config option would be great in case others still wish to use IP addresses.
The text was updated successfully, but these errors were encountered:
Hi DA-Osborne, I wished I had a workaround for you to ease this situation but unfortunately I don't have one.
The way the DCV session instantiation works, we don't have available a way to use the dns name.
I'm going to note this for our future developments.
Thank you for pointing this out for us!
Some institutions block outgoing requests to IP addresses in combination with non-standard ports. As a result, console access is required to get the head node DNS name, and then must be replaced in the DCV URL within the 15 seconds it takes for the token to expire. Can a configuration option be added to use the public DNS name over the IP address, as these work fine and are not blocked. Putting this as a config option would be great in case others still wish to use IP addresses.
The text was updated successfully, but these errors were encountered: