Yeah, someone just made a post about that recently. This solved the issue, and now I’ve my Mollysocket server running! Many thanks to you for assisting.

I guess I managed to break too many things while testing several settings…so I did a fresh Linux Mint installation and decided to try Crates option again almost succeeding…

Now I managed to perform cargo install mollysocket as well as create vapid key (though only as a plaintext…) and add that to corresponding file. I set up Mollysocket to be used in air-gapped mode (webserver = false), then performing systemctl restart mollysocket, and now based on systemctl status mollysocket the process is now active. I also got the QR code via journalctl -u mollysocket, but now the status on the Molly app says it’s “Unable to create the linked device”.

That’s where I’m stuck now. Seems to be so close to work…

1. Using Crates.io:

cargo install mollysocket

ends up with

error[E0658]: c"…" literals are experimental … error: could not compile rusqlite (lib) due to previous error.

Now rustc --explain E0658 states that this is due to unstable feature “repr128”. I’m using a nightly version.

2. Using precompiled release:

After systemctl enable --now mollysocket

performing systemctl status mollysocket gives

… Active: failed (Result: exit-code) … Process: … (code=exited, status=203/EXEC) …

3. Docker:

sudo -u mollysocket mollysocket vapid gen | systemd-creds encrypt --name=ms_vapid -p - -

or basically any command starting mollysocket ends up with

mollysocket:command not found error.

I’m currently running Linux Mint (though I’m okay and/or planning to change the distro once I succeed with this setup for the first time).