Local icons not loading. getting 404 about homepage HOT 8 CLOSED

Right, so this seems to be an oddity with the Next.js server.

You need to restart the container for new icons to be recognized.

I'll look into a fix for this.

from homepage.

Double check your local path and icon names are all correct. A couple other users where having trouble before and have since fixed it (a documentation issue), so I do know that it's working for others as well.

Feel free to reopen if you're sure it's a problem with Homepage directly.

from homepage.

I fight we the exact same issue. but I don't think this is a naming issue.
this is what I have in the icons folder, this is inside the container:

those are exact the same icons with different names, if I use the warning.png everything is working fine:
entry in the services.yaml: icon: /icons/warning.png

now if I use the other name warn.png:
entry in the services.yaml: icon: /icons/warn.png

I can not figure out what the issue is 😞

from homepage.

Double check your local path and icon names are all correct. A couple other users where having trouble before and have since fixed it (a documentation issue), so I do know that it's working for others as well.

Feel free to reopen if you're sure it's a problem with Homepage directly.

I don't want to rely on icons from the Internet so I load all the icons locally.
I did check several times. the name of the file and the path and everything looks as it should

from homepage.

Additional note about this issue. I was getting very inconsistent results with different icon references for local icons. Until I restarted the container as you suggested above. Then things settled down. But I see some different results still... As the above user, I also would like to have local icons. So when I specify "icons: /icons/pihole.png" which is in the correct location with other local icons that do work; it for some reason returns a 404. If I specify icon: "http://ip:port/icons/pihole.png" from another docker container that is running (another diff app w/local icons); then it appears correctly. If I use the remote CDN specification "icons: pihole.png" it also appears correctly. As I said I am specifying just like other local icons that do work but "pihole.png" does not (as an example). I have seen others that do this. Its like if they are already in the CDN, then they get skipped, not sure ¯_(ツ)_/¯. BTW: sidebar, documentation issue: I also noticed that all local icon file names need to be lower case to work, otherwise they 404. Other online icon libraries have upper case filenames that caused issue for me. Anyway thanks for a great app. Hopefully the above info helps.

from homepage.

Right, so this seems to be an oddity with the Next.js server.

You need to restart the container for new icons to be recognized.

I'll look into a fix for this.

This fixed my issue too. I would have thought adding the new volume ref. to my docker-compose.yaml file would have recreated (and thus restarted) the container, so I'm unsure why this works. Possibly worth adding a note at https://gethomepage.dev/en/configs/settings/#background-image.

Great work, btw.

from homepage.

...and I see it's the content rather than the location (volume mount) that's only recognised after a container restart. Sorry for the noise.

from homepage.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.

from homepage.