I have removed the empty properties,and I have tried some more things:
-I have changed Port for the Reporting Server from 80 to 88
-I have used IPNr of Reporting Server instead of its name
-I have disabled firewall
Still I see the same error in Chrome: "Refused to connect"
And Chrome Console says this:
Refused to display 'http://188.8.131.52:88/Reports_SQLEXPRESS//Pages/ReportViewer.aspx?%2Freport/Test3&rs:Command=Render&rs:Embed=true'
in a frame because it set 'X-Frame-Options' to 'sameorigin'.
Load denied by X-Frame-Options: http://184.108.40.206:88/Reports_SQLEXPRESS//Pages/ReportViewer.aspx?%2Freport/Test3&rs:Command=Render&rs:Embed=true
does not permit cross-origin framing.
This content cannot be displayed in a frame
So this messages says something about iframe and X-Frame-Options....
So I have tried to change the response header in ISS (I have tested some X-Frame-Options ), but it did not help.
And I think that SSRS does not use IIS anyway but has other mechanism... I have read somewhere that current version of SSRS does not use IIS anymore... so I wonder where I could the set response header...
While searching in Google I have found some recommendations to use parameter "rs:Embed=true" in URL call to the report, and as I can see in the console message this parameter is used... but doesnt help...
So in the beginning I thought this was somehow a problem with credentials / permissions.... but now it seems it is a problem related to the usage of iframe.... ?
Here my environment:
SQL 2016 Express Advanced (+ Reporting Services)