Confluence fails to start on port 80 or 443 with "Permission denied" error in logs

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: 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 は除く

問題

Confluence fails to start up, and a "Failed to initialize component" error shows in the catalina.out followed by a "permission denied" cause:

catalina.out
12-Mar-2019 16:44:49.905 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-80]]
...
Caused by: java.net.SocketException: Permission denied


原因

The error above indicates the Tomcat cannot start the server to accept connections due to permissions issues. [Connector[HTTP/1.1-80]] indicates Confluence is attempting to start on port 80, which is often restricted for security purposes on many operating systems.

ソリューション

There are two options for resolving this:

  • Run Confluence on a non-restricted port, such as 8090 (the default port for Confluence)
  • Install a reverse proxy to redirect requests from port 80 and 443 to the internal server. For recommended reverse proxy configurations, see the articles linked from Proxy and HTTPS setup for Confluence.


説明 Explanation of why an application server might not start up on port 80
製品Confluence Jira
最終更新日 2019 年 6 月 13 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.