- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-20-2022 01:57 PM
Hi Everyone.
I am having an issue in selecting the publish appliations in clientless vpn apps.
Prior to the recent firewall upgrade , I was able to use published apps configured for Clientless VPN, and now it is not working. I get error message 404 page not found whenever I select a published application.
Here is a summary of my issue.
I can login to the portal successfully
Download Global Protect files successfully
Select published apps unsuccessfully (not working)
anyone have this issue lately please let me know, i am suspecting that this might be a bug in Pan OS, my current OS version is 10.2.2.
Any help in this regard will be highly appreciated.
Thank you in Advance.
08-31-2022 10:10 PM
Ran into this issue as well, when we moved over to 10.2.2. There is something wrong with 95-239 and 10.2.2. We rolled the clientless application down to panup-all-gp-89-207, (no reason other than the date looked good.) once manually installing file from the GUI, we installed the older version and turned off the schedule updates. Once panup-all-gp-89-207 was marked as currently installed all our clientless apps came live again.
07-21-2022 03:52 PM
What release were you running prior just so we know how many major versions you jumped. PAN-OS 10.2.2 doesn't have any known issues with clientless VPN.
07-22-2022 06:58 AM
I'm having the same issue. I upgraded from 10.1.5 to 10.2.2
07-22-2022 07:03 AM
07-24-2022 02:48 PM
was having the same issue, just try to disable clientless VPN commit and enabled > commit
make sure the clear browser cookies etc as well.
08-12-2022 11:40 AM
We are having the same issue, we migrated from PA-850 (OS 9.1.7) to PA-460 (OS 10.2.2), the published app shows "404 page not found". I tried disabling the Clineless App option on the portal per the suggestion above and re-enabling it, still the same issue.
Any other suggestions?
08-12-2022 11:54 AM
Hello
I will recommend you open the case with support. So far when i worked with support we performed the following tasks:
added a static entry to application in clientless vpn setting as we were not able to see DNS cache entries
reverted back the version of Global protect clientless vpn under dynamic updates and tested the access which didn't work.
added a secondary test application to clientless vpn settings which also didn't work
monitored traffic logs from user source IP and it showed the action drop by default policy
added a test rule allowing the application access from SSL VPN zone after that applications worked.
upgraded back the GP clientless vpn under dynamic updates to recent version
tested the application access and observed the DNS cache entries in palo alto cli logs.
08-14-2022 07:30 AM
Are the apps published based on users or user groups? If so, check if setting the user to 'all' helps.
I've seen a similar User-ID issue which I believe will be fixed in 10.2.3.
08-17-2022 01:04 PM
Hello. We had the same situation here. We went back to version 1.1.6-h6 and it didn't fix it. So we suspect it could be something else. We did more tests and found that the license had a problem. Maybe it got corrupted. We reapplied it and it started working again.
Maybe it will help you too.
08-31-2022 10:10 PM
Ran into this issue as well, when we moved over to 10.2.2. There is something wrong with 95-239 and 10.2.2. We rolled the clientless application down to panup-all-gp-89-207, (no reason other than the date looked good.) once manually installing file from the GUI, we installed the older version and turned off the schedule updates. Once panup-all-gp-89-207 was marked as currently installed all our clientless apps came live again.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!