services.yaml gone with upgrade to 1.9.0

[cleanmachine]

Description

My customized homepage was replaced by a default config after upgrading to 1.9.0. I run homepage in an LXC on Proxmox via a Community Script (https://community-scripts.github.io/ProxmoxVE/scripts?id=homepage&category=Dashboards%20%26%20Frontends). When I noticed a new version earlier today, I ran the update command in the container and found to my great dismay that my customized setup was replaced by a default install. Um, help? I am not a sophisticated user. The .yaml files all appear to be the defaults from a fresh install. None of my customized files are present. I run nightly backups of the container so I can restore things if need be but thought I would check in here first. I am also not sure if I am even reporting this properly as I am a Github newbie as well.

homepage version

1.9.0

Installation method

Docker

Configuration

Container Logs

[2026-01-19T17:06:01.728Z] info: kubernetes.yaml was copied to the config folder
[2026-01-19T17:06:04.859Z] info: docker.yaml was copied to the config folder
[2026-01-19T17:06:04.866Z] info: services.yaml was copied to the config folder
[2026-01-19T17:06:04.868Z] info: bookmarks.yaml was copied to the config folder
[2026-01-19T17:06:04.869Z] info: widgets.yaml was copied to the config folder
[2026-01-19T17:07:40.110Z] info: custom.css was copied to the config folder
[2026-01-19T17:07:40.111Z] info: custom.js was copied to the config folder
[2026-01-19T17:07:40.147Z] error: undefined
[2026-01-19T17:07:40.185Z] info: proxmox.yaml was copied to the config folder
[2026-01-19T17:07:40.187Z] error: undefined

Browser Logs

No response

Troubleshooting

I SSH'd into the container to look at the cirectory and the logs and cannot find the customized files I developed over months of edits and changes. Only the default files from a fresh install and the logs I copied above.

[shamoon]

That sucks. Can you provide a bit more details about the permissions of your setup, config directory etc?

[shamoon]

Ps. this version didnt really change anything about this.

homepage/src/utils/config/config.js

Lines 30 to 43 in d3f1832

	if (!existsSync(configYaml)) {
	const configSkeleton = join(process.cwd(), "src", "skeleton", config);
	try {
	copyFileSync(configSkeleton, configYaml);
	console.info("%s was copied to the config folder", config);
	} catch (err) {
	console.error("❌ Failed to initialize required config: %s", configYaml);
	console.error("Reason: %s", err.message);
	console.error("Hint: Make /app/config writable or manually place the config file.");
	process.exit(1);
	}
	return true;
	}

only copies the skeleton when a file is missing, never when it already exists.

[shamoon]

ChatGPT suggests:

Likely causes to check: the upgrade recreated the container without the bind mount, changed the mount target (e.g., /config vs /app/config), overrode the entrypoint, or set HOMEPAGE_CONFIG_DIR to a new path. The data is probably still on the old volume if it existed.

Suggested next steps:

docker inspect --format '{{json .Mounts}}' to confirm the host path is actually mounted to /app/config (or /config).
Inspect the old volume path on the host for the missing files.
Verify no HOMEPAGE_CONFIG_DIR override or custom entrypoint/command is bypassing docker-entrypoint.sh.

[cleanmachine]

As I said, I am not a sophisticated user. It is all the defaults that come from that Community VE Helper Script install. I pasted the install script (bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homepage.sh)") into the Proxmox shell and setup VS Code to SSH into the appropriate directory in that LXC (/opt/homepage/config/). From there, I followed the widgets examples and customized things bit by bit. I have restored 1.8.0 from last night's backup and will await a fix.

[shamoon]

That script seems to set CLEAN_INSTALL=1 and that might be the issue here. Perhaps its worth checking with the makers of the script (and / or seeing if thats the correct way to update, seems more like an install script)

[cleanmachine]

I have used that script's update function in the past several times with no trouble. This homepage LXC has been running for well over a year and obviously has gone through several updates. I do really love the software and the customization. But I will reach out in that community to see if others are in the same boat - thank you for the suggestion.

[shamoon]

community-scripts/ProxmoxVE#10993

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.