-
Bug
-
Resolution: Fixed
-
Medium
-
5.5.6-beta1, 5.5.6, 5.6.3, 5.6.4, 5.6.5, 5.7
-
None
-
OS: Windows 7 64bit
DB: Postgres
Installed Products: Jira, Stash, ConfluenceInstalled using the windows 64bit installer and the included Apache Tomcat server
Original Description
When installing confluence I set the listen port to 8096 because jira was already set up on 8090. When I closed the installer my browser poped up with a page not found message.
I later attempted to open jira and the confluence startup page was visible.
Steps to Reproduce
- Install Confluence 5.6.0 and configure a custom port
- Upgrade to 5.6.1 using the installer, and confirm that the port is preserved
- Upgrade to 5.6.5 and confirm that the port is now back to the default of 8090 in the server.xml
Fix
Edit the server.xml and correct the port number. You can find the old port number in the server.xml in the installation directory backup created by the installer.
- has a regression in
-
CONFSERVER-39985 Confluence Windows Installer and Linux installer - ignores custom port settings on upgrade
- Closed
- is caused by
-
CONFSERVER-32970 server.xml contains incorrect parameters for threads in the default connector
- Closed
- is duplicated by
-
CONFSERVER-35573 Confluence installer does not keep the port settings when upgrading
- Closed
-
CONFSERVER-34744 Confluence is set up on default ports despite entering custom ports in 64 bit Linux Installer
- Closed
-
CONFSERVER-34875 Windows - 64bit Installation Wizard (Custom Install)
- Closed
-
CONFSERVER-35379 Cannot change listening port from installer
- Closed
-
CONFSERVER-35599 Windows x64 installer for Confluence 5.6.3 ignores Http Port Number
- Closed
-
CONFSERVER-35906 change port with linux installer (64 bit) failed, confluence still on 8090
- Closed
- relates to
-
CONFSERVER-24226 Confluence installer ignores custom Control Port Number
- Closed
- Testing discovered
-
CONFSERVER-36766 Confluence Installer does not update control port when installing with custom option.
- Closed