Skip to main content
jiahoong112
Staff
Staff
April 1, 2025

Technical Tip: Agentless ZTNA Access Proxy Portal unable to access internal HTTP/HTTPS resources using ‘apptype web’

  • April 1, 2025
  • 0 replies
  • 2574 views

Description

This article describes what is required to access internal HTTP/HTTPS resources with 'apptype web'.


Agentless ZTNA Access Proxy portal is a new feature as of 7.6.1: ZTNA agentless web-based application access 7.6.1.


To initiate the configuration for this, follow this KB article: Technical Tip: How to configure clientless ZTNA with FortiGate v7.6.

Scope

FortiGate v7.6.1 and above.

Solution

Topology:

FortiGate-800D (public/external ip: 10.56.241.104) ===IPsec=== Remote-FortiGate === internal-web-server (10.191.1.231).

 

Problematic configuration of 'apptype web'. 'https-win-server' is the internal resource of interest:

 

jiahoong112_0-1743491979428.png

 

Agentless ZTNA Access portal:

 

jiahoong112_1-1743491979429.png

 

 

The RDP and web server are on the same IP, 10.191.1.231. RDP works, access to a public domain like yahoo.com works, but access to the internal web server via HTTP/HTTPS, where RDP was successful, fails.

 

clientlessztna-kb.gif

 

To fix this, a VIP object must be configured in Remote-FortiGate (not the FortiGate-800D, which provides the web-portal web service). This VIP must translate the public IP to the internal IP of the web-server.


This has to be done even though the internal IP can be directly accessed. In other words, this VIP must be accessible from a public domain so that it can be accessed through the Agentless ZTNA access proxy portal.

 

Create the VIP:

 

jiahoong112_2-1743491979433.png

 

Create a firewall policy (in Remote-FortiGate) so that the VIP can be accessed:

 

jiahoong112_3-1743491979435.png

 

Change the configuration of the ZTNA web portal as such:

 

jiahoong112_4-1743491979438.png

 

jiahoong112_5-1743491979440.png

 

The web server access has been changed to use the public IP, which is the external IP of the VIP, instead of directly using the internal IP.

 

The result is that the internal web-server is now accessible via HTTP/HTTPS through the Agentless ZTNA Access Proxy portal: 


clientlessztna-kb-working.gif

 

Traffic will match the proxy-policy in FortiGate-800D and firewall-policy (of VIP) in Remote-FortiGate.

To ensure optimal DNS resolution results, see this article: Technical Tip: Unable to access ZTNA Agentless web-based bookmarks.