Skip to main content
Fort-zender
New Member
Jan 22, 2024 1:11 PM UTC
Solved

SSL VPN avoid IP access

Hi all,

 

Is there a way to restrict SSL-VPN access solely to the FQDN, disallowing users from accessing the web portal via the IP address? We prefer users to only use the FQDN for access.

OR

Can we use multiple server certificates that cover both IP and FQDN, eliminating certificate warnings?

 

Any lead?

Hong_FTNT
Hong_FTNTAnswer
Staff & Editor
Jan 22, 2024 2:24 PM UTC

Hi @Fort-zender,

 

There is no way to allow FQDN and deny IP address as FortiGate always see traffic coming from IP addresses. FQDN is resolved at the client side.

 

To avoid certificate warning, you can add FortiGates IP address to the SAN field of the certificate: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Adding-SAN-Subject-Alternative-Name-while/ta-p/213434

 

Regards, 

3 replies

AEK
SuperUser
SuperUser
Jan 22, 2024 2:11 PM UTC

Hello

I don't think FGT can deny VPN by IP and allow with FQDN.

On the other hand you can have one single private or public certificate for both IP and FQDN.

AEK
mle2802
Staff
Staff
Jan 22, 2024 2:23 PM UTC

Hi @Fort-zender,

You can use SAN certificate for both FQDN and IP.

Hong_FTNT
Staff & Editor
Hong_FTNTAnswer
Staff & Editor
Jan 22, 2024 2:24 PM UTC

Hi @Fort-zender,

 

There is no way to allow FQDN and deny IP address as FortiGate always see traffic coming from IP addresses. FQDN is resolved at the client side.

 

To avoid certificate warning, you can add FortiGates IP address to the SAN field of the certificate: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Adding-SAN-Subject-Alternative-Name-while/ta-p/213434

 

Regards, 

Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024