Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

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 ...
Vitaliy_Savrans's avatar
Vitaliy_Savrans
Icon for Nacreous rankNacreous
Jun 11, 2014

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
    Jun 11, 2014
    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
    Jun 11, 2014
    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.