Tridion Docs - No Endpoint Listening

When installing LiveContent Architect you might receive the following error message when trying to open the webclient:

Trisoft.InfoShare.Client.InfoShareConnectionException: Unable to reach the repository '<USERACCOUNT>'. A connection with the service 'http://<URL>/InfoShareWS/Wcf/API25/Application.svc' could not be established. There was no endpoint listening at http://<URL>/InfoShareWS/Wcf/API25/Application.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://<URL>/InfoShareWS/Wcf/API25/Application.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.  at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)    --- End of inner exception stack trace ---

Resolution: 

Step 1 Check Bindings

1. Open Internet Information Services
2. Check the bindings of the website used (for example Default Website)
3. A default configuration has to have Port 443 and Port 80 Bind without any special configuration. See screenshot.
4. If port 80 is not bind you need to added. If port 80 is bind to a different website, you either have to remove it from that website, or change the binding for that website to a different port.

 
A Typical binding configuration without any IP address specified.

Step 2 Check proxy settings

If the bindings are correct check if a proxy server is used. All internet communications are relying on the proxy setting of Internet Explorer. 

1. Open Internet Explorer
2. Go to Tools --> Internet options
3. open the Tab Connections
4. Click Lan Settings
5. Make sure that Automatically detect settings and Use proxy server are unchecked

IIS settings for bindings and certificate is not correctly set.

Also see:
Troubleshooting Relying parties and Certificate issues