Install on Windows Server 2019

[qholmberg]

We are migrating our Lansweeper instance to a new server. When we walk through the install, it tells us that something is running on port 80. However, running a netstat -anb does not reveal anything running on port 80.

The installer takes port 443 without any issue.

This is a brand new install of Windows 2019. Nothing else is installed on the machine nor has it been granted any additional roles. IIS is not installed either. It is a VM in an ESXi 6.7 server, if that is important. The Windows firewall is disabled. No antivirus has yet been installed.

Does this sound familiar to anyone? Is there, maybe, something with 2019 that confuses the installer? Any hints at finding out what is going on?

Yes, I could just take port 81 but, I guess, I'm just too anal for that. I'm dedicating a server to this now and I just want it to run on the standard HTTP port.

TIA

-- Quintin

[BarefootGreg]

Did this ever get resolved? We are having the same issue.

[Rufinobr]

qholmberg wrote:
We are migrating our Lansweeper instance to a new server. When we walk through the install, it tells us that something is running on port 80. However, running a netstat -anb does not reveal anything running on port 80.

The installer takes port 443 without any issue.

This is a brand new install of Windows 2019. Nothing else is installed on the machine nor has it been granted any additional roles. IIS is not installed either. It is a VM in an ESXi 6.7 server, if that is important. The Windows firewall is disabled. No antivirus has yet been installed.

Does this sound familiar to anyone? Is there, maybe, something with 2019 that confuses the installer? Any hints at finding out what is going on?

Yes, I could just take port 81 but, I guess, I'm just too anal for that. I'm dedicating a server to this now and I just want it to run on the standard HTTP port.

TIA

-- Quintin

2020 and same here! Just installed a fresh new 2k19 server with ISS, changed default port but LS tells someone is using port 80.

[AZHockeyNut]

so the only thing I can think of is Reporting services in SQL. I have seen that often take up port 80 if installed before anything goes to IIS. Even IIS express can do it when it monopolizes the WKP rather than full blown IIS, depends on how you set up the rest of the system and in what order. Not sure that is it or helps. Thought I would share in case it does.

If it is SQL SSRS, go into Reporting services configuration, and change the bindings, then you will get IIS back to having port 80. SSRS does not bind 443 out of the gate, which is what made me think you ran into something I have seen before.

[Esben_D]

Just did a quick test on my own W10 machine and I get the same popup. I'm not quite sure what could be blocking it but let me know if you find out.


You can try and use netsh http show urlacl to check the port reservations.

I did try some of the suggestions in these links to find things using port 80.

https://blogs.msdn.microsoft.com/rohithrajan/2017/08/27/how-to-fix-the-error-port-is-currently-used-by-another-application/
https://www.howtosolutions.net/2015/04/solving-apache-port-80-is-already-used-error-on-windows/

Lastly, you can also just install it to port 81 and change it to port 80 after the install.
Since I do so many installs I always just pick whatever it suggests