Maycon Santos
Maycon Santos
> Hello, I have 2 questions. I am undecided whether to upgrade or not. > > 1. I don't fully understand the new Relay Feature. How will it benefit us?...
> Is it okay to update to 0.29.0 without actually running the new relay image and changing management.json? Yes it is. You don't need to update or configure anything if...
> For new relay to work is there any new openwrt package released? We will look into updating the openwrt version.
> Is it okay to use same domain for management, signal, coturn and relay? > > Example: If i use domain netbird.domain.com and i want to use this domain for...
@MDMeridio001 it seems like you are using nginx for SSL termination too, in that case, try this: ```yaml - NB_EXPOSED_ADDRESS=rels://netbird.mydomain.com:443 ``` and ```json "Relay": { "Addresses": ["rels://netbird.mydomain.com:443"], "CredentialsTTL": "24h", "Secret":...
@rgdev With a new deployment, it is very likely that Coturn will only be used with mobile clients until we update them.
Hey folks, we have a new release, 0.29.1. This release improves the relay with better authentication messages. To ensure your system is working properly, you should upgrade your relay and...
Dashboard stuck on loading after 0.29.4 > 0.30.0 update (Self-Hosted) if "JWT group sync" is enabled
@onyxkyr can you confirm if you have jwt groups sync and peer group propagation enabled?
Dashboard stuck on loading after 0.29.4 > 0.30.0 update (Self-Hosted) if "JWT group sync" is enabled
The fix will come on the next release. In the mean time, you can workaround the issue by disabling JWT group sync.
Hello @alexunderboots, to understand your case better, can you check this behavior with the cloud-hosted version?