Andri Yngvason

Well, traffic on localhost:7900 won't be encrypted, but I'm off to bed anyhow. Thanks for testing!

Ahh, could it be that it just wants an older version of the RFB protocol? Edit: That could very well be the case. See: https://github.com/any1/neatvnc/issues/48

I'm rather apprehensive about fail2ban. I wouldn't trust it myself. The problem here seems to be that `Screen Sharing.app` wants an older protocol version that Neat VNC doesn't support.

> I use Apache Guacamole to access some devices exclusively using an OpenVPN tunnel and, at the moment, I can't use devices installed with raspbian+wayvnc . You can turn off...

> @any1 Just so I'm clear, does not fixing this imply that Apple's Screen Sharing won't work with wayvnc unless Apple changes something? Or did I miss a configuration setting...

The utility of a trace log is not contingent upon whether it's a crash or not. Anyhow, the captured output needs to be enabled for capturing to work because nothing...

Power management will now be turned on only while a user is connected. That should take care of this problem.

What happens if stop the wayvnc service and run it from terminal instead, attaching directly to the headless session? A trace log might be useful.

Did you maybe run it in detached mode (`-D` or `--detached`)? That would give you a grey screen until it's attached using the `wayvncctl attach` command.

If you run `journalctl --unit=wayvnc`, you'll see the output from the wayvnc service. If you have one wayland instance running, it should be located at "wayland-1". It might also be...