>
    Strata Copilot
    Prisma Access Agent 26.2 Known Issues
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma Access Agent
    3. Prisma Access Agent Release Notes
    4. Prisma Access Agent Release Information
    5. Prisma Access Agent Known Issues
    6. Prisma Access Agent 26.2 Known Issues
    Download PDF
    Prisma Access Agent

    Prisma Access Agent 26.2 Known Issues

    Table of Contents

    Prisma Access Agent 26.2 Known Issues

    Review the known issues in Prisma Access Agent 26.2.
    Prisma Access Agent version 26.2 has the following known issues:
    Issue IDDescription
    PANG-11923
    On Linux devices, Prisma Access Agent signs users out without warning when the Re-authentication Frequency timer expires.
    When the user refresh token expires, the Prisma Access Agent signs the user out of the Endpoint Manager and disconnects the tunnel. On Windows and macOS, the agent notifies users before the token expires — giving them time to re-authenticate without losing their session. On Linux, notification support is not yet implemented, so the logout occurs without any warning and users see no message explaining why they were signed out.
    The Re-authentication Frequency setting controls how long a user session remains valid before re-authentication is required. The default is 7 days, but if your organization has configured a shorter interval, Linux users may be signed out sooner than expected.
    Workaround: To reduce unexpected sign-outs, increase the Re-authentication Frequency interval in your Global Agent Settings. Inform Linux users that periodic sign-outs are expected and that they must sign back in to restore access.
    PANG-12348On Linux devices, Prisma Access Agent installation does not complete when the AppImage file is stored in a directory whose name contains spaces. The installation appears to start but does not finish successfully.
    Workaround: Move the AppImage file to a directory whose name contains no spaces before running the installation.
    PANG-12303For Docker containers in a Prisma Access Agent-deployed Linux environment, domain-based blocking rules configured in a forwarding profile do not apply to domains that contain uppercase characters. For example, if a rule is configured to block "*.facebook.com", requests to www.facebook.com are blocked as expected. However, requests to "WWW.FACEBOOK.COM" are allowed and forwarded, even though domain names are case-insensitive.
    PANG-12226For Docker containers in a Prisma Access Agent-deployed Linux environment, after a secure tunnel is disconnected, a security policy block rule applied to a container does not prevent traffic flow. This issue occurs specifically when containers are configured in default bridge mode. The block rule functions correctly only when the tunnel is active.
    PANG-12224On Linux virtual machines (VMs), when you uninstall and reinstall Prisma Access Agent, the machine ID reported to the endpoint manager changes. This occurs because Prisma Access Agent derives the machine ID from the MAC address of the first available network interface, which may be a Docker interface rather than a stable system identifier. As a result, the endpoint manager receives a new, unrecognized machine ID on the next enrollment attempt. When anti-spoofing is enabled on the endpoint manager, enrollment is rejected with a 409 Conflict error. When anti-spoofing is disabled, the endpoint manager inventory is updated with the new machine ID instead.
    PANG-12223When the sudo pkill -SIGHUP -f PASrv command is executed, the PASrv process for Prisma Access Agent on Linux terminates unexpectedly. This action causes the secure tunnel to disconnect and the agent to lose its connection to the Endpoint Manager. The agent cannot re-establish its connection to the Endpoint Manager, even after reinstallation, resulting in a complete service outage.
    PANG-12217On Linux systems running Ubuntu 22, the Prisma Access Agent user interface does not switch to the dark theme when the system theme is changed. Although the theme selection drop-down indicates "Dark theme," the UI appearance remains unchanged.
    PANG-12205On Linux devices, the Prisma Access Agent does not reconnect to the internal gateway it was previously connected to after a temporary network disruption, such as an Ethernet cable disconnection and reconnection. Instead, the agent connects to the best available gateway.
    PANG-11945On Linux distributions (for example, Fedora) running Prisma Access Agent Version 26.2.0.34, traffic originating from Podman containers is processed differently than traffic from Docker containers. While Docker container traffic is directed through a tunnel and only block rules are applied, Podman container traffic has security policies applied and flows as if originating from the host system.
    PANG-11860After installing the Prisma Access Agent for Linux on ARM Red Hat 9.6 systems and connecting it to the Endpoint Manager and gateway, debug messages print out on the console. This output occurs consistently after installation and connection.
    PANG-11687When a Linux device running the Prisma Access Agent switches network environments (for example, moving from a corporate network to a home network), the Prisma Access Agent might become disconnected and its tunnel status displays as "Undefined". This causes the Prisma Access Agent user interface to become unresponsive, preventing users from reconnecting.
    PANG-11379After a fresh installation of the Prisma Access Agent on Linux operating systems, the agent does not successfully enroll and authenticate to the endpoint manager on the first attempt. Even after an initial authentication, the user interface indicates that the user is not enrolled, requiring a second authentication attempt to complete the process.
    PANG-7726On macOS devices, communication with multicast addresses is unsuccessful when the Prisma Access Agent's extensions are enabled but Prisma Access Agent is not connected.

    © 2026 Palo Alto Networks, Inc. All rights reserved.