can't change webserver base url

[mptpro]

I can't change the Base URL of the webserver. Whenever I change it and save, it reverts back to the previous entry.

I am using Zerotier, but no longer need it, and the current entry in the Webserver Base URL is a Zerotier URL. I am trying to change it to the server's LAN IP (as I have successfully done in the Stream Base URL) but the setting won't "stick".

I don't get any errors, it just doesn't update the URL. I have restarted the Docker container after updating the URL and saving, but that doesn't help either.

• Docker container
• MA v2.7.0b22

thanks

[Tooa]

I have the same problem with the latest beta image ghcr.io/music-assistant/server:beta (https://github.com/music-assistant/server/releases/tag/2.7.0b26). I can reproduce the issue with a fresh installation as well. The log shows the following error:

music-assistant  | 2025-12-14 13:53:19.543 ERROR (MainThread) [music_assistant.webserver] Error handling message: config/core/save: Command remote_access/info is already registered

Tested changing the webserver base URL with the following settings. The base URL is my custom Traefik Docker network:

• Base URL: http://172.19.0.1:8095
• TCP Port: 8095

This is the docker-compose.yaml:

services:
  music-assistant:
    image: ghcr.io/music-assistant/server:beta
    container_name: music-assistant
    restart: unless-stopped
    # Network mode must be set to host for MA to work correctly (i.e. discover Sonos player)
    network_mode: host
    volumes:
      - ./data-beta:/data/
    # privileged caps needed to mount smb folders within the container
    #cap_add:
    #  - SYS_ADMIN
    #  - DAC_READ_SEARCH
    #privileged: true
    environment:
      # Provide logging level as environment variable.
      # default=info, possible=(critical, error, warning, info, debug, verbose)
      - LOG_LEVEL=info
    labels:
      - traefik.enable=true

      # Router
      - traefik.http.routers.musicassistant.rule=HostRegexp(`^musicassistant\.home\.(arpa|internal)$`)
      - traefik.http.routers.musicassistant.tls=true

      # Services
      - traefik.http.routers.musicassistant.service=musicassistant
      - traefik.http.services.musicassistant.loadbalancer.server.port=8095

networks: {}

[tmjpugh]

stop musicassistant
change "base_url" in /data/settings.json file
restart musicassistant

[marcelveldt]

That is a workaround. We should fix the issue. I'm pretty sure this bug is fixed in the beta already

[tmjpugh]

i running beta 26. Still an issue.
I agree. workaround until fixed.

[marcelveldt]

It works fine here. Did you press the save button ?

[chmac]

Where is the base_url, I don't find it in settings.json. Are there docs somewhere on the format of that file?

[tmjpugh]

yes. pushed save
I get below error

2025-12-14 16:46:54.234 INFO (MainThread) [music_assistant.webserver.remote_access] WebRTC certificate remote_id: xxxxxxxxxxxxxxxxxxxxx

2025-12-14 16:46:54.234 ERROR (MainThread) [music_assistant.webserver] Error handling message: config/core/save: Command remote_access/info is already registered

[marcelveldt]

are you sure you are on the latest beta ?

[tmjpugh]

Previous log was from ghcr.io/music-assistant/server:2.7.0b26

just tried ghcr.io/music-assistant/server:2.7.0.dev2025121403

2025-12-14 17:45:22.408 ERROR (MainThread) [music_assistant.webserver] Error handling message: config/core/save: Command remote_access/info is already registered

[tmjpugh]

If I go to settings >> system >> webserver >> base url and make change.
I get the error log I provide before and no change is shown on this page

If I go to settings >> about
The intended change is reflected in the "Base URL" shown but no actual change is made in the settings.json file

Currently my about shows Base URL as http://afasnafhdsadfdsafasd:8095. I typed in gibberish.

settings.json show

    "webserver": {
      "values": {
        "base_url": "http://music:8095"
      },

[marcelveldt]

that settings file has a delayed write so it will take up to 30 seconds before it gets written

[tmjpugh]

ghcr.io/music-assistant/server:2.7.0.dev2025121403
I changed to music.mydomain.com 2 days ago. today whats listed in about and .json are not the same. about is correct. json is unchanged.

ghcr.io/music-assistant/server:2.7.0b29
I started a complete new install. same results. same errors
I was thinking maybe it was some permission issue but by mistake I originally didnt mount the volumes. As a result Docker created volumes and I doubt permissions are going to be an issue with those. Same result with mounted folders as well.

EDIT
With the new installs it seem to never write to .json file actually but below log seem to suggest webserver has changed from the original http://10.88.30.16:8095 to what I changed it to http://music:8095. Either way reverts back to original after reboot.

Webserver available on: http://music:8095

If this address is incorrect, see the documentation on how to configure

the Webserver in Settings --> Core modules --> Webserver

################################################################################

2025-12-16 23:30:35.598 ERROR (MainThread) [music_assistant.webserver] Error handling message: config/core/save: Command remote_access/info is already registered

[phoenixtechnam]

Same here, cannot change base_url. When manually adding it into the config file, it is removed on next restart.

[chmac]

I have this issue, and I changed my base_url value in settings.json and restarted multiple times, I didn't see the value disappear or get overwritten.

[chmac]

@phoenixtechnam it's necessary to stop the server before editing the file, maybe that's why your changes get overwritten.

[andreasbrett]

Check the workaround mentioned here:
#4547 (comment)

[phoenixtechnam]

It seems to work with the code below. However, this is quite confusing

• Enable SSL although SSL is handled by reverse Proxy
• Random path to non-existent SSL Certificate must be set, otherwise settings are discarded on restart
• Still not able to set URL from UI as intended

    "webserver": {
      "values": {
        "base_url": "https://mass.example.com:8095",
        "enable_ssl": true,
        "ssl_certificate": "/path/to/certificate.crt",
        "ssl_private_key": "/path/to/privatekey.key"
      },
      "domain": "webserver",
      "last_error": null
    }

[Tooa]

Looks like the bug got fixed here #4547. The fix is part of the 2.7.4 release.