Troubleshooting ☁️

Jupyter Viewer for Confluence Cloud: page-attached notebooks do not render; Atlassian authorization error

Problem

Page-attached notebooks do not render within the Insert/Edit macro browser preview window or in-page. Instead, an “Atlassian authorization” error is displayed. 

There are three known causes of this erroneous behavior:

• Missing space permissions for the app

• App is not allowed to view a restricted page and its attachments

• IP allowlisting is enabled

• Notebook URL is from an unsupported location

Solutions

Space permission

The app does not have permission to the Confluence Space containing the notebook attachment.

To resolve, following the Permission Configuration settings in the Installation guide.

Allowlisting

IP “Allowlisting” (a “Premium” feature) is enabled in the Confluence Cloud security settings.

To resolve, either:

• Disable this Confluence Cloud feature for the site

• Whitelist the IP range used by Jupyter Viewer

  • The app uses the Heroku platform in the European zone, so the IP used may be from anywhere in the AWS European range. The latest AWS IP ranges can be programmatically queried by following the AWS guide.

Supported notebook locations

Check that the Notebook URL is from a supported notebook location.

Page Restrictions

If the Confluence page has restrictions, allow the app "IPython Notebook Viewer for Confluence" to view the page.

Is it possible to define an external Jupyter renderer for IPython Notebook Viewer for Confluence?

It is not possible to define an external renderer. The rendering happens with JavaScript on the client for the cloud and server app.

Why isn’t the macro visible to guest or anonymous users?

We’re currently transitioning our Jupyter Viewer for Confluence macro from Atlassian Connect to Atlassian Forge, Atlassian’s modern cloud development platform.

At this time, Forge does not support execution for guest or anonymous users. This includes:

• Anonymous users (not logged into Confluence)

• Guest users (external collaborators with limited permissions)

When these users view a page containing a Forge-based macro, the macro will not render and may display an error like:

This is a known limitation on the Atlassian platform and is being tracked here: CONFCLOUD-80208. Atlassian has not yet provided a timeline for support.

What can I do?

• Ensure the page is only shared with authenticated Confluence users who have appropriate access.

• If guest or anonymous access is critical to your workflow, please reach out to us.

We will update our macro functionality as soon as guest or anonymous access becomes supported on the Forge platform.