Strangely enough, the service seems to be back up now (like it did the last time I posted an issue here 
), so this is no longer a blocker. I am still quite curious about what exactly caused the crash and subsequent IP collision errors though.
1 Like