[Bug]: Custom stun server config not working on self hosted environment

[qadet123]

Contact Details

qadet123@gmail.com

What happened?

I've configured a custom STUN server in my compose file as follows

version: "3.4"

services:

  netmaker:
    ...
    environment:
      # this name is the config default name
      - STUN_SERVERS=<my_ip>:3478
      # this name is described in 
      # https://docs.netmaker.io/docs/server-installation/advanced-options#server-configuration-reference__compose-file-annotated
      - STUN_LIST=<my_ip>:3478

After restarting the services, I added a device, but it seems the custom configuration is not being applied in the servers.json file, The device still receives the default Google STUN servers:

{
    "<my_domain>": {
       ...
        "Stun": true,
        "StunServers": "stun1.l.google.com:19302,stun2.l.google.com:19302,stun3.l.google.com:19302,stun4.l.google.com:19302",
       ...
    }
}

the custom stun server address seems not working when client pull config from server

I have checked there are not other stun configs:

:~# grep -r -i stun ./ 
grep: ./netclient: binary file matches
./netmaker.default.env:# if STUN is set to true, hole punch is called
./netmaker.default.env:STUN=true
./docker-compose.yml:      - STUN_SERVERS=<my_ip>:3478
./docker-compose.yml:      - STUN_LIST=<my_ip>:3478

Version

v1.0.0

What OS are you using?

Linux

Relevant log output

Contributing guidelines

• Yes, I did.