Customer Portal loading up blank after a Jira upgrade
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
要約
After performing a Jira upgrade, you notice that the customer portal page is showing completely blank on the browser.
No apparent errors are shown on the browser, on a HAR file, or on the Jira logs about it, and you have confirmed that have the appropriate version of Service Desk installed and enabled.
環境
Jira service desk configured with SSL (prior to the upgrade).
診断
Check the Browser console logs from when loading up the blank customer portal page.
- Open the Developer tools by pressing F12.
- Switch to the Console tab
- Right-click at any place in the console content, and choose "Save as...".
With the saved results, look for occurrences of Mixed Content errors informing that This request has been blocked; the content must be served over HTTPS.
例:
Mixed Content: The page at 'https://JiraBaseURL.com/servicedesk/customer/portals' was loaded over HTTPS, but requested an insecure script 'http://JiraBaseURL.com/s/34cf567dff4d26da16adf1dc36f9bc3c-CDN/31dj44/940000/iwvr1za/a0000dc68b693301/c7d809889492d9ff_/download/contextbatch/js/async-chunk-cv-help-center-portal-page,-customerportal,-com.atlassian.analytics.analytics-client:js-events,-jira.webresources:almond/batch.js?locale=en-UK'. This request has been blocked; the content must be served over HTTPS.原因
As is mentioned in the Upgrading Jira Data Center documents, after performing a Jira upgrade, customizations applied to its Installation Directory, such as SSL settings, are overwritten back to their defaults.
This means that any SSL settings that were applied to your instance have been lost, and because of it, although you are attempting to still access Jira with HTTPS, its server settings are configured to only provide HTTP connections.
ソリューション
In order to solve the issues with the customer portal, and ensure your instance is operating with SSL enabled, you'll need to re-apply the lost customizations to your instance.
This can more easily be achieved by copying the connector details from the previous version of Jira, or they can be manually re-applied using the same instructions utilized when initially setting up SSL.