Describe the problem/motivation
Zebar appears to rely on a fixed localhost port (127.0.0.1:6124) for its internal local server / WebView loading flow.
This can conflict with other resident applications that bind the same port. In my case, it conflicted with Shure MOTIV Mix / ShureDeviceManager, and Zebar showed a blank / white bar because its internal local endpoint was no longer owned by Zebar.
Since background apps like this often start automatically at login and remain resident, users currently have no reliable way to avoid this kind of conflict.
Describe the solution you'd like
Please add a supported way to configure Zebar's localhost listen port.
A setting, config field, environment variable, or CLI flag would all work. Keeping the current default port is fine, as long as users can override it when another application is already using that port.
Alternatives considered
Changing startup order can sometimes avoid the visible Zebar failure, but it does not remove the port conflict itself.
Describe the problem/motivation
Zebar appears to rely on a fixed localhost port (
127.0.0.1:6124) for its internal local server / WebView loading flow.This can conflict with other resident applications that bind the same port. In my case, it conflicted with Shure MOTIV Mix /
ShureDeviceManager, and Zebar showed a blank / white bar because its internal local endpoint was no longer owned by Zebar.Since background apps like this often start automatically at login and remain resident, users currently have no reliable way to avoid this kind of conflict.
Describe the solution you'd like
Please add a supported way to configure Zebar's localhost listen port.
A setting, config field, environment variable, or CLI flag would all work. Keeping the current default port is fine, as long as users can override it when another application is already using that port.
Alternatives considered
Changing startup order can sometimes avoid the visible Zebar failure, but it does not remove the port conflict itself.