Forum Discussion

destank's avatar
destank
Microsoft Employee
8 years ago

Save as via HTTPS: Server is not reachable

Hi all,

 

in our organisation we have private cloud where we are hosting 2 Report Servers: RnD and Production.

RnD is reachable via HTTP and Production is reachable via HTTPS.

Each server has its own private network.

For production server we have certificate installed and Kerberos is working.

All users can access both server.

PBIX reports work fine on the server

Using "Upload" button from portal we can deploy PBIX files from our machines on both servers but only on HTTP (RnD server) we can use "Save As" option in Power BI Desktop (Version: 2.51.4885.1423 64-bit (October 2017)) to deploy reports.

When we specify url for PRODUCTION server (HTTPS) we have "Server is not reachable" message.

 

Does HTTPS Save As option works on specific PORT that we need to open in firewall on our private network?

Or it is something else?

 

Thanks in advance.

 

Dejan

HTTPS
PBI Report Server
Server is not reachable

4 Replies

  • destank's avatar
    destank
    Microsoft Employee
    8 years ago

    In addition, i have just tested to deploy from the server itself logged in as administrator using Power BI Desktop (same version) and it reports same error: "Server is not reachable"

     

    update: i have tested the same as above but using HTTP and it works where HTTPS does not.

    • laaxy's avatar
      laaxy
      Frequent Visitor
      8 years ago

      I have the same issue.

      Did you found a solution?

      • destank's avatar
        destank
        Microsoft Employee
        8 years ago

        Hi,

         

        i think that in our case the issue is with TLS. For our front end servers we use only TLS 1.2. We have similar issues with our SharePoint farm.

         

        Regards

         

        Dejan

  • alexus555's avatar
    alexus555
    New Member
    3 years ago

    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.