1000TurquoisePogs

That essentially means that network activity is reaching the server through 7556 and not through 7554. A possible cause is authentication error, and clearing your browser cookies has worked for...

To turn on maximum logging if needed, here's how you do it: server-side, we have a websocket-to-TCP proxy. In the zowe.yaml, you can configure server-side logging of that plugin like...

> @1000TurquoisePogs It seems the issue reported is also related to the VT terminal use. In https://github.com/zowe/vt-ng2 I don't see a wiki like with the TN3270. What are the loggers...

One thing you must be careful of is when things are tagged wrongly. Sometimes this happens due to human error, other times it happens because configuration of some software is...

When using the explorers, please access the Desktop from the gateway, https://myhost:httpsPort/zlux/ui/v1/

You must use lowercase, it's https://myhost:httpsPort/zlux/ui/v1/ not https://myhost:httpsPort/ZLUX/ui/v1/

@DivergentEuropeans was working on this at one point. It requires the jes explorer to exist and you need to access from the gateway. Other than that, not sure if this...

i found the gateway has headers, x-forwarded-host: zowe_host:port x-forwarded-prefix: /zlux/ui/v1 x-forwarded-port: 7554 this seems to be the info necessary to determine whether or not to redirect.

This was implemented in 2.10.0

We implemented some of the workflows they had (stale bot) and issue templates. They had a changelog workflow that I didnt include though.