HFS can't use port 80 on Windows server essentials 2019

[rubberbutt]

Hello all.

First of all, i'm a big fan of HFS. I've installed it on my home laptop, and works fine(windows 10 Pro-64 bit).
I've also installed hfs on a Windows server 2016 essentials. No problem here.

I also have a Windows server 2019 essentials, and this is where the problem is. So at this point i'm not quite sure wheter it is a HFS problem or a Microsoft problem.
The windows server is NOT a domain controller.

I want to use the hfs server on this windows 2019 essential server, but when i try to use the standard HTTP port 80 hfs reports: This port is blocked possibly by you router/or firewall.
 I switched off windows defender completely. IIS (internet information Server) is NOT running, so it can't claim port 80).
I have forwarded port 80 to my server.  But HFS refuses to accept port 80.

I know for sure that my ISP is not blocking port 80, since port 80 can be used on the windows 2016 essentials server.

When i want to run the webpage shields up (a website that can check external TCP ports_  https://www.grc.com/x/ne.dll?bh0bkyd2)   on this server it reports that all ports are blocked.

So it seems to be a windows problem ?
Is this a correct assumption ?

[danny]

When you can't get access to a port in windows, then a different piece of software is already using that port. 

It is probably http.sys
http://web.archive.org/web/20160126063606/http://www.mikeplate.com/2011/11/06/stop-http-sys-from-listening-on-port-80-in-windows/

[rubberbutt]

Hello Danny. thanks for your reply, but your suggestion did not do the trick.
 In windows powershell:
netsh http add iplisten ipaddress=192.168.2.180

But still hfs sees a blocked port 80. This is a windows problem and I will start my question on a Microsoft Technet forum.

[danny]

netsh http add iplisten ipaddress=192.168.2.180

I believe that the article wanted you to 'distract' http.sys by changing it to ipv6-only (thus ipv4 port 80 is clear). 
netsh http delete iplisten ipaddress=192.168.2.180
netsh http add iplisten ipaddress=::
netsh http show iplisten
Be sure there is no ipv4 address on that list.
netsh http show servicestate view=requestq verbose=yes

netstat -o -n -a | findstr 0.0:80
The last column of each row is the process ID, PID, which can be matched to a PID number in Task Manager details tab (and find out what has hogged the port).

P.S.  Here is the really simple firewall that I use:  https://tinywall.pados.hu/download.php  It is a whitelist type, which reduces data costs.

[rubberbutt]

typing netstat -o -n -a|findstr 0.0:80 gives me :

TCP 0.0.0:80     0.0.0.0.0    LISTENING  2504.

When i check the PID in taskmanager it turns out it is my FTP server (Wing FTP server) is allready using that port.

[danny]

When i check the PID in taskmanager it turns out it is my FTP server (Wing FTP server) is allready using that port.

In the wing admin panel, the port settings are located at Domains / mydomain / WebLink Manager / settings / Listeners  And, there you can modify the wing's http listener to use port 8080.

P.S. 
Filezilla FTP server can do FTPS (FTP over TLS) And the more modern SFTP secure connections, free. 

[rubberbutt]

Allright, I got Wftpservices stopped. Port 80 is free now.
But now i got another problem.

HFS is now running with port 80. When i click open in browser, i see the HFS homepage.

The pc where HFS is running on (192.168.2.180) is reachable bij ping command.
In fact windows defender firewall on the HFS pc is disabled.
But when i type http://192.168.2.180  i get error 404 the requested resource is not found   

[danny]

...i get error 404 the requested resource is not found...

Good news!  That is a response from an HTTP server. 
Maybe you need content at webroot, or replace the VFS?

[rubberbutt]

Something went wrong with the .vfs database (sort of unexpected shutdown). Installed hfs again, installed files realfolder etc. and it's working.
The only thing it still won't start at tcp port 80.
But as i said before, that's a windows issue. There are a lots of pages on how to deal with that problem. I still have to work it out.

[rubberbutt]

For now I have stopped the http.sys service. By editing the windows registry.
HKEY_Local_Machien\System\CurrentControlSet\Services\HTTP
changed value os start to 4 <reboot>

This is not an ideal workaround. The http service is stopped, so now you can't run IIS.
I wasn't planning on using Internet Information Server, so it's good enough for me.
Now i can switch hfs to use port 80 

[danny]

For now I have stopped the http.sys service. By editing the windows registry.  HKEY_Local_Machien\System\CurrentControlSet\Services\HTTP  changed value os start to 4 <reboot>

This is not an ideal workaround. The http service is stopped, so now you can't run IIS.  I wasn't planning on using Internet Information Server, so it's good enough for me.  Now i can switch hfs to use port 80 

That's some good results. 
Previously, I had suggested changing the http.sys service to ipv6-only (no listeners on ipv4 addresses) to clear ipv4 port 80. . . and still allow more modern microsoft things to use http.sys on ipv6.