Skip to main content

​
Who this guide is for

Administrators and evaluators who see an infinite-loading board or a blank widget and need to rule out network-level causes before escalating to product support. Planningboard renders as a widget inside a Polarion LiveDoc or Wiki page. The browser page loads the Polarion host directly; the widget then makes additional HTTP requests back to the same Polarion server to load Plans, work items, and capacity data. If a corporate firewall or proxy intercepts those requests — even silently — the board spinner never resolves.
Browser connects only to the Polarion host, which routes through the Planningboard server-side plugin to the Tracker, Users/Teams, and Link Role APIs
All traffic is same-origin — the browser only ever contacts the Polarion server. There is no external CDN or cloud endpoint.
1

Confirm the Polarion host is reachable

  1. Open your browser and navigate to your Polarion instance (e.g. https://polarion.example.com/polarion/).
  2. Confirm the Polarion login page loads and you can authenticate.
  3. Navigate to the LiveDoc or Wiki page that contains the Planningboard widget.
If Polarion itself does not load, the problem is upstream of Planningboard — fix Polarion connectivity first.
2

Open the browser developer console

When the board is stuck loading, browser developer tools show exactly which request is failing.
  1. On the page with the stuck Planningboard widget, press F12 (Windows/Linux) or Cmd+Option+I (macOS) to open DevTools.
  2. Click the Network tab.
  3. Reload the page (F5 or Cmd+R).
  4. Watch for requests that are red (failed) or that hang indefinitely (no response status).
DevTools Network tab showing two hung GET requests to the Plans and work items endpoints, and a 403 response on the Users endpoint
Look for requests to /polarion/rest/ or /polarion/ws/ paths that return 0, timeout, or 403/407.
A status of 407 means a proxy server is intercepting requests and demanding credentials. The Planningboard widget’s HTTP calls do not carry proxy credentials — the browser must be configured to authenticate with the proxy, or the Polarion host must be added to the proxy bypass list.
3

Check the browser console for errors

  1. In DevTools, click the Console tab.
  2. Reload the page and look for red error messages.
Common error patterns and their causes:
4

Identify which hosts and ports must be reachable

Planningboard makes requests only to the Polarion server. The ports depend on your deployment:No other hosts, ports, or external services are required. If your Polarion is behind a reverse proxy, the proxy must forward the full request path (including /polarion/rest/ and /polarion/ws/) without stripping headers.
Planningboard does not call any external APIs, license servers, or analytics endpoints at runtime. All requests are contained within the Polarion server. An outbound-only firewall rule to the Polarion host is sufficient.
5

Check proxy bypass configuration

If your organization routes browser traffic through a proxy, add the Polarion server hostname to the proxy bypass (no-proxy) list so that same-origin requests are not intercepted.Examples by platform:Windows (Internet Options > LAN Settings > Exceptions):
macOS (System Settings > Network > Proxies > Bypass proxy settings for):
Environment variable (CLI / scripts):
After updating bypass settings, close and reopen the browser entirely before retesting.
6

Check TLS / SSL certificate trust

If your Polarion instance uses a certificate issued by a corporate or internal CA, the browser must trust that CA.
  1. Click the padlock icon in the browser address bar on the Polarion page.
  2. Verify the certificate chain shows no warnings.
  3. If there is a certificate error, ask your IT team to install the corporate root CA into the browser trust store.
Some corporate proxies perform TLS inspection (SSL bump / man-in-the-middle). They replace the server certificate with a proxy-issued certificate. If the proxy’s CA is not trusted by the browser, every HTTPS request from Planningboard fails with a certificate error. Ask your network team to exclude the Polarion host from TLS inspection, or ensure the inspection proxy’s CA is deployed to all client machines.
7

Test with a direct connection

If possible, test from a machine that is not behind the corporate firewall or proxy (for example, a home network or a mobile hotspot):
  1. Connect to the alternative network.
  2. Navigate to the Polarion Planningboard page.
  3. If the board loads correctly, the problem is confirmed to be network/firewall-specific.
This test confirms the issue is environmental and not a Planningboard configuration problem.

​
Common firewall rules to verify

Have your network or security team confirm the following:
Polarion uses long-lived connections for some server push notifications. Ensure the firewall and any load balancer in front of Polarion allow WebSocket upgrade (Connection: Upgrade, Upgrade: websocket) on the Polarion port.

​
You should now see

After resolving the network issue and reloading the page, the Planningboard widget should:
  • Render the board within a few seconds (depending on the number of Plans and work items).
  • Display swimlanes with cards populated from Polarion Plans.
  • Show no red errors in the browser console Network tab.
If the board still does not load after confirming all network paths are open, check the Common Errors guide or review Version Updates and Checking to confirm the plugin is correctly installed.

​
See also

Support TicketsSource Code
  • PlanningBoardDataService.java
  • PlanningBoardWidgetDependenciesProcessor.java
  • licenseReadonly.cy.ts
  • PlanningBoardWidgetRenderer.java
Last modified on July 9, 2026