Weird interaction with Mullvard VPN

[pedrolabonia]

Hey,

Following a standard PC reboot, I encountered errors indicating a node crash. The logs revealed a permission denial error at port 11922:

[2024-01-05 07:20:40.881] [info]  dbPath C:\Users\xxx\AppData\Roaming\Memex Desktop_
[2024-01-05 07:20:40.885] [info]  Read/Write access is available for the database file**
[2024-01-05 07:20:41.548] [error] There was an uncaught error Error: listen EACCES: permission denied 0.0.0.0:11922
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at Server.listen (node:net:1953:7)
    at Function.listen (C:\Users\xxx\AppData\Local\Programs\memex-desktop\resources\app\node_modules\express\lib\application.js:635:24)
    at startExpress (file:///C:/Users/xxx/AppData/Local/Programs/memex-desktop/resources/app/build/index.js:171:29)
    at file:///C:/Users/xxx/AppData/Local/Programs/memex-desktop/resources/app/build/index.js:354:21
    at step (file:///C:/Users/xxx/AppData/Local/Programs/memex-desktop/resources/app/build/index.js:32:23)
    at Object.next (file:///C:/Users/xxx/AppData/Local/Programs/memex-desktop/resources/app/build/index.js:13:53)
    at fulfilled (file:///C:/Users/xxx/AppData/Local/Programs/memex-desktop/resources/app/build/index.js:4:58)

I thought at first maybe it was something about running it in sudo mode in windows, but it wasn't. I decided to just for good measure disable it, and then it worked flawlessly.

It might have something to do with the way Mullvard captures the local traffic(you do have to enable local traffic, but mine was enabled anyway before).

Probably a freaky thing with my setup.

It might be helpful to mention this in the docs. 🙂