Possible bug but more likely user error. "Host validation failed for: 192.168.0.X:3000. Hint: Set HOMEPAGE_ALLOWED_HOSTS to allow requests from this host."

[winslowhome]

Hi there, I am getting the following error in the Container logs:
"Host validation failed for: 192.168.0.X:3000. Hint: Set HOMEPAGE_ALLOWED_HOSTS to allow requests from this host."
with the following error on the page for my Homepage:
"Host validation failed. See logs for more details."

I have searched on her as well as gethomepage.dev for anything related to "Allowed_hosts" and similar search terms. However, I was not able to find the details for that error or config option. I did find allowed_endpoints but this does not seem to be related to my issue. As far as I can tell. My setup was working before I ran a docker pull on 17/FEB/2025. After updating accessing hostIP:3000 gives the host validation failed error.

Any help on how to resolve this or what settings I am missing would be helpful.

[shamoon]

You are running the dev version, and it tells you how to resolve it, that ENV needs to be set appropriately

[winslowhome]

Yup definitely user error. I should not have been on the nightly Branch. Not even sure how I managed that. I tend to avoid those as I'm not savvy enough in docker etc to be fixing things on my own 100% of the time. Again Thank you Kindly @shamoon.

[winslowhome]

Yeh don't know how I ended up on the nightly/dev version. I'll see if I can figure out how to get on the standard latest version. Thank you kindly.

[shamoon]

It will eventually land in our next release, so no reason to figure it out now but when youre ready: https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/

=)

[winslowhome]

I'll keep an eye out on the next version but I may be being a noob but I don't see Allowed_hosts mentioned on any of the docker environment pages. I could find allowlists for urls but not hosts. unless these are the same thing. but I will look for the Allowed_Hosts line in the next version. Thanks again for pointing me in the correct direction to resolve it for now.

[tylahfam97]

I'm getting this after installing standalone (not through docker)

[shamoon]

Did you read my reply above? This is not a bug, you are running the dev version and the explanation of what you need to do is in the logs.

This will be required in our next release, so up to you if you want to deal with it now or not.

[tylahfam97]

You didn't read my response, I am not running docker. I do not know how to set an env variable when npm installs and builds it, hence why I am here asking.

[shamoon]

You didn't say that at all. It's also quite google-able, here's the AI answer:

AI Overview
Learn more
To pass environment variables to a "pnpm start" command, simply set the environment variables in your shell before running the command, using the syntax VARIABLE_NAME=value pnpm start.

Example:

Set the NODE_ENV variable to "production" before running pnpm start

NODE_ENV=production pnpm start 

Key points:
Setting environment variables:
You can set environment variables in your shell using the export command: export VARIABLE_NAME=value.
...