How to Troubleshoot the issue with MetaDefender MFT not reachable after enabling HTTPS
This knowledge base article provides step-by-step instructions for checking and resolving the issue when MetaDefender Vault becomes unreachable after enabling HTTPS.
This situation is usually caused by a process using the port 80 while NGINX is also trying to use that server. To check if this is true, please follow the below steps:
- Run the command netstat -np TCP | find ":80" in CMD admin to view the existing processes using port 80
- Once identified, copy the PID inside the command tasklist.exe /v /fi "PID eq 777", replace 777 with the PID of the process that uses port 80.
- If the Process is System, then it means that the server has the IIS service installed.
Moving forward, please check if the process identified can be removed or not.
- If the process can be removed, please remove it, and restart the MetaDefender Vault Helper Service (vaultHelper) , then MetaDefender Vault should come up.
- If the process cannot be removed, please follow the below steps:
- Please navigate to
C:\Program Files\OPSWAT\MetaDefender Vault\WebServer\conf
and opendynamic.conf
in a Notepad run as admin. - Remove the following lines: server {
- Please navigate to
listen 0.0.0.0:80;
return 301 https://$host:8010$request_uri;
}
- Once edited, please save and close the dynamic.conf
Was this page helpful?