How to bind Confluence to a particular network interface
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
目的
By default, Tomcat will bind *:port when reading in a connector; that is, it will listen on every IP/Interface. In situations where a server has more than one network interface card, you can bind to a specific one by adding the address element to the connector configuration.
ソリューション
Change the server.xml file by adding an address element:
<Connector port="8080" connectionTimeout="20000" redirectPort="8443"
address="192.168.1.1"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"/>
...
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">Also, change the hostname from localhost to the relevant host name. In the file above, they are on the same IP.