action #117550
opendeveloper mode over ssh bridge "thinks" we are in a "developer setup" needing second port forwarded
0%
Description
Observation¶
While doing a workshop on 2022-10-04 there was one setup where the openQA webserver was not directly accessible by the user's browser. With an ssh bridge
ssh -L 8080:localhost:80 <target>
the user's browser could reach the target webUI but the developer mode could not establish a connection. Using
ssh -L 8080:localhost:80 -L 8082:localhost:80 <target>
Expected result¶
Would be nice if this works out of the box or a hint is given in the webUI
Updated by okurz about 2 years ago
- Copied to action #117553: multiple people can not access openqa.suse.de but can access openqa.nue.suse.com, we should clarify the difference and maybe change our wording added
Updated by mkittler about 2 years ago
It is simply that 8080 is not a standard port (either 80 or 443) and therefore the setup is considered to be not behind a reverse proxy.
If you would have used ssh -L 80:localhost:80 <target> or ssh -L 443:localhost:80 <target> it would've worked.
I suppose we could add a config option to explicitly specify whether the instance is supposed to be accessed directly or from a reverse proxy (and still default to our current auto-detection based on ports).