Skip to content

PLOSSYS Administrator

Here, you find possible solutions to problems that can occur with PLOSSYS Administrator when installing or running PLOSSYS Output Engine.

No Dashboard After Updating to 5.3.2

With PLOSSYS 5.3.2, the dashboard of PLOSSYS Administrator has been secured. In order that the user can see the dashboard, the dashbord area has to be specified in the ALLOWED_OIDC_CLIENTS key. For more information, refer to ALLOWED_OIDC_CLIENTS.

Flickering Browser When Opening PLOSSYS Administrator

If you cannot open the user interface, PLOSSYS Administrator, and the browser is flickering, the reason could be be one of the following situations:

  • Check the configuration for the OIDC identity provider. Check if the AUTH_ISSUER_URL and the ID_PROVIDER_NAME environment variables are specified correctly. For more information, refer to Configure the PLOSSYS Administrator Environment.

  • The HTTP code 304 (Not Modified) is returned erroneously by the services. This is shown in the log data. Then deactivate the ETag handling by setting USE_ETAG to N.

Loading Browser When Opening PLOSSYS Administrator

If Loading... is the only thing you get when opening the user interface, PLOSSYS Administrator, the reason could be the following situation:

  • You do not have the permission to do anything with PLOSSYS Administrator. In the OIDC identity provider, check if you have a role assigned that has permissions for PLOSSYS Administrator.

Erroneous Job With Virtual Queue

With a virtual failover queue, all queues involved have to be configured in PLOSSYS Output Engine. Otherwise, the jobs for the virtual queue will terminate as erroneous.

Queue Does Not Respond

If a queue no longer respond and no longer print, reactivate the queue by pausing and resuming it in PLOSSYS Administrator. When pausing the queue, all locks will be removed.

Back to top