homepage's config shouldn't get clobbered by unrelated module changes

Posted by franciscus

I have linkaggregation on my nas with ip ending .149. Before I had 2 ip's .149 and .150 at the end. Yesterday happened this an today, when I enabeld today lidarr on my media center the ip of the stack changes back from .49.to .150 and I cannot connect the apps on the HOMEPAGE app. here is an part of sevices.yaml: Core: - SparkBox Dashboard: href: http://192.168.8.150:8443 description: Manage your server - Portainer: icon: portainer.png href: http://192.168.8.150:9000 description: Container management - Media: - Jellyfin: icon: jellyfin.png href: http://192.168.8.150:8096 all the apps have the wrong ip TomIA give me a workaround: sudo sed -i 's/192\.168\.8\.150/192.168.8.149/g' /opt/sparkbox/modules/core/config/homepage/services.yaml and after that restart: sudo sparkbox restart core On my flint3 router , I have my ugreen nas 8800 with a preffered ip address ending with .149 Is there a permanent solution for it?

2 replies

Chris wrote:

Good news — nothing's broken, and there's a proper permanent fix. Those homepage links get rebuilt from one saved setting (your "server address") every time SparkBox starts or you switch a module on — that's why the .149 you set keeps flipping back to .150. The earlier fix only edited the finished page, so the rebuild overwrites it each time. The lasting fix is to point that one saved setting at the IP you want, then let it rebuild once: sudo sed -i 's/^SBDOMAIN=./SBDOMAIN=192.168.8.149/' /opt/sparkbox/.env && sudo sparkbox up Once it finishes, every link on your homepage should read .149 and stay that way. I've also passed the wrong-IP-on-link-aggregation part to Tom — he likes to see these.

Chris wrote:

One correction I owe you, and it's about the Radarr tile fix from your other thread. You were told to run sudo sparkbox update to land on 1.6.400. That only re-pulls the app images your box is already pinned to — it cannot move you onto a newer SparkBox release. The command that does is: sudo sparkbox upgrade So if your tiles are still dropping after an update, the likeliest reason is that 1.6.400 never actually reached your box. Running that should settle it. The SBDOMAIN change above is separate and still stands. Sorry for the runaround — Tom has since corrected the wording that caused it.