Self-Hosted instance of Zrok with docker (401 Unauthorized)

zrok
1

Hi Everyone!
i was trying to set-up my self hosted instance of Zrok using a docker container in my linux machine,
everything went great but the "zrok-docker-zrok-frontend-1" keeps restarting, while checking the logs i saw this error
error: unable to authenticate to https://ziti.empleados.oycservicios.cl:1280/edge/management/v1. Status code: 401 Unauthorized, Server returned: {
"error": {
"code": "INVALID_AUTH",
"message": "The authentication request failed",
"requestId": "BT7dNB87z"
},
"meta": {
"apiEnrollmentVersion": "0.0.1",
"apiVersion": "0.0.1"
}
}
this may be a really stupid problem on my part, i'm a begginner, but i couldn't find any info online about this.
i would appreciate any help or feedback.

2

also i forgot to add that im running a cpanel server with a subdomain, the a records are pointing to my linux machine public ip
Name: empleados.oycservicios.cl TTL: 14400 Type: A Register: "My public ip"
Name *.empleados.oycservicios.cl TTL:14400 Type: A Register: "My public ip"

3

Hey there @jveliz-08 :wave:

That's the way I run my zrok too. Your DNS looks good. Are you following these instructions?

https://docs.zrok.io/docs/guides/self-hosting/docker/

1 Like
4

hey @qrkourier !
yes, i followed those exact same instructions.
could be a problem with my .env?
this is what i'm using right now
ZROK_DNS_ZONE=empleados.oycservicios.cl

ZROK_USER_EMAIL="my email"
ZROK_USER_PWD="my password"
ZITI_PWD="ziti password"
ZROK_ADMIN_TOKEN="zrok admin token"
in my .env file the fields ZITI_PWD and ZROK_ADMIN_TOKEN are just random passwords, i followed this video along with the official zrok guide.

5

Oh hey, that's me! The good news is that zrok-frontend can "see" the Ziti controller because it got an error response, so at least it's connecting.

The error is clear: the frontend has the wrong password. Maybe you changed the value in the .env after it was set. It won't auto-update the password, but you can use the same .env file you have now and reset everything.

:warning: destroy everything:

docker compose down --volumes

It's possible to change Ziti's password to the one you're currently setting in .env, but it's easier to start over.

1 Like
6

wow! how lucky i am! haha thanks for all the help and the video, it was really an amazing tutorial.
well i used docker compose down --volumes and then build it again with docker compose up --build --force-recreate
after that i got this error:
dependency failed to start: container zrok-docker-ziti-quickstart-1 is unhealthy
gladly, i decided to to the process from scratch and everything went great!
thanks again for all your help, with the video and here on the forum.
have a great day!

1 Like