[BUG] Blocked request. Host not allowed.

[prudhvikrishnap]

Description:

Not able to access UI when self-hosting on k8s. This error is not occurring when using version 0.24.0 on k8s.

Docker Image Tag: ghcr.io/fmaclen/hollama:latest

Error:

Blocked request. This host ("{INGRESS_URL}") is not allowed.
To allow this host, add "{INGRESS_URL}"" to `preview.allowedHosts` in vite.config.js.

Reproduce Issue

1. Create a kubernetes deployment with image tag: ghcr.io/fmaclen/hollama:latest
2. Expose Application using service and ingress and try to access the URL with host mapping.

[shiqianwei0508]

change the file vite.config.ts

import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vite';

export default defineConfig({
    plugins: [sveltekit()],
    preview: {
        allowedHosts: ['test.testdomain.com']
    }
});

[randomouscrap98]

While we certainly could change the container and rebuild, that kind of defeats half the purpose of using docker in the first place. It would be nice if perhaps this configuration was able to pull allowed hosts from environment variables. I was trying to self host on my server and ran into several problems, including this one.

[fmaclen]

I'm not super familiar with Kubernetes but I just put out a new PR with an updated config to specify allowed hosts.

With these new changes you'd need to run the docker container as such:

docker run --rm -d -p 4173:4173 \
  -e VITE_ALLOWED_HOSTS='your-domain.com,another-domain.com' \
  --name hollama ghcr.io/fmaclen/hollama:latest

If VITE_ALLOWED_HOSTS is not specified, it will default to localhost.

@prudhvikrishnap Can you confirm if this will work with your setup?

[prudhvikrishnap]

@fmaclen I built docker image and tested the code locally. By configuring the VITE_ALLOWED_HOSTS variable, I was able to access to the webpage when using a custom host. I also tested the scenario where the hosts variable was removed, which resulted in the error mentioned above.

The changes in the pull request were successful and worked as expected on my end.

[fmaclen]

🎉 This issue has been resolved in version 0.27.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[fmaclen]

@prudhvikrishnap thanks for confirming the implementation. You should be able to pull the latest version of the image from the Docker hub.