'Can't check compatibility' error in the Confluence Data Center and Server mobile app
プラットフォームについて: 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 は除く
問題
The Confluence Data Center and Server mobile app throws the following errors when user tries to connect it to an existing Confluence server site.
Can't check compatibility
A custom filter within a virtual private network (VPN) or firewall may be preventing unauthenticated requests to your server. Talk to your network admin to resolve this.
または
Can't check compatibility
A custom filter may be preventing unauthenticated requests to your server. Talk to your admin to resolve this.
原因
- The Confluence Data Center and Server mobile app needs to check that you're running a compatible version of Confluence before it can log you in. If you have configured a custom filter in the VPN or firewall to prevent unauthenticated requests to your server, Confluence will be unable to complete this check.
- Also, if you're using a proxy server, it might be filtering some headers or cookies required by the mobile app.
ソリューション
If you distribute the Confluence Mobile app using an MDM solution (Mobile Device Management), you can add the skipInfo parameter to the app config which will skip this check. See Mobile Device Management (MDM) for more information.
Otherwise, to resolve this issue, you will need to configure your custom filter to allow our check to pass through without authentication.
- For Confluence 7.6 and later, allowlist
<confluence-base-url>/rest/nativemobile/1.0/info/login. - For earlier versions of the mobile app and Confluence (7.5 and earlier), allowlist
<confluence-base-url>/server-info.action.
Additionally, you might need to allowlist headers and cookies required by the mobile app. For more info, see Problems with logging in because of missing headers or cookies.
Not an admin? Send this page to your Confluence administrator and ask them to investigate the issue for you.