I tried multiple ports even though port 80 is free for use but always the same.


It looks like the port you’re trying to use is already in use, either by another application or because the server was started twice.DeanCTS wrote: Wed Oct 28, 2026 1:48 pm Hello, I am getting the error as seen on screenshot when trying to run this app.
I tried multiple ports even though port 80 is free for use but always the same.
![]()
I see clearly now, could have made a bit clearer error text then man. Can't wait to give this a try in our office!Wagnard wrote: Wed Oct 28, 2026 2:06 pmIt looks like the port you’re trying to use is already in use, either by another application or because the server was started twice.DeanCTS wrote: Wed Oct 28, 2026 1:48 pm Hello, I am getting the error as seen on screenshot when trying to run this app.
I tried multiple ports even though port 80 is free for use but always the same.
![]()
Note that it’s not port 80 here, it’s the TFTP UDP bind (port 69) that fails. If you have WDS installed (common on MDT deployment servers), it holds UDP 69, so you’d need to stop/disable the WDSServer service.
Yeah possibly, the error is mostly from the .NET code itself, it was not manually written. But I could.DeanCTS wrote: Wed Oct 28, 2026 2:26 pmI see clearly now, could have made a bit clearer error text then man. Can't wait to give this a try in our office!Wagnard wrote: Wed Oct 28, 2026 2:06 pmIt looks like the port you’re trying to use is already in use, either by another application or because the server was started twice.DeanCTS wrote: Wed Oct 28, 2026 1:48 pm Hello, I am getting the error as seen on screenshot when trying to run this app.
I tried multiple ports even though port 80 is free for use but always the same.
![]()
Note that it’s not port 80 here, it’s the TFTP UDP bind (port 69) that fails. If you have WDS installed (common on MDT deployment servers), it holds UDP 69, so you’d need to stop/disable the WDSServer service.
![]()
![]()
![]()