It’s been many weeks since --webui-config and --webui-config-file don’t work for me. I was expecting that they were bugs that would be quickly fixed, but here I am… I use Chromium in Linux, and also tested it in Librefox. I don’t have a github account and don’t want to make it just to report this issue, but I doubt it’s a bug anyway, someone else would have already reported it. Any clue about what could be happening?
Command examples in case you want to test it:
llama-server --models-preset ~/models/presets.ini --webui-config ‘{“systemMessage”: “You are a helpful assistant.”, “showSystemMessage”: false, “showMessageStats”:“true”}’ --model ~/models/Qwen3.6-35B-A3B/Qwen3.6-35B-A3B-UD-MTP-Q4_K_XL.gguf --temp 0.6 --min-p 0 --top-k 20 --top-p 0.95 --mcp-servers-config ~/config/llama-mcp-servers.json
or
llama-server --models-preset ~/models/presets.ini --webui-config-file ~/config/llama_settings_2026-07-28.json --model ~/models/Qwen3.6-35B-A3B/Qwen3.6-35B-A3B-UD-MTP-Q4_K_XL.gguf --temp 0.6 --min-p 0 --top-k 20 --top-p 0.95 --mcp-servers-config ~/config/llama-mcp-servers.json
The webui config json file is loaded in this last command, I know it because if I make a wrong json file it throws an error, but the configurations don’t show up in Settings window an the are completely ignored, I have to load it manually using the Import/Export tab in the Settings.
The config settings are passed via
/props. Use the browser developer tools network tab and you should see them passed through there.Solved. I was using a config file generated using the Export Settings button, but llama-server --webui-config-fle doesn’t understand it because it has extra params, only the config entry of the saved json file should be passed to llama-server webui flag. No errors show up in the browser’s console, qwen pointed me out the conflict.
Thanks! yeah, the configuration has passed through and I can see the correct settings there, but they don’t show up in the Settings and I also checked that they are no “loaded”, e.g. the model ignores the system prompt of the config file, something that doesn’t happen when I load the config file manually.
deleted by creator
Flatpak variants of browsers might have issues because of having no access to all directories.
For example I can’t open the local Rust documentation in Flatpak Librewolf.
Good catch. Yeah I run both browsers from flatpak. The weird thing is that the presets.ini and mcp-servers.json files are loaded without issues.



