Pi-Kvm not connecting

[Richard Fancher]

Has anyone gotten this client to connect to a Pi-Kvm? I also get something similar when I try and connect to a known working vnc server running on a piHole

Initializing VNC Session instance: 0

Connecting VNC Session in the background...

Ensuring buttons are initialized, and positioning them where they should be

VNC server supports protocol version 3.8 (viewer 3.8)

We have 2 security types to read

0) Received security type 19

Selecting security type 19 (0/2 in the list)

1) Received security type 2

Selected Security Scheme 19

OpenSSL version OpenSSL 1.1.1g  21 Apr 2020 initialized.

Got VeNCrypt version 0.2 from server.

We have 4 security types to read

0) Received security type 256

1) Received security type 259

Selecting security type 259 (1/4 in the list)

2) Received security type 2

3) Received security type 258

FAILED_TO_INIT_CONNECTION_TO_SERVER

Done initializing VNC session

Connection failure, showing error with title VNC_CONNECTION_FAILURE_TITLE.

Scheduling disconnect

Lazy disconnecting

wasDrawing(): true

Setting maintainConnection to false

Hiding keyboard.

[Richard Fancher]

This is what I get from the server.

[main] [::ffff:192.168.1.198]:57687: Error: Tight JPEG encoding is not supported by client: RfbClientEncodings(encodings=frozenset({0, 1, 2, -223, 5, 6, -314, 15, 16, -239, 21, 22, 24}), has_resize=True, has_rename=False, has_leds_state=False, has_ext_keys=False, has_tight=False, tight_jpeg_quality=0)

[Richard Fancher]

OK well....I think 3 days is an unacceptable amount of time with 0 response from the author on this.......so you can close.

[i iordanov]

Hi Richard,

Sorry I've had a crazy couple of weeks of work after the holiday.

So this basically says that the VNC Client does not support TightVNC encoding which it is supposed to support.

Could you please tell me is this happening on an iOS device or on Mac OS X? If it's Mac OS X, what architecture - x86_64 or arm64?

Thanks!

iordan

--
You received this message because you are subscribed to the Google Groups "bVNC, aRDP, aSPICE, Opaque Remote Desktop Clients" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bvnc-ardp-aspice-opaque-remot...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bvnc-ardp-aspice-opaque-remote-desktop-clients/08145c5d-faaa-4bff-b354-d8b0cdd99a32n%40googlegroups.com.

--

The conscious mind has only one thread of execution.

[Richard Fancher]

iOS, even tried on my android tablet. What's super annoying, that should be explained up front is, ios ONLY has a pro version whereas android has a demo and pro version. 

Not sure if this is even worth pursuing at this point but I'm willing to keep adding nessesary info. 

[i iordanov]

Hi Richard,

All veritable issues are worth pursuing. Let me try to reproduce this one.

So are you saying that the connection fails even on your Android tablet?

If so, I would caution against blaming bVNC and looking for a misconfigured server, because the implementation of the Android and iOS versions of the software is absolutely and completely different, relying on totally unrelated libraries implemented in different programming languages.

If it works on Android but fails on iOS, I'll need to set up something resembling the server you are connecting to. Could you please reply with a link to what it is you have set up? I am not familiar with Pi-Kvm.

Is it this project? https://pikvm.org/

Thanks,

Iordan

[Richard Fancher]

Yes, that is the project. It failed on both iOS and Android. Failed to also connect to an existing Pi-Hole using Raspian. I think it comes built with a vnc server.

I spoke with the author and he just said that it was a client problem.

TigerVNC on the PC connects to it with no issue

I am blaming bVNC because as an end user, all I see is that it doesn't connect to anything, this would be different if I was getting an invalid user/pass but it just does not connect on either client. Coupled with 0 documentation as to the restrictions of what server works with this client, I can only assume it's the client at fault.

From the author:

Can this run in a VM?

Yes

git clone https://github.com/pikvm/kvmd
make run  # one terminal
make run-vnc # second terminal

[Richard Fancher]

I am going to need to retract the statement that this does not work on Android, I just tried it again and it works so I will blame it on being a pebkac.

[Maxim Devaev]

Hi! I'm Pi-KVM developer. I'm very interested in solving this problem. Let's deal with this and make our users happy.

> So this basically says that the VNC Client does not support TightVNC encoding which it is supposed to support.

That's right. The server reported a list of encodings, but there is no encoding with code 7, which means Tight. It was based on this specification: https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#encodings

Also the client does not transmit the JPEG compression level:

https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#jpeg-quality-level-pseudo-encoding

But it seems optional and my server knows how to live without it.

четверг, 14 января 2021 г. в 20:48:18 UTC+3, Richard Fancher:

[i iordanov]

Hey,

That was quite a bit more work than I anticipated, but it's OK.

First of all, I needed gpio-mockup compiled as per the second answer (i.e. recompile the whole kernel):

https://stackoverflow.com/questions/60941225/compile-gpio-mockup-in-5-4

However, I am having no luck with the instructions for running pikvm in a VM.

git clone https://github.com/pikvm/kvmd
make run  # one terminal
make run-vnc # second terminal

1) This gave me errors with missing /dev/video0 device (I removed the lines that were mounting it).

2) then it gave me a different error:

mount: /sys/kernel/debug: cannot mount none read-only.

3) I removed the mount line, and maybe that broke things because the docker run command exits with exit code 1 now.

Any ideas?

iordan

To view this discussion on the web visit https://groups.google.com/d/msgid/bvnc-ardp-aspice-opaque-remote-desktop-clients/bc8dfd8b-e28b-42a2-a222-be14824d9364n%40googlegroups.com.

[Maxim Devaev]

Due to the complexities of emulation, you need a real video device to
run. Any Linux-supported USB webcam that you can throw into your
virtual machine will do. The video device is needed to simulate video
capture. Alas, v4l2-loopback works very poorly.

Replace mount & test lines to just one "true \". It should work.

пт, 15 янв. 2021 г. в 06:24, i iordanov <iior...@gmail.com>:

[i iordanov]

Is there no easier option for reproducing the bug than this?

Can I start by running the same VNC server that is used by the project somehow and see if that reproduces the issue?

Thanks!

iordan

[Maxim Devaev]

This VNC server software cannot work on its own and requires my
backend, which generates the image. In fact, a VNC server is just a
proxy from one protocol to another.

Checkout the bvnc branch from that kvmd repo. You still need gpio
mockup, but now it should work without video and debugfs. Username and
password is admin/admin.

пт, 15 янв. 2021 г. в 07:44, i iordanov <iior...@gmail.com>:

[i iordanov]

Hi Maxim,

Pretty brilliant - it now runs.

The results are in. It fails with Remmina from my Ubuntu 18.04 laptop and from iOS running bVNC the exact same way with:

kvmd.apps.vnc.server              INFO --- [entry] [::ffff:192.168.123.10]:49160: Connected client
kvmd.apps.vnc.rfb                 INFO --- [entry] [::ffff:192.168.123.10]:49160: Starting client tasks ...
kvmd.apps.vnc.rfb                 INFO --- [main] [::ffff:192.168.123.10]:49160: Using RFB version 3.8
kvmd.apps.vnc.rfb                 INFO --- [main] [::ffff:192.168.123.10]:49160: Using VeNCrypt security type
kvmd.apps.vnc.rfb                 INFO --- [main] [::ffff:192.168.123.10]:49160: Using VeNCrypt/TLSPlain auth type
kvmd.apps.vnc.rfb                ERROR --- [main] [::ffff:192.168.123.10]:49160: Error: [SSL: NO_SHARED_CIPHER] no shared cipher (_ssl.c:1123)
kvmd.apps.vnc.rfb                 INFO --- [kvmd] [::ffff:192.168.123.10]:49160: Cancelling subtask ...
kvmd.apps.vnc.rfb                 INFO --- [streamer] [::ffff:192.168.123.10]:49160: Cancelling subtask ...

It does work with xtigervncviewer and with Android running bVNC though, so it is definitely a libvncclient (part of libvncserver) library issue of some kind since it impacts both Remmina and iOS bVNC.

iordan

[i iordanov]

I created an issue to track this at

https://github.com/iiordanov/remote-desktop-clients/issues/245

[Richard Fancher]

Any update to this? 

You received this message because you are subscribed to a topic in the Google Groups "bVNC, aRDP, aSPICE, Opaque Remote Desktop Clients" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bvnc-ardp-aspice-opaque-remote-desktop-clients/e69thWMSE_k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bvnc-ardp-aspice-opaque-remot...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bvnc-ardp-aspice-opaque-remote-desktop-clients/CAMS0tn3ZfTUjizmHZag9ZZg7h1oXNUykcxv%3Dcfp9CG2tx01h9w%40mail.gmail.com.

[i iordanov]

Hi Richard,

I made a fix to Maxim's repository that fixes the issue for iOS and
avoids many other technical issues for Maxim's project.

For reference:
https://github.com/pikvm/kvmd/pull/28#issuecomment-777067207

Maxim and I will work toward getting this or something like it
introduced into pikvm.

Cheers!
iordan