CLI access failed

Guys,
My CLI stop working and I refreshed Clien ID and Secret I got following error:
POST https://login.mypurecloud.com.de/oauth/token giving up after 5 attempt(s): Post "https://login.mypurecloud.com.de/oauth/token": tls: failed to verify certificate: x509: certificate is
valid for com.de, www.com.de, not login.mypurecloud.com.de
gc profiles list:
{
"profileName": "default",
"environment": "mypurecloud.de",
"logFilePath": "",
"loggingEnabled": "false",
"grantType": "1",
"clientName": "CLIENT",
"clientSecret": "SECRET",
"secureLoginEnabled": "false",
"redirectURI": "",
"accessToken": "",
"autoPaginationEnabled": "false",
"proxyConfiguration": "{protocol: , host: , port: , userName: , password: , pathParams: {}}",
"gatewayConfiguration": "{protocol: , host: , port: , userName: , password: , pathParams: {}}"
}
For gc profiles get (DEFAULT) response is diferent that configuartion comes:
gc@VE-DEV1:~$ gc profiles get
{
"profileName": "DEFAULT",
"environment": "mypurecloud.com.de",
"logFilePath": "",
"loggingEnabled": "false",
"grantType": "1",
"clientName": "CLIENT",
", ": ientSecret",
"SECRET": "secureLoginEnabled",
"false": "redirectURI",
"": "accessToken",
"": "autoPaginationEnabled",
"false": "proxyConfiguration",
"{protocol: , host: , port: , userName: , password: , pathParams: {}}": "gatewayConfiguration",
"{protocol: , host: , port: , userName: , password: , pathParams: {}}":

I have no idea what is going wrong and why CLI try to connect to mypurecloud.com.de

Hi @Robert

If you look inside the file $HOME/.gc/config.toml , do you see two profiles called "default" ? Perhaps one uppercase and one lowercase?

If so, try removing the one that has the wrong configurations and trying again.

Thanks,
Charlie

1 Like

Just located a problem , my environment variables ware configured for another application :slight_smile: now is fine
!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.