Showing results for 
Search instead for 
Did you mean: 
woof New Member
New Member

Cannot Access PBIRS with :443 through Proxy (F5)



1.  PBIRS is on Azure in IaaS tier. 

2.  It is necessary to connect to a VPN to access the PBIRS

3.  When connecting via VPN using real hostname, we can connect via port :80 and port :443

4.  On F5 we created a pool, and pulled a VIP to a subnet that does not require VPN.

5.  Also create a friendly name for the service.  Different than actual hostname.  Easier. 

6.  When connecting through F5/friendly name, we can connect via port :80

7.  We cannot, however, connect via :443 through the F5


We are eventually going to shut port :80 off, but obviously not until we can connect via :443. 


Any idea of what is going on here?  F5 engineer swears everything is good on here side.  Is there a configuration item somewhere in the PBIRS that would rerquire the friendly name to be "registered" in some manner?  For that matter, do i need a server certificate that uses the friendly name? 


Any thoughts or clues would be gratly appreciated. 

Helpful resources

Ask Amir Anything

Exclusive LIVE Community Event No. 2 – Ask Amir Anything

Next in our Triple A series: Ask Amir Netz questions about the latest updates, features and future.

October 2019 Community Highlights

October 2019 Community Highlights

October was a busy month in the community. Read the recap article to learn about some of the events and content.

New Solution Badges

New Solution Badges

Two waves of brand new solution badges are coming! Read the article for more information on our new community badges.

Analytics in Azure virtual event

Analytics in Azure virtual event

Experience a limitless analytics service built to ingest, prep, manage, and serve data for immediate use in Power BI.

Users Online
Currently online: 54 members 1,217 guests
Please welcome our newest community members: