#Client doesn't show Listen Port when listening in selected and session is restarted

3 messages · Page 1 of 1 (latest)

whole apex
#

Hi Folks,

I've been using Ooba on Windows for about a year and when I enabled listen in the session tab the client would list a listen port that would use in other apps.

After a recent update, this port changed every time I launched the client and enabled listen which was a little frustrating but workable.

I updated a couple days ago hoping that this was resolved and now I don't see a port listed at all when I enable listen in the session tab.

I tried asking on the Ooba reddit, I looked at documentation (which doesn't have anything on listen specifically) and tried some google searches which suggested added --listen In the CMD_Flags but this no longer lists a port on the client. I tried adding --listen-port:XXXX but I didn't see anything listed on the client cmd that this was working.

Is there a new method for the listen checkbox in the session tab?

Thanks!

sturdy orbit
#

Have a look at the readme, at the part saying "List of command-line flags":
--listen Make the web UI reachable from your local network.
--listen-port LISTEN_PORT The listening port that the server will use.
--listen-host LISTEN_HOST The hostname that the server will use.

#

The --listen flag is only used to make tgwu listen on all IPs and not just on localhost, exposing the application to all network interfaces.