Skip to main content
royarpit
New Member
April 22, 2021
Question

FortiManager GUI Not Accessible inspite of being able to ping it

  • April 22, 2021
  • 19 replies
  • 21432 views

Hi Experts,

 

I'm trying to setup a Virtual FortiManager on my EVE-NG platform. I have performed the following configurations on it through the CLI:

config system interface     edit "port2"         set ip 192.168.1.200 255.255.255.0         set allowaccess ping https ssh http     next end

My workstation IP is 192.168.1.14 and I'm am able to ping it successfully.

C:\Users\Arpit>ping 192.168.1.200 Pinging 192.168.1.200 with 32 bytes of data: Reply from 192.168.1.200: bytes=32 time=119ms TTL=64 Reply from 192.168.1.200: bytes=32 time=211ms TTL=64 Reply from 192.168.1.200: bytes=32 time=307ms TTL=64 Reply from 192.168.1.200: bytes=32 time=389ms TTL=64 Ping statistics for 192.168.1.200:     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 119ms, Maximum = 389ms, Average = 256ms

However, whenever I try to access the FortiManager WebGUI on a browser (Chrome, FireFox, etc.) I receive the following error:

This site can’t be reached

192.168.1.200 refused to connect.

 

If someone is aware of this problem, kindly let me know how I could rectify this to access the FMG WebGUI.

Any help would be greatly appreciated :)

 

Regards,

Arpit Roy

    19 replies

    ilan
    New Member
    April 22, 2021

    Hi Arpit,

     

    In your Port2 allow webservice

    set allowaccess webservice ping http https ssh

    royarpit
    royarpitAuthor
    New Member
    April 22, 2021

    ilan wrote:

    Hi Arpit,

     

    In your Port2 allow webservice

    set allowaccess webservice ping http https ssh

     

    HI Ilan,

     

    Thanks for your kind response.

     

    I tried the following configuration, but still no luck :(

    (port2)# show config system interface     edit "port2"         set ip 192.168.1.200 255.255.255.0         set allowaccess ping https ssh http webservice     next end

    Getting the following error:

    Unable to connect Firefox can’t establish a connection to the server at 192.168.1.200.

     

    Kindly advise.

     

    Regards,

    Arpit Roy

    Jayanb
    New Member
    September 17, 2021

    Hi Arpit,

    Did you fixed this issue?

     

    Regards

    Jayan

    paulinster
    Visitor III
    September 17, 2021

    You may want to look at your admins users. There may be some restricted host set. In CLi you may look at something like this ... 

     

    config system admin user     edit "admin"         set trusthost1 208.x.x.x 255.255.255.224         set trusthost2 208.x.y.y 255.255.255.240         set trusthost3 192.x.x.x 255.255.255.0

     

     

    Mikiyas_D
    New Member
    June 23, 2022

    Hello, Royarpit This could be the most delayed response you've ever received. nonetheless, I used two steps to resolve my problem. One, I set the web service's allow-access option, and two, I increased the device's RAM by one GB. total 2048eve-ng.png

    eve-ng1.png

    Syawal_adhitya
    New Member
    June 28, 2022

    Hello Miki

    i have a problem, and i have followed your suggestion like add RAM with your suggested and set allow-access in FMG configuration but still not working.1.png2.png

    3.png

     

     

    Thanks
    Syawal Adhitya

    Djihane
    New Member
    May 9, 2023

    Hello, did you find the solution because i have the same problem as you. If you find it please share it with me

    Thank you.

    Iraj
    New Member
    November 21, 2024

    I had the same problem, Just increased the RAM to 4GB (4096)

    wpaz
    Explorer II
    September 19, 2023

     I had the same problem, and resolve increase the memory to 8192 and 4 cpu.

    Before that the fortimanager was try to create the LVM but does not work, and after increase the memory and cpu, works as expected.

     



    Keilon
    New Member
    December 10, 2023

    This work for me.

    ede_pfau
    SuperUser
    SuperUser
    November 11, 2023

    In case you try to connect from a different subnet, you need to install a default route first:

    conf sys route

    edit 0

    set dstint port1

    set dest 0.0.0.0/0

    set gateway x.x.x.x

    next

    end

    (from memory, you'll find the exact syntax, it's similar to FortiOS).

    Of course, this is not the root cause if your PC is on the same subnet. A valid ping test will show you that a route is not needed.

     

    And, for "trusted hosts", these are not preset in a new VM.

    Ghofrane35
    New Member
    September 24, 2024

    i have problem who can help me 

    i can't ping to the @OFIvolve fortinet from cmd also i Can't ping to 8.8.8.8 and the GUI is not connect err fgt.JPGsite unr.JPG neeeeed help plzzz

    Iraj
    New Member
    November 21, 2024

    Just increase the RAM to 4BG (4096).

    good luck

    sw2090
    SuperUser
    SuperUser
    May 7, 2025

    just as a tip: ping is kernel based while http(s) is a service.

    So ping may work but http(s) may not.

    In this case you coud try to debug it on cli with somethng like

    dia debug enable

    dia debug app httpd/httpsd 

     

    this will give you some debug log output that might give you a clue on what is  wrong.

    TharukaRajapaksha
    New Member
    June 30, 2025

    After increasing both CPU & Memory (upto 4 & 4096) it worked. Thanks for the help.

     

     

     

     

    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!