'Can't connect to your site' error in the Confluence Data Center and Server mobile app

Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.

*Except Fisheye and Crucible

Problem

The Confluence Data Center and Server mobile app throws one of the following errors a user tries to connect it to an existing Confluence server site, or when they are using the app.

Can't connect to your site

This could be because you need to use a VPN, the URL is wrong, or Confluence is unavailable.

Can't connect to your site

We couldn't get a HTTPS connection to your site.

Your site is unavailable or you need to connect to your VPN or network to access it. 

Cause

This error appears when the mobile app can't reach the Confluence site at all. This may be because:

  • the Confluence site URL entered in the login screen is incorrect

  • you've entered the URL with HTTPS, but the site is HTTP (or vice versa)

  • HTTPS is enabled, but the Confluence base URL is set to HTTP

  • the Confluence site is only accessible when connected to a virtual private network (VPN)

  • the Confluence site is currently down or unavailable, for example for scheduled maintenance or upgrade

  • your network configuration may be preventing unauthenticated requests to your server

  • your proxy server is filtering out headers or cookies required by the mobile app

Before you start — try this 30-second check

  1. Open your device's browser (Safari, Chrome, etc).

  2. Type your Confluence site URL exactly as you entered it in the app, including any context path (e.g. mycompany.com/confluence).

  3. If the browser can't reach the site either, the problem is the URL or network — not the mobile app. Skip to the URL / VPN checks below.

  4. If the browser reaches the site but the app cannot, the problem is most likely a proxy / header / cookie issue — skip to the proxy check below.

Resolution

Resolution — work through these in order:

  1. Confirm the URL is correct. Re-enter the Confluence site URL including the context path (e.g. mycompany.com/confluence). Try omitting http:// or https:// — the app will try both.

  2. Confirm scheme alignment. If you entered https:// but the site is served over HTTP (or vice versa), the app will fail to connect. The Confluence base URL setting (Admin → General configuration → Server Base URL) should match the scheme the app uses.

  3. Confirm browser reachability. Open the same URL in your device's browser. If the browser also fails, the issue is network / DNS / VPN — not the app.

  4. Connect to VPN if required. If your Confluence site is only accessible behind a VPN, connect first.

  5. Check proxy / header / cookie configuration. If the browser can reach the site but the app cannot, your proxy server may be filtering headers or cookies the app requires. See Problems with logging in because of missing headers or cookies.

  6. Check for scheduled maintenance. Confirm with your Confluence administrator that the site is not currently down for upgrade or maintenance.

  7. Platform-specific: if you only see this error on Android but see a different compatibility error on iOS, see 'Can't check compatibility' error in the Confluence Data Center and Server mobile app instead.

If the issue persists

Talk to your Confluence administrator and provide:

  • The exact URL you entered in the app.

  • Whether the browser on the same device can reach the site.

  • Whether you are connected to a VPN.

  • The exact error message wording shown (there are two variants — "couldn't get a HTTPS connection" vs "your site is unavailable or you need to connect to your VPN").

Updated on May 27, 2026

Still need help?

The Atlassian Community is here for you.