For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Neikel_146292's avatar
Neikel_146292
Icon for Nimbostratus rankNimbostratus
Jun 11, 2014

Confusing - non-standard HTTPS Ports

Hi everyone,

 

After searching around, I still can't solve my problem my self.

 

My system includes:

 

  • One BIG-IP 11.3.0 Build 39.0 (IP Address: 1.1.1.1 - for example)

     

  • 2 Server A and B (IP Address: 2.2.2.2 and 3.3.3.3)

     

  • Running the same service on port 8444 (https)

     

And, I don't know how to configure BIG-IP to get access to the service on server A & B by address:

 

https://1.1.1.1:8444

 

Please show me how to get this model or suggest me another way to reach my goals.

 

Thanks a lot. Neikel

 

6 Replies

  • Hi, you can configure 1 VS with 1.1.1.1 port 443 for example or 8443 if you need. Then create pool with 2 nodes: server A and server B. Map that pool to vs and you can get access.

     

    • Vitaliy_Savrans's avatar
      Vitaliy_Savrans
      Icon for Nacreous rankNacreous
      http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-3-0/1.htmlunique_243537012
    • Neikel_146292's avatar
      Neikel_146292
      Icon for Nimbostratus rankNimbostratus
      Hi Vitaliy, thank you for your help, but I can't get access to https with other ports than 443. Because at least my original servers A & B serve on secures port 8444 (https). When I choose whatever port different from 443 then the protocol automatically change to http but not https.
  • Protocol automaticaly change on visrtual server settings (it doesn't have any influence on service, just mapping for well known ports)? You can use number of port for service as you want. Really, it doesn't matter on wich ports serve your original servers, it may be different port on virtual server (big ip) and original servers. If you donn't need 8444 port on virtual server you can make configuration: 1. Virtual server 1.1.1.1 port 443 https. 2. Pool with original servers 2.2.2.2 port 8444 3.3.3.3 port 8444.

     

    I have the similar configuration for vs and it works fine. Let me know if you need additonal help.

     

  • If any of the below posts have provided a solution to your issue, please indicate so by clicking the tick to the left of them. This gives feedback and recognition to the volunteers who responded to your issue :-)