Skip to main content
Participating Frequently
September 23, 2024
Question

ColdFusion 2021

  • September 23, 2024
  • 1 reply
  • 419 views

Team,  our Infrastructure changing later this year and main impact is IP on our Web server where CF installed  changing.

 

?  I have identified 2 changes in IIS/Hosts file change., Does WSconfig /connector need to be rebuilt?

I have validated no IP's embedded in CF source code.

 

I am currently at update 9, plan to go to latest update 16 next month.

 

ty Jose

    This topic has been closed for replies.

    1 reply

    BKBK
    Community Expert
    Community Expert
    September 23, 2024

    If you go from Update 9 to Update 16, you will have to recreate the connector. To confirm this, go to the page offering information on ColdFusion 2021 Update 16 and scroll to the bottom of the page.

    Participating Frequently
    September 23, 2024

    Ok txs,

     

    What about when my web server IP changes? Anything inherit to my CF installation i need to worry about?

     

    ty Jose

    BKBK
    Community Expert
    Community Expert
    September 23, 2024

    A fuller explanation follows.

     

    ColdFusion's web server connector (wsconfig) does not rely on the web server's IP address. It configures the interaction between ColdFusion and IIS based on the port and context path, not the web server's IP address.. As long as the IP of the ColdFusion server itself remains unchanged, there shouldn’t be any inherent issues related to ColdFusion that require a rebuild or reinstallation. Some points to note:

    1. Usually, if there’s no change to the web server architecture (that is, no change in hostnames, port bindings, or configurations), the connector does not need to be rebuilt. So, even after changing the web server IP, wsconfig/connector does not need to be rebuilt unless IIS bindings or configurations have significantly changed. For example, with the CF updates indicated in the link I gave earlier.
    2.  After the web server IP changes, you have to update the IIS bindings and Hosts file. Ensure that there are no dependencies on the old IP address anywhere.
    3.  Check firewall/security rules and ensure that any DNS propagation is handled properly.
    4.  Normally, SSL certificates are tied to domain names, rather than to IP addresses, so this might not be an issue. But it's worth checking. If your SSL certificates are tied to a specific IP address, then you may need to reconfigure or reissue certificates.
    5.  If there are external services or clients that cache your web server's IP, make sure that they refresh their DNS cache to point to the new IP.
    6.  After making the changes, it is vital to perform end-to-end testing. That will ensure that the ColdFusion application is communicating correctly with IIS, and that requests are flowing as expected.