What you ran into was not a formatting rule of ours — it was nginx rejecting the file.
An nginx server block accepts exactly one
location /. The generated vhost always wrote its own, and your custom file was included in the same block, so adding
location / produced a duplicate and nginx refused to load the configuration. That surfaced in the panel as an invalid-format error, which did not explain the real cause.
The panel now checks whether your custom configuration already defines
location /. If it does, the generated block is left out and yours is used. If it does not, nothing changes. Your Vue history-mode configuration now works as written:
Code:
location / {
try_files $uri $uri/ /index.html;
}
This is not specific to Vue — any setup that routes unknown paths to a single entry point behaves the same way.
Three cases still keep the generated block and ignore a custom
location /: a suspended account, maintenance mode, and forced HTTPS redirection. Those are decisions the panel enforces, so they cannot be overridden.
Saving now regenerates the vhost, and if the result fails to load, the previous file is restored automatically.