Forum Discussion

Kalido's avatar
Icon for Altostratus rankAltostratus
Mar 02, 2023

LTM Policy Port redirect

Hi Guy's

I currently have a VS listening on 443, all our backend servers work on 443.


We have a new requirement where we have a backend server already operating on 443 so we need to use a different port.


So the backend server is:


I need to browse to:


I need to connect externally to the F5 on port 443 and I need the policy to forward the connection to the backend server using 8443.


I have the URI rewrite configured already.


Please see my policy rule:

I get connection reset every time I browse to the url



8 Replies

  • Kalido To make sure I understand the request. You have a virtual server (VS) with lets say IP and listening on port 443 performing SSL termination with a client SSL profile. You also have a pool associated to this VS and it has pool memebers lets say and and the VS has a server SSL profile to encrypt the traffic and send it to those pool members. Now you would like requests for URI path /xyz to go only to a but on port 8443 instead of 443 which it is already listening on? If that is the case I would create another pool with a name that makes sense to you with the pool member and then choose the "Forward Traffic" to be pool and select the new pool that you created for this purpose. I would like to note that you must have both client and server SSL profiles configured under the VS and an HTTP profile in order for this to work. If you do not have those three pieces configured this will not work.

  • Hi Paulius,

    You have it 90%.


    So I don't use pool's I use LTM policy to forward traffic depending on a specific URI in the URL.

    For example:

    /abc/ -> forward to node

    /def/ -> forward to node


    This server is running something on 443 already as you mentioned so the new application will need to run on 8443.

    So as you can see from my ltm policy above, I have told it when a external user connects to the VS on 443 as they should the F5 to the backend should be 8443.

    However I just get connection reset, I am not 100% sure what you mean by client and server SSL profile, I believe I have that setup correctly because for 443 the SSL works fine. 


    Not sure I have a HTTP profile configured, what would this do for this situation ?


    • Paulius's avatar
      Icon for MVP rankMVP

      Kalido Understood on your configuration setup. I would recommend moving away from sending traffic to a specific node because this messes with any persistence that you might want to configure. You really should have a pool configured for each path that you are going to balance traffic for and use the forward to pool option instead. Using pools will ensure that persistence functions as expected, allows you to add additional members for a specific URI path or Host field without much of a change to the virtual server, and finally this allows you to run health monitors at a level that doesn't effect the entire node if by chance this node is working for one URI path or Host field but not others.

      In regards to client and server SSL profile, this configuration can be found under the VS with labels SSL Profile (Client) and the other as SSL Profile (Server). For the HTTP profile you can also see that under the virtual server and the configuration box says HTTP Profile next to it. Based on your previous statment you would have to have 1 or both SSL profiles and an HTTP profile configured already for it to be working for other URI paths so probably something you don't have to worry about but you can verify what is configured.

      Now in regards to 8443 if you run the following tcpdump you should be able to see if the F5 is issuing the reset or if it's the server. Most likely based on your description it is the server issuing the reset which typically means the server is either blocking because of a local OS firewall rule, the server isn't listening on 8443, or the server isn't expecting HTTPS traffic on port 8443. By "<f5_selfIP_closest to serverIP>" this would be the interface the traffic leaves the F5 on when attempting to reach the destination node. Replace the entirety of the pieces below from < to > for the appropriate IP.


      tcpdump -nni 0.0:nnp host <f5_selfIP_closest to serverIP> and host <nodeIP> and port 8443


      The following is an example of what the command would look like if the selfIP of the F5 was and the destination node IP is


      tcpdump -nni 0.0:nnp host and host and port 8443


      Hopefully this all makes sense and helps you resolve the issue at hand.

      • Kalido's avatar
        Icon for Altostratus rankAltostratus

        I can also see that traffic is getting to the backend server, I can see packets in but I can't see packets out:


        So the inital connection is getting there, what would your thought be regarding this situation?