- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to access web bookmark in ztna agentless feature
Hi team,
I have configured ztna agentless feature which introduced in 7.6 version (using 7.6.2) but getting 'site can't be accessed' error while accessing the web bookmark.
redirected url: https://10.10.1.17:4434/XX/YY/ZZ/webservice?bmgroup=bookmark&bmname=fmg&cookie=DB2B48CEE7376444186CB...
Why this XX/YY/ZZ is showing here ??
Kindly suggest.
- Labels:
-
ZTNA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We are still looking for someone to help you.
We will come back to you ASAP.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here. I created an public dns for the webserver facing the public ip of the ztna portal but no luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I found these information and hope it will help:
To troubleshoot the issue of being unable to access the web bookmark in the ZTNA agentless feature:
- Verify Configuration: Ensure that the agentless ZTNA applications are correctly configured. Check the configuration settings under Configuration > Agentless ZTNA.
- Access the Bookmark Portal**: Navigate to Configuration > Agentless ZTNA, click on the Private applications tab, In the top-right corner, click on Bookmark portal, copy the link from the Bookmark portal link field and paste it into a web browser to access the portal.
- Check Prerequisites: Ensure that all prerequisites for agentless ZTNA are met. Refer to the prerequisites documentation for any missing requirements.
- Network Connectivity: Verify that there are no network connectivity issues preventing access to the portal.
- Application Assignment: Ensure that each web-based application is assigned a custom domain name associated with the FortiSASE instance.
- Compatibility: Confirm that the setup does not involve SPA hubs configured with BGP on loopback or private web-based applications with the Server Type set to FQDN, as these are not supported.
