Unauthorized to create provider

[txrubel]

Hello,

getting Unauthorized error while trying create provider, Here I created new project and set it as default. And then I think CLI created a api secret for this project as following,

and the error found in the CLI,

and, from the debug log of fonoster_apiserver_1,

time="2021-11-19T18:09:21Z" level=debug msg="vulcand/oxy/roundrobin/rr: completed ServeHttp on request" Request="{"Method":"POST","URL":{"Scheme":"","Opaque":"","User":null,"Host":"","Path":"/fonoster.providers.v1beta1.Providers/C
reateProvider","RawPath":"","ForceQuery":false,"RawQuery":"","Fragment":"","RawFragment":""},"Proto":"HTTP/2.0","ProtoMajor":2,"ProtoMinor":0,"Header":{"Accept-Encoding":["identity"],"Access_key_id":["PJ6197d53d0b118e
0700000001"],"Access_key_secret":["eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJmb25vc3RlciIsInJvbGUiOiJQUk9KRUNUIiwiYWNjZXNzS2V5SWQiOiJQSjYxOTdkNTNkMGIxMThlMDcwMDAwMDAwMSIsImlhdCI6MTYzNzM0MDQ3NywiZXhwIjoxNjY4ODk4MDc3fQ.lM0Vy8N-31AsVloDhyFhFB9Nxr
qJpfAVmCuL-_sGhuQ"],"Content-Type":["application/grpc"],"Grpc-Accept-Encoding":["identity,deflate,gzip"],"Te":["trailers"],"User-Agent":["grpc-node-js/1.4.4"],"X-Forwarded-Host":["172.24.0.5:50051"],"X-Forwarded-Port":["50051"],
"X-Forwarded-Proto":["http"],"X-Forwarded-Server":["f8363bf8c487"],"X-Real-Ip":["172.24.0.1"]},"ContentLength":-1,"TransferEncoding":null,"Host":"172.24.0.5:50051","Form":null,"PostForm":null,"MultipartForm":null,"Trailer":nu
ll,"RemoteAddr":"172.24.0.1:43830","RequestURI":"/fonoster.providers.v1beta1.Providers/CreateProvider","TLS":null}"

Its look like request made with correct secret.

From log in the fonoster_providers_1 container,

Now my question, is there any place we need to add this secret before creating the provider?

Thanks,

[psanders]

Can you share the content of your config/rbac.json? Also, if you decode accessKeySecret at jwt.io what is the payload?

-- Update --

We don't know what caused but might be related to issue 245. If you encounter this problem please send us your logs. The solution, in this case, was to clean the Docker engine and run the process again:

#242 (reply in thread)

[txrubel]

Here attached the sipproxy log, there have 2 exception, may be those are related one,
fonoster_sipproxy_1.log

[txrubel]

here if we disabled the dynamic sipproxy api secret generation, then everything in docker loaded fine and even we can access sipproxy rest-api using that static api secret. But the issue still persist in providers create.

Errors in providers container while we run, fonoster providers:list

For which key its showing this error? could you please help us to debug this issue?

[psanders]

It's a bit hard to help when I can reproduce the issue. My recommendation is for you start from scratch with a clean Docker Engine. Remove the folder fonoster created and if possible clean all the volumes. Then, install Fonoster and if it fails send all logs from the installation process.

Here attached the sipproxy log, there have 2 exception, may be those are related one,

This should be a bug report, but I don't believe is the cause of the issue since the container is still responding.

[txrubel]

Dear @psanders , Cleanup docker help me to solve this issue. Thanks a lot for all the inputs.

[psanders]

I'm glad it worked! I marked this as answered, but feel free to comment if you have any related issues.