No browser opens by default and can't reach slides when manually navigating to Suave server's address

[OmanF]

Metadata:

• OS: Linux Debian Sid
• Mono version: 6.8.0.80

Issue:
When running build.sh (I had to also use the workaround stated in #116, maybe that is the reason for my issue) no browser opens by default and goes to the slideshow.

Furthermore, manually opening the browser (any, I've got Firefox, Chromium and Google Chrome) and navigating to either localhost:8083 or 127.0.0.1:8083 gets a response that, (on Firefox) the connection was reset, (on Chrom* family) the localhost server didn't send any data.

Clicking any key to end the presentation than throws an error:

1) System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'FileSystemWatcher'.
  at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x00013] in <5ddccb0244894a3db95fe3ed17856fcc>:0 
  at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher.set_EnableRaisingEvents(bool)
  at Fake.ChangeWatcher+WatchChangesWithOptions@113-6.System-IDisposable-Dispose () [0x00021] in <574c61baccf1c534a7450383ba614c57>:0 
  at FSI_0005.Build+clo@132-5.Invoke (Microsoft.FSharp.Core.Unit _arg2) [0x00082] in <4423ec592ffc4fa682eb02d63f9d6136>:0 
  at Fake.TargetHelper.runSingleTarget (Fake.TargetHelper+TargetTemplate`1[a] target) [0x00040] in <574c61baccf1c534a7450383ba614c57>:0 

[OmanF]

I just tried on a Windows machine as well.

Some more metadata: Both Linux and Windows machines are running .Net Core 3.0 release version (the Linux machine also has Mono as stated in the original issue).

1. I had to use the workaround in Unable to start on mono Docker #116 on the Windows machine as well!
2. The same behavior, i.e. no default browser nor is the slideshow reachable manually on either localhost:8083 or 127.0.0.1:8083
3. Unlike the Linux machine, when clicking any key to terminate the show, didn't get any errors. The slideshow terminated with an all green build!

The fact that I had to use the workaround from #116 on both Linux and Windows machine, producing the same (faulty) result on both makes me suspect that this workaround is the reason for this behavior, but, without using the workaround the build crashes immediately with the error message listed on the other ticket, so can't use FsReveal either way.

Also note, on a third machine I have at work, running Windows with .Net Core 3.0 everything worked out of the box and still works correctly.
The only difference I can think of is that the work machine is Windows 10 Enterprise version 1903 and my local machine is Windows 10 Pro version 1909.
(I don't have Linux at work at all).