Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-26550

Confluence installer does not detect modifications to server.xml

      The Confluence installer appears to not detect modifications to server.xml

      For our deployment of Confluence Standalone on Linux, we have it running behind a proxy server out of a subdirectory on our domain. As such, we have a modified server.xml that changes the port, sets the proxy domain name and port, and sets the root directory.

      Upgrading Confluence via the installer catches other modified or unrecognized files, but does not appear to recognize changes to server.xml and, as such, we are forced to manually updated server.xml each time.

            [CONFSERVER-26550] Confluence installer does not detect modifications to server.xml

            It would be great if changes to context.xml could also be considered. If not, please let me know if this requires a new issue to be created (or there's already an existing one).

            Matthias Voss (Bekast) added a comment - It would be great if changes to context.xml could also be considered. If not, please let me know if this requires a new issue to be created (or there's already an existing one).

            This is especially critical due to this bug (workaround gets lost on every update).

            Matthias Voss (Bekast) added a comment - This is especially critical due to this bug (workaround gets lost on every update).

            The ports should be migrated on upgrade, that is being tracked in CONF-39985.

            Leaving this ticket open to track the request to migrate all modifications in the server.xml.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - The ports should be migrated on upgrade, that is being tracked in CONF-39985 . Leaving this ticket open to track the request to migrate all modifications in the server.xml.

            I had not seen this previously, but the 5.6.4 installer did indeed fail to pick up the changed port in our server.xml, where prior installers had done so.

            Mark Bickford added a comment - I had not seen this previously, but the 5.6.4 installer did indeed fail to pick up the changed port in our server.xml, where prior installers had done so.

              Unassigned Unassigned
              dc0ea640ac68 Mahmoud Al-Qudsi
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated: