Host not found
1. The VirtualHostingPath option is not configured correctly
This error usually occurs when you try to connect to a Custom
S3 server using S3 Explorer.
When you click Login
on the Add Account page, S3 Explorer reports the following error:
Add account failed: -1: Oepration failed: Host not found: No such hos is konwn (Code: 11001)
You need to check if the VirtualHostingPath
option is configured correctly.
By default, this option is turned on. If your S3 server does not support this option, you will need to turn it off and try connecting again.