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.

[SawkeeReemo]

I have applied the env for HOMEPAGE_ALLOWED_HOSTS successfully for my domain, but how do you add multiple hosts? Apparently you also have to approve the local IP:port if you want to also access it directly and not through reverse proxy.

What’s the syntax for that? I tried [“my.domain.com”, “host-ip:port”] but that didn’t work.

[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]

But you are also not simply telling people how to do that. It’s not that hard to do, but since you don’t even give people the syntax anywhere that I can find, we are left to guess.

Please leave out the obnoxiousness as you complain about software that you enjoy for free.

Since you’re running the dev branch you’ll need to look there until it’s released https://github.com/gethomepage/homepage/blob/dev/docs/installation/index.md#homepage_allowed_hosts

[winslowhome]

But you are also not simply telling people how to do that. It’s not that hard to do, but since you don’t even give people the syntax anywhere that I can find, we are left to guess.

Please leave out the obnoxiousness as you complain about software that you enjoy for free.

Since you’re running the dev branch you’ll need to look there until it’s released https://github.com/gethomepage/homepage/blob/dev/docs/installation/index.md#homepage_allowed_hosts

@shamoon I get that @SawkeeReemo Could have worded the first part better but even I just gave up and decided to wait until you had released it in the hope that there will be an example in the DockerCompose.yml file. The Docker docs were not helpful in the slightest in trying to apply what they said to this new setting for GetHomepage.

Is it possible to have both a FQDN and a local IP:port or is it one or the other?

[shamoon]

Setting environment variables in docker compose in general seems pretty google-able, but maybe thats not what you meant? Yes, when released the document should be more obvious.

You can include as many domains as needed, depending on how you are using it you may need both, but if thats the case the logs will tell you specifically which is missing.

[SawkeeReemo]

But you are also not simply telling people how to do that. It’s not that hard to do, but since you don’t even give people the syntax anywhere that I can find, we are left to guess.

Please leave out the obnoxiousness as you complain about software that you enjoy for free.

Since you’re running the dev branch you’ll need to look there until it’s released https://github.com/gethomepage/homepage/blob/dev/docs/installation/index.md#homepage_allowed_hosts

I wasn't complaining? My apologies if that somehow read as obnoxious, definitely was not my intention. I was trying to offer a way for you to effectively help folks here since that seems like something you are genuinely interested in doing. For situations like this, usually offering up the syntax is all most people need who are trying to figure something out. Sometimes I can read someone's explanation 500 times and have no idea what they are trying to say, then I see an example and understand it immediately. That's all I was suggesting.

Thanks for the link as well. For some reason when I tried to find that earlier, I couldn't. Also, I tried the comma separated list initially but it did not work as I also had a space after the comma. Removing that space has corrected the issue. So for anyone searching who may be looking for an example of what to put in your docker compose file, it'll look something like this:

- HOMEPAGE_ALLOWED_HOSTS=sub.domain.com,192.168.1.234:3000

Hopefully it's obvious to you that you need to use your own values in there.

[SawkeeReemo]

Setting environment variables in docker compose in general seems pretty google-able, but maybe thats not what you meant? Yes, when released the document should be more obvious.

You can include as many domains as needed, depending on how you are using it you may need both, but if thats the case the logs will tell you specifically which is missing.

Just FYI, when I was trying to solve this, the logs told me that my local IP:port was not added to my HOMEPAGE_ALLOWED_HOSTS even though it was. As I stated above, the issue was having a space after the comma when defining multiple hosts. Would it be possible for homepage to remove whitespaces when parsing out HOMEPAGE_ALLOWED_HOSTS? Or maybe indicate in the logs that this is the problem? (Again, not complaining, I'm trying to submit helpful feedback. I hope it is being received that way.)

[Cyph3r]

Been using homepage for over a year. It's NODE_ENV is production. Haven't changed anything in all that time since original setup. Today it is broken with the error in this thread.
I added HOMEPAGE_ALLOWED_HOSTS to ENV and set to 192.168.0.4:3550,192.168.0.4,192.168.0.2
Same error.
What's the LAN notation? 192.168.0.0/24 not working either.

[shamoon]

read the release notes. It's not a CIDR. And the logs will tell you exactly what you need there. Anyone still having issues please open your own discussion