saferwall: Connection to localhost:8080 was refused

I follow the setup installation from https://github.com/saferwall/saferwall/blob/master/docs/BUILDING.md for the Deploying in Minikube and I’m stuck at step 11.

Can you help me?

sw@sw:~/saferwall$ make helm-init-cert-manager
# Create the namespace for cert-manager.
kubectl create namespace cert-manager
The connection to the server localhost:8080 was refused - did you specify the right host or port?
make: *** [build/mk/helm.mk:34: helm-init-cert-manager] Error 1

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 22 (10 by maintainers)

Most upvoted comments

Oh yeah ! I forgot to add that, thank you for reminding me !

The credentials are in deployments/files/backend-conf.toml.

admin_user = "Administrator"
admin_pwd = "password"

I will think for a solution for an SMTP server.

LordNoteworthy on Oct 17, 2020

Hey @fareedfauzi I did many changes. I would highly appreciate if you can help with me with testing the new changes.

I removed none driver support for minikube as it makes too many issues, for local k8s deployment, we will be using kind for now but the vbox one is still there, I did some changes, can you please pull master branch and follow allong, most of the stuff is still the same: https://github.com/saferwall/saferwall/blob/master/docs/DEPLOYING-DEV.md.
I also added a vagrant box (experimental one) here: https://github.com/saferwall/saferwall/blob/master/docs/DEPLOYING-TEST.md

I am available at Gitter to help.

LordNoteworthy on Oct 15, 2020

@fareedfauzi sounds like a good idea, I will try to produce a ovf or a vagrant box img.

LordNoteworthy on Oct 11, 2020

Thanks a lot @fareedfauzi for trying that. I will try to run this on Ubuntu 20 as I only did the tests on the 18 one. and come back to you.

LordNoteworthy on Oct 6, 2020

The reason why you see this error is this: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory.

Because you are running minikube inside a VM which does not have VT-x enabled, and you’re trying to use VirtualBox (nested VM), it complains.

You have 2 solutions:

Either enable VT-x from vCenter settings.
Use MINIKUBE_DRIVER=none.

LordNoteworthy on Oct 5, 2020