HowTo - Handle 'Soap http error - Cannot connect to host'

HowTo - Handle 'Soap http error - Cannot connect to host'

BioManager may report  " Soap http error - Cannot connect to host" after installation/upgrade. This is an  error indicating that BioManager application cannot connect successfully to the Core web services.
It can happen due to couple of reasons: either the communication over HTTPS was not correctly set up or  there is a mismatch in the configuration.


Checklist
  1. In R10.4 or earlier version - enabling the custom port (with default HTTP) creates a wrong configuration in config.yml under {Installation}\WebClient folder. To resolve, the 'endpoint' value under 'remote_admin' should be set to 'Basic' from 'BasicSecure'. NOTE: If HTTPS is used, this value shouldn't be modified. The defect has been fixed in R10.5 or newer version.
  2. If manual changes were made in configuration files, please double check to make sure they are correct (eg. config.yml must contain correct url to Core web services)
  3. If your installation requires HTTPS, during WebEdition installation, make sure that HTTPS configuration is done correctly in the Hosting Tool

  1. HTTPS setup requires correct TLS/SSL certificates installed on the web server (IIS). Based on this server certificate type, TBS provides clear documentation with steps to follow for proper setup. Please go through this document (TechNote - Securing Server Channel) and follow all those steps carefully 
During the WebEdition upgrade, the common.pem file could be replaced with a new version to include latest common public root CAs. In this case any custom root CA that has been appended to common.pem file would be lost resulting in the above issue. To resolve, please append again the custom root CA to the file.

    • Related Articles

    • HowTo - Handle 'SOAP-ERROR: Parsing WSDL' error in BioManager

      BioManager reports error “SOAP-ERROR: Parsing WSDL” which means connection to RemoteAdmin WSDL resource failed. Solution This error is most of the times caused by: missing ‘WCF Services - HTTP activation’ component (under Windows Features - .Net 4.5 ...

    • FAQ - WebEdition server installation troubleshooting

      Question What are the most frequent problems when installing WebEdition server, and how can I solve them? Answer Installing all WebEdition server components is not a click-and-go experience. It requires several installation steps and skipping or ...

    • HowTo - Handle 'Processing...' error

      BioManager may report 'Processing...' error endlessly after installation/upgrade. This is a generic error indicating an internal component was not installed or configured properly. No standard solution can be given, hence more information is required ...

    • HowTo - Handle 'Access denied' error with WebEdition R10

      To increase system security, from WebEdition version R10 web service authentication is enabled by default. This leads to problems with integrations that do not support security token on web service interface and results in 'Access denied' error. ...

    • HowTo - Handle '413. Request Entity Too Large' error in installations with SSL/HTTPS setup

      This error may occur in certain installations with SSL / HTTPS setup, in cases when clients send significant amount of data to server, more than the default limit of 49'152 bytes in IIS. That is because the entire request entity body must be ...