Foris-controller won't fully start when something is running on port 5353
After a load of debugging with one user it turns out that foris-controller started using port 5353 (mdns). Is this port essential? At the moment at minimum foris-controller gets stuck if there is something already binded on that port and that is major issue at minimum. It should pass that error or if it is critical it should fail not get stuck.