Gennaro | 2023-09-04 09:13:25 UTC | #1
Version 79.0.0 I tried almost every possibilities in the TOML. W PWD WO PWD, etc. According to the Proxy team I engaged to log wireshark, GC is ignoring the proxy and try to reach the cloud directly without proxy.
FATAL: 2023/09/04 09:32:44 POST https://login.mypurecloud.de/oauth/token giving up after 5 attempt(s): Post "https://login.mypurecloud.de/oauth/token": dial tcp 18.159.236.158:443: i/o timeout FATAL: 2023/09/04 10:39:51 POST https://login.mypurecloud.de/oauth/token giving up after 5 attempt(s): Post "https://login.mypurecloud.de/oauth/token": dial tcp 52.57.159.230:443: i/o timeout FATAL: 2023/09/04 10:45:31 POST https://login.mypurecloud.de/oauth/token giving up after 5 attempt(s): Post "https://login.mypurecloud.de/oauth/token": dial tcp 52.57.159.230:443: i/o timeout
Suggestion?
here my TOML [default] clientcredentials = 'myCRED' clientsecret = 'mySECR' environment = 'mypurecloud.de' loggingenabled = true loggingpath = 'C:\Users\Local\Temp\1\GenesysCloud' proxyhost = 'HOST' proxypassword = 'myPWD' proxyport = '8080' proxyprotocol = 'http' proxyusername = 'myUSER' redirecturi = '' secureloginenabled = false
Declan_ginty | 2023-09-04 11:52:39 UTC | #2
Hi,
I have asked one of my colleague to investigate the issue.
Regards, Declan
Jerome.Saint-Marc | 2023-09-04 12:07:49 UTC | #3
Hello,
I haven't used the CLI behind a proxy so far. But I noticed this section on Proxy Configuration in the CLI github repo. Have you tried with these parameter names and commands to enable or disable proxy? CLI Proxy Configuration
Regards,
Gennaro | 2023-09-04 12:20:30 UTC | #4
Yes I did it in different ways but always the same result Unfortunately there is no way to log what gc.exe is doing in regard the proxy usage. What I can see was in Wireshark that it is trying to connect directly.
Hemanth | 2023-09-04 13:18:17 UTC | #5
Hi @Gennaro
Thanks for the post. Looks like it is a bug with proxy bypassed particularly for the Login. While we provide a fix ASAP for it , just thinking out ways for you to proceed further in your setup. If you can provide an access token directly during the profile setup, you should not see this problem.
For all the rest of the GC calls the proxy should work as is.
Let me know if it works for you.
Best Regards Hemanth
Gennaro | 2023-09-04 14:06:35 UTC | #6
Thanks @Hemanth can you please explain what do you exactly mean for "provide an access token directly during the profile setup"?
Jerome.Saint-Marc | 2023-09-04 14:24:29 UTC | #7
Hello,
What Hemanth meant is that as a temporary workaround, you could obtain an access token using curl/postman/.... from Genesys Cloud (I think you are trying to use an OAuth Client Credentials Grant flow, as it is just the authorize/login step which is having a problem in GCLI (not using the proxy). Then you can set the access token directly in the config file, or as an Environment Variable or as a parameter of the GC command. See: https://github.com/MyPureCloud/platform-client-sdk-cli#setup-and-configuration
The rest of the gc commands should leverage the proxy. We'll work on providing a fix as soon as possible for the login/authorize step in the CLI.
Regards,
Hemanth | 2023-09-05 13:49:36 UTC | #8
Hi @Gennaro
You can upgrade to the latest version of GC-CLI ( [80.1.0] which should fix the problem. Please let us know if you need further info or assistance.Happy to help
Best Regards Hemanth
system | 2023-10-05 13:50:15 UTC | #9
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 21831