Skip to main content
S
SP_137340013-Newcomer
3-Newcomer
June 12, 2026
Solved

Dashboards are not Accessible on Runtime.

  • June 12, 2026
  • 2 replies
  • 41 views

I am using ThingWorx Platform Release 9.1 and DatecodeSP1 Users or Developers are not able to see the mashup Runtime, even though they are in the "Administrators" group. Sometimes, after restarting the laptop or incognito Runtime shows up, but most of the time, the dashboards won't come up. We tried in different ways:

1. Different Browsers

2. Restarted Laptops

3. Incognito Windows

4. Restarted the Thingworx with clearing cache When the Runtime Dashboard is opened, we get HTTP Status 403 – Forbidden Here are the errors that I faced HTTP Status 403 – Forbidden

Best answer by abandal

Hello ​@SP_13734001,

 

To help narrow this down, could you please confirm a few details:

  1. Are you using ThingWorx basic authentication or (LDAP/SSO method)?
  2. Does this behavior occur for all users or only certain users, even if they belong to the Administrators group?
  3. Do the affected users have Run Time and Visibility permissions not just on the mashup, but also on all dependent entities (Things, Services, Data Shapes, etc.)?
  4. Are users able to open the mashup in Composer preview, or does it fail only in runtime?
  5. Could you share any relevant entries from the ApplicationLog.log when the 403 occurs (especially authorization or security-related errors)?
  6. When the issue occurs, do you see any failed requests or errors in the browser Developer Tools (Console/Network tab)?
  7. Are you accessing ThingWorx via a reverse proxy or load balancer, or directly on the server?

From the behavior you described (working in incognito and after restart), this could also be related to session/cookie handling or cached authentication state, so checking browser/network logs will be very helpful.

Looking forward to your findings, this will help identify whether the issue is permission-related, session-related, or environment-specific.

 

Regards,

Abhi

2 replies

A
abandalCommunity ManagerAnswer
Support
June 22, 2026

Hello ​@SP_13734001,

 

To help narrow this down, could you please confirm a few details:

  1. Are you using ThingWorx basic authentication or (LDAP/SSO method)?
  2. Does this behavior occur for all users or only certain users, even if they belong to the Administrators group?
  3. Do the affected users have Run Time and Visibility permissions not just on the mashup, but also on all dependent entities (Things, Services, Data Shapes, etc.)?
  4. Are users able to open the mashup in Composer preview, or does it fail only in runtime?
  5. Could you share any relevant entries from the ApplicationLog.log when the 403 occurs (especially authorization or security-related errors)?
  6. When the issue occurs, do you see any failed requests or errors in the browser Developer Tools (Console/Network tab)?
  7. Are you accessing ThingWorx via a reverse proxy or load balancer, or directly on the server?

From the behavior you described (working in incognito and after restart), this could also be related to session/cookie handling or cached authentication state, so checking browser/network logs will be very helpful.

Looking forward to your findings, this will help identify whether the issue is permission-related, session-related, or environment-specific.

 

Regards,

Abhi

A
abandalCommunity Manager
Support
June 30, 2026

Hello ​@SP_13734001,

 

I hope you’re doing well.

 

I wanted to follow up on my previous message regarding the details needed to better understand your requirement. Could you please share the requested information when you have a chance?

 

Also, if the issue has already been resolved, please let us know—this would be helpful for other community members who might be facing a similar situation.

 

Regards,

Abhi

Terms & ConditionsAccessibility statement