gorilla help : Fails - to reach server about gorilla-cli HOT 5 CLOSED

Hey @abhisheknist149 is this still persistent? I just checked, and all services seem to be healthy. Have you checked if your network can reach any of our end points? You can test with ping 34.135.112.197

re: Running it locally - here is the issue tracking it. tldr: it is on the way! Stay tuned!

from gorilla-cli.

@ShishirPatil Thanks ping works , but command fails still - any way to troubleshoot to get more verbose...

🦍 LoadingServer is unreachable.
Try updating Gorilla-CLI with 'pip install --upgrade gorilla-cli'

Pinging 34.135.112.197 with 32 bytes of data:
Reply from 34.135.112.197: bytes=32 time=266ms TTL=43
Reply from 34.135.112.197: bytes=32 time=265ms TTL=43
Reply from 34.135.112.197: bytes=32 time=266ms TTL=43
Reply from 34.135.112.197: bytes=32 time=266ms TTL=43

Ping statistics for 34.135.112.197:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 265ms, Maximum = 266ms, Average = 265ms

from gorilla-cli.

Hmm. This is interesting. Are you behind a firewall, where any HTTP traffic might be getting dropped?

from gorilla-cli.

Closing this since I didn't hear back! Feel free to reopen.

from gorilla-cli.

I have the same problem using gorilla-cli==0.0.9 and PowerShell in Windows Terminal:

> gorilla hi
| 🦍 LoadingServer is unreachable.
Try updating Gorilla-CLI with 'pip install --upgrade gorilla-cli'

> ping 34.135.112.197

Pinging 34.135.112.197 with 32 bytes of data:
Reply from 34.135.112.197: bytes=32 time=134ms TTL=57
Reply from 34.135.112.197: bytes=32 time=134ms TTL=57
Reply from 34.135.112.197: bytes=32 time=134ms TTL=57
Reply from 34.135.112.197: bytes=32 time=134ms TTL=57

Ping statistics for 34.135.112.197:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 134ms, Maximum = 134ms, Average = 134ms

@ShishirPatil do you know what may cause the problem?

from gorilla-cli.