Server not reachable over https

[irvmic]

Using the PBIRS and PB Desktop both october release I get a problem when trying to upload using https.

I get the Server not reachable error message when trying to save to server.

If I open the firewall and use the http version it works fine.

That is not an option for us to open it up to http.

If I go through my browser on https it works just fine to reach both /reports and /reportserver. I can upload the files using the web interface but that is not something we want to do. We would really prefer to use the https version in the client.

Any suggestion on where to look for an error? I can't find anything on the server and I don't know if the client logs anything at all?

[alexus555]

Hi there,

I had the same issue and the problem was in the mismatching of server name used for saving reports (in our case https://bi/reports) and  "issued to" name in certificate (in our case certificate was issued to *.ourdomain.kz). So when we tried to save report to https://bi/reports we got the error "Server is not reachable", but if we saved to https://bi.ourdomain.kz it worked fine. 

[garyhow01]

Hi, did you get a solution for this? May i ask if your ssl cert is self-signed?

[irvmic]

I got it running but the gui didn't help me much. had to modify the .config file and use the HttpCfg.exe utility to reserve the correct url's.

Can't get the upload from the client though.

[Greg_Deckler]

You can go to File | Options and settings | Options and then to Diagnostics and Enable tracing on the Desktop.

[irvmic]

Well that trace doesn't seem to trace the network information. It only seems to trace what the guid is showing on the screen with what componenet etc.

Fiddler shows that I am getting that the remote connection is forcibly closed.

 Warning: ClientHello record was 389 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. 

HTTPS handshake to myhostname (for #7) failed. System.IO.IOException Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. < An existing connection was forcibly closed by the remote host