[BUG] UI 'serve-files' configuration strange behaviour

[Peelige]

Description Hello again, I briefly spoke with you on discord regarding this issue regarding the root folder serve-files.conf (along with the corresponding ROOT_FOLDER entry within site.env)

Set up is multisite, bunk-nginx, with ui. Latest versions as of this post (1.3.1)
The hosts configured are;

• the server's fqdn (proxying to the bunkerized-nginx-ui),
• domain2 : one wordpress site, serving files, remote php (another linked docker containter)
• domain3 : one html site, serving files.

What happens is when I update the configuration for domain2 via the UI (eg set gzip comp on), the root_folder for domain2 is written correctly: root /opt/bunkerized-nginx/www/www.domain2.com;

BUT all server configs are updated and the serve files for the other domains are also updated (domain3 in this case) and after a few config updates/saves ends up like this (in both serve-files.conf & site.env)

root /opt/bunkerized-nginx/www/www.domain3.com/www.domain3.com/www.domain3.com;

How to reproduce deploy bunkerized-nginx & the ui

• SERVER_NAME=vps1.domain.com
• MULTISITE=yes
• DISABLE_DEFAULT_SERVER=yes
• USE_API=yes
• API_URI=/bunk-admin-api
• AUTO_LETS_ENCRYPT=yes
• REDIRECT_HTTP_TO_HTTPS=yes

Within the UI add a couple of domains, set up to serve files. Then go back and edit domain2, then inspect the serve-files.conf that is written for domain3.

Logs None relevant to the problem.

[fl0ppy-d1sk]

Hello @Peelige,

Problem should be fixed in the next version. Thanks for your report !

[fl0ppy-d1sk]

Hello @Peelige,

This should be fixed in the last version. Don't hesitate to open a new issue if needed.