Unauthenticated regardless of token generation

[marek-hanzal]

Hello, I've managed to setup running Quirrel in Docker with all the env. variables, called token acquisition, but I'm getting unauthenticated on the quirrel side all the times.

Some hints, how to make this strange thing work? Only way I've currently found is to disable secrets at all.

Here is snapshot of my docker-compose:

[Skn0tt]

One thing that stands out to me is that you're exposing Quirrel's :9181 as :49181, while in the app you're using :9181. Could that be a problem? (maybe it's just a weird behaviour from Docker).

[marek-hanzal]

Sadly, I'm really unauthenticated:

Is there some option to make quirrel logs more verbose? When I turn off encryption stuff, quirrel accepts a job, but it is marking it as failed and I don't know why: there is connection problem? API does not respond correctly? Oooor what? Also in the UI, job is marked as "completed" but in logs it's accounted as an error (so, I'm not able to see from UI a job is failed?).

[marek-hanzal]

So as a very first case I'm trying to authenticate in UI, second step I want to execute a job.

Another question - I'm running in next.js, with this solution, is it possible to run long running tasks? I mean for example few minutes of import or so?

[Skn0tt]

Please give me a detailed sequence of steps (as in: "create this file, run this command") that I can execute on my machine to replicate what you're seeing. I won't be able to help you if I cannot replicate your problem.

[marek-hanzal]

• docker compose up on the file I've copied here
• generated token using curl --user ignored:06b3673c19b20f87d0d1232ee1cfd392 -X PUT http://localhost:49181/tokens/puff-smith
• open http://localhost:49181 where quirrel UI sits, fill up http://localhost:49181, given token and secret from docker compose file

Got the 401 answer as an alert, in the logs and in network in the browser (Chrome in my case).

[marek-hanzal]

And note to the ports: there could be mess in Docker as backends are communicating on the docker internal network, thus using "native" ports, but to have an access to internal apps, I'm adding some prefix number; so the app see Quirrel, Quirrel see Redis, but for some reason, Quirrel cannot callback the app. If I've put prefixed ports inside, there will be connection timeouts as 4xxx ports are visible only outside of docker.