values set in .env file are not replaced in homepage

[PhoenixNoble]

Description

I have set a bunch of HOMEPAGE_VAR_XXXXX and they do not seem to be replaced in 0.8.6 causing links to fail and status information to be missing

Steps to reproduce

update to 0.8.6

homepage version

0.8.6

Installation method

Docker

Configuration

HOMEPAGE_VAR_PIHOLE_URL=http://192.168.1.2
HOMEPAGE_VAR_PIHOLE_ADMIN_URL=http://192.168.1.2/admin
HOMEPAGE_VAR_PIHOLE_API_KEY=00000000000000000000000000000000000000000000000000000000000000

- DNS:
    - PiHole:
        icon: pi-hole.svg # icons found here https://github.com/walkxcode/dashboard-icons
        href: "{{HOMEPAGE_VAR_PIHOLE_ADMIN_URL}}"
        description: PiHole
        widget:
          type: pihole
          url: "{{HOMEPAGE_VAR_PIHOLE_URL}}"
          key: "{{HOMEPAGE_VAR_PIHOLE_API_KEY}}" # <--- updated with API key from PiHole

Container Logs

No response

Browser Logs

No response

Troubleshooting

n/a

Other

never reported an issue before, if i have missed something im sorry

Before submitting, I have made sure to

• Check the documentation
• Follow the troubleshooting guide (please include output above if applicable).
• Search existing issues and discussions.

[shamoon]

I don’t think this broke, did you re-create the container? Not just restart

[maf12]

I have the same issue. tried homepage over the weekend and it's not replacing any handlebars I set in the.env file. the docker-compose file is able to pull my PUID etc but the homepage config files don't pull any of the HOMEPAGE_VAR variables through.

I've tried recreating the container, making sure there are no permission errors but nothing fixes the issue.

[shamoon]

Well I just checked and this is still working fine.

Perhaps if people here can provide more specifics about how they're using this, my guess is thats the issue. As a basic point, if youre using e.g. HOMEPAGE_VAR_HOMEBRIDGE_PASSWORD that needs to be in the environment: part of your compose, if you put it in an env file, you need to specify env_file.

I tested both methods and they worked fine.

[maf12]

Yep that's the issue. From the docs I thought I was supposed to add the HOMEPAGE_VAR_ variables directlly in the .env file. I didn't realise these needed to be set in the environment part of the compose file etc. My bad.

[PhoenixNoble]

I have upgraded back to latest and it seems to be fine now, from memory all the variables where set in the container env, i tried both restart and recreating the container. Ill try and repro again in a fresh enviroment tomorrow

[glime-ai[bot]]

Based on the context provided, it seems that your environment variables prefixed with HOMEPAGE_VAR_ are not being replaced correctly in the configuration after updating to version 0.8.6 of Homepage.

To troubleshoot this issue, please ensure that:

1. The environment variables are correctly defined in your Docker environment. You can pass environment variables to your Docker container using the -e flag in the docker run command or by specifying them in your docker-compose.yml file.

2. The environment variables are correctly named and prefixed with HOMEPAGE_VAR_ as per the documentation.

3. The Homepage application has been restarted after setting the environment variables to ensure that it picks up the new configuration.

4. There are no typos or errors in the environment variable names or values in your configuration.

If you have verified all the above and the issue persists, you may want to check the container logs for any errors related to environment variable substitution or configuration loading. You can view the logs by running the command docker logs homepage (replace homepage with the actual name of your container if different).

If you are still unable to resolve the issue, consider reaching out for support on the #ai-support channel on Discord or by using the 'Ask AI' button on any page in the Homepage docs.

Additionally, you can check if there are any known issues related to environment variable substitution in the latest version by searching the existing issues and discussions on the Homepage GitHub repository.

If none of the above steps resolve the issue, you may need to file a bug report with the Homepage maintainers, providing all the relevant details including the steps to reproduce, configuration, and any logs that may help in diagnosing the problem.

---

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer above is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

This comment was generated by Glime.

[Fr3di]

I have similar issue but currently only with Home Assistant widget. I am using env_file method and have HOMEPAGE_VAR_HOME_ASSISTANT_API_KEY set in the .env file. Unfortunatelly the widget shows 401: Unauthorized error. When I set the api key directly in the services.yaml file it works fine, the widget can connect and shows data. But it is stopped working as soon as I move the key to the .env file.

What is even more strange, I have also added Portainer and PiHole the same way with keys set in the .env file and everything works fine. Only Home Assistant widget has this problem :/

Download v0.8.4 and it works with the key set in the .env file correctly but it doesn't work in v0.8.6

[PhoenixNoble]

if you have portainer and can see the ENV variables do you see it in that list? try a force-recreate?
"docker compose up -d --force-recreate" , I dont know if thats what fixed it for me or if going back a version did something but it all seems good on my end now

[Fr3di]

That's actually interesting, I have redownload the lates version and it is working now. No idea what happened but seems like going back end forth fixed the issue

[Fr3di]

Can confirm that the content of the .env file is not refreshed after homepage restart so it doesn't see newly added variables

[shamoon]

Docker requires recreating containers to pickup new env variables. That’s docker, not homepage

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. 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.