PowerShell TCP test - for troubleshooting error "Could not proceed due to internal error: switching to cache channel : pos: create bucket error - encountered network error" during a Cloud Backup device backup attempt

We do have another separate KB article that covers this very same subject, that contains more fix methods in it, which goes into more depth and is more thorough than this current KB article that you are reading here, as compared to the instructions in this simplified KB article, and you can access that other directly related KB article here.

The reason that the error "Could not proceed due to internal error: switching to cache channel : pos: create bucket error - encountered network error when sending http request" in a Cloud Backup log (to our hosted Cloud Storage device) is seen is almost always that the Agent itself cannot connect to our Cloud Storage server's DNS address ("us1.storage.online-backup.com").

The following PowerShell TCP command should be able to connect, if it doesn't it means there is an issue on the network side (90% of the time it is DNS related we've found).

Please run this connection test to our "us1.storage.online-backup.com" Storage Server DNS address, that the Cloud Backup device uses. Go to Start Menu and type in PowerShell, and run it, and paste this command in:

test-netconnection -Port 443 -ComputerName us1.storage.online-backup.com -InformationLevel "Detailed"

In addition run the ping command "ping us1.storage.online-backup.com" to see if it fails to ping or if it can resolve to a valid IP.

If the test-netconnection command last output line of text shows "TcpTestSucceeded : True" then it passed. If the output shows "TcpTestSucceeded : False" then it did NOT pass. If the test did NOT pass, check to see what the "InterfaceAlias" line of text shows, that will state what network adapter was used, and if it is a VPN or other such adapter, disconnect the VPN & retry the tests. If the output shows "TcpTestSucceeded : False" then disable the SW & HW firewall and retry, and if it still fails then add these public DNS Servers to the main (LAN & WiFi) network adapter's DNS Server settings, by editing the adapter(s), and do a properties on the "TCP/IPv4" section, then click "Use the following DNS server addresses:" and specify these DNS Server IPs manually (Google & CloudFlare public DNS Server IPs):

8.8.8.8, 4.4.4.4, 1.1.1.1

Then save the changes and retry the same PowerShell TCP test & ping commands again. If both commands work it was due to the Firewall or the DNS Server settings, to resolve our DNS address. You can leave the DNS Servers manually config'd on that same network adapter, or you can on your internet router add at least 1 of the 3 above public DNS Server IPs in as a DNS Server address, and then change your main network adapter back to using automatic DNS Server settings, and run the same test again (possibly after a PC reboot, or after disabling that network adapter and re-enable it).