Can you ssh to the compute node (the card will have a button to click to do this to make it easy by the “Host” line) and see if the app is in fact running using something like telnet to ensure the port you see in the logs is actually being used? Here’s an example I just ran:
$ netstat -tlnp | grep 5911
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:5911 0.0.0.0:* LISTEN 2038909/Xvnc
And that was after I checked the output.log to see which port was in use. If you don’t see something returned here, then the app didn’t even start on the compute node and we can go from there.
Now this is where I’m out of my league and you are doing a non-standard thing where I’m just winging it. Have you tested connectivity between this container and the compute? That’s outside my realm of knowledge, but you will need to test this as well if the first check above passes.
Lastly it looks like you need to set the OIDCXForwardedHeaders in the ood_portal.yml as well here. This is a bit unknown to me but I see other posts of users going through this here:
Which says you will need something like:
oidc_settings:
OIDCXForwardedHeaders: X-Forwarded-Proto X-Forwarded-Port
dex_uri: /dex
dex:
client_redirect_uris:
- 'https://your.redirect.edu:443/oidc'
....
Though they were using dex in that example. I’m definitely not an expert in this area but that’s the best i can see to get this unique setup running possibly. Hope some of this helps!