Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Blocked Host" error after docker-based install #10

Open
TomFrost opened this issue Aug 28, 2021 · 0 comments
Open

"Blocked Host" error after docker-based install #10

TomFrost opened this issue Aug 28, 2021 · 0 comments

Comments

@TomFrost
Copy link

TomFrost commented Aug 28, 2021

Using the Docker-based install script instructions from the website, I installed MissionKontrol (kuwinda/kuwinda container) using the command:

./auto-install.sh --run --use_https --ssl_cert /path/to/cert.pem --ssl_cert_key /path/to/privkey.pem

And when loading the application in my browser, I get:

Blocked host: my.hostname.net
To allow requests to my.hostname.net, add the following to your environment configuration:
config.hosts << "my.hostname.net"

There doesn't appear to be a way to do this via the script+docker install method.

Edit: Realized after simplifying the install that this isn't specific to SSL or remote. I ran the container with barebones settings and accessed via localhost, and still got the message that localhost is blocked. Did I miss a step? This seems like something everyone would be running into... but that doesn't appear to be the case.

@TomFrost TomFrost changed the title "Blocked Host" when using SSL on remote hostname "Blocked Host" error after docker-based install Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant