Yuagbyte webserver_interface not working in tmaster flags

General
1

Hi,

I ve been adding yuagbyte webserver_interface to the .conf file passed to yugabyted under the “master_flags” section , but it gets overdriven and doesn’t apply! the webserver still points to the same IP address of the host!

For Tserver it works! please help.

2

webserver_interface=127.0.0.1

That is the param I m trying to set for tmaster so that the UI under port 7000 cannot be accessible from the outside

3

Hi @maxernstscr

Please paste the full command you’re running so we can reproduce.

I believe it’s being overriden in this line yugabyte-db/bin/yugabyted at bfff348f93b0953c46658a8ee4a76c65ff2b0785 · yugabyte/yugabyte-db · GitHub

4

yugabyted.conf:

{
“master_flags”:“hide_dead_node_threshold_mins=1,webserver_interface=127.0.0.1”,
“tserver_flags”:“webserver_interface=127.0.0.1”
}

command:

export ZONE=zone4
export CONTAINER_NAME=yugabyte-v2025

podman run -d --name $CONTAINER_NAME
–network=host
-v /local/data/scratch/yugabyte:/home/yugabyte/$ZONE:Z
yugabyte bin/yugabyted start
–base_dir=/home/yugabyte/$ZONE
–config $ZONE/yugabyted.conf
–background=false
–cloud_location=$ZONE
–backup_daemon=true
–fault_tolerance=zone
–advertise_address=$(hostname)

5

The UI at 9000 is inaccessible but the UI at 7000 is still accessible and in UI I can see that the flag “webserver_interface” is overridden to the hostname itself