
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
05-19-2022
11:09 AM
We have received several customer reports that the prerequisite checks succeeded when trying to connect to Cloud, but the initial push fails afterward due to connection issues to all addresses. See an example error below.
ERROR:
2022-05-03 10:54:21,935 [145] ERROR [InstallationDataManager] Error sending installation data to Cloud: InstallationDataManager => sending installation data failed: Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1651596861.940000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\client_channel.cc","file_line":3187,"referenced_errors":[{"created":"@1651596861.940000000","description":"failed to connect to all addresses"...
The error can be found in:
Our developers are still investigating the issue. The first findings do indicate that Firewall SSL inspection or SSL decryption could be causing the issue.
As a workaround, we suggest disabling SSL decryption of your firewall or adding a custom policy to not decrypt traffic to our URL endpoints.
ERROR:
2022-05-03 10:54:21,935 [145] ERROR [InstallationDataManager] Error sending installation data to Cloud: InstallationDataManager => sending installation data failed: Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1651596861.940000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\client_channel.cc","file_line":3187,"referenced_errors":[{"created":"@1651596861.940000000","description":"failed to connect to all addresses"...
The error can be found in:
- Program Files (x86)\Lansweeper\Service\Errorlog.txt
- Program Files (x86)\Lansweeper\Service\sync_errorlog.txt
Our developers are still investigating the issue. The first findings do indicate that Firewall SSL inspection or SSL decryption could be causing the issue.
As a workaround, we suggest disabling SSL decryption of your firewall or adding a custom policy to not decrypt traffic to our URL endpoints.
Was this post helpful? Leave a Kudo!
Did you have a similar issue and a
different solution? Share your work in the comments below and help your fellow IT Hero's!
More questions?
Browse
our
Quick Tech Solutions
or
Community Forum.
If you can't find what you're looking for, create a post in our Community Forum.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.