Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
khalilbouzaiene1
Contributor

can't access to the gui of fortianalyser docker

i have deployed fortianalyser container with this command 

Docker run -it --restart always -p <Port Mapping>:443 -p <Port Mapping>:22 -p <Port Mapping>:541 --cap-add=ALL <image ID>:<Tag>
and then i go to the browser i put localhost:39443, it says  

"This site can’t be reached

The connection was reset."

is the image fortinet/fortianalyser not stable or what !!
what is the solution please  !!?

1 Solution
khalilbouzaiene1

Yes, that's what I thought too. So, I used the command '

docker run -it --restart always -p 8080:80 -p 3922:22 -p 541:541 --cap-add=ALL fortinet/fortianalyzer:latest'

to map port number 80 to 8080. However, the result remained unchanged !!

View solution in original post

6 REPLIES 6
srajeswaran
Staff
Staff

The https port mapped is 443, but you are trying to access it via 39443, can you please clarify?

Do you have CLI access? Can you verify the installation was completed successfully as suggested in below article?

https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-FortiManager-FortiAnalyzer-deployment-...

Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

khalilbouzaiene1

hello srajeswaran 
the full commade that i used it is :
docker run -it --restart always -d -p 39443:443 -p 3922:22 -p 541:541 --cap-add=ALL fortinet/fortianalyzer:latest
and then i write localhost:39443 in the browser and no thing happen just the message
also  i don't have CLI access and i followed that article step by step but no result !!!


srajeswaran

Can you try connecting via SSH 3922 port , this could confirm if the issue is with web ui or the image itself?

Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

khalilbouzaiene1

i have just tryed to connect to the container via ssh by this commande :
ssh admin@localhost -p 3922

and the result was :
kex_exchange_identification: Connection closed by remote host
Connection closed by ::1 port 3922

the problem in the image !?

srajeswaran

It don't look like a problem with image, but since we are not able to have access we can't check it.
Can you activate a new instance , and add port mapping for port80 (http)) as well, this should avoid issues with certificates/encryption algorithms etc (which looks like the case in the current instance).


Regards,

Suraj

- Have you found a solution? Then give your helper a "Kudos" and mark the solution.

khalilbouzaiene1

Yes, that's what I thought too. So, I used the command '

docker run -it --restart always -p 8080:80 -p 3922:22 -p 541:541 --cap-add=ALL fortinet/fortianalyzer:latest'

to map port number 80 to 8080. However, the result remained unchanged !!

Labels
Top Kudoed Authors