aSpice Don't Work

4 views
Skip to first unread message

José R. Lara

unread,
Nov 29, 2025, 3:38:03 PM (3 days ago) Nov 29
to bVNC, aRDP, aSPICE, Opaque Remote Desktop Clients
I try to open .vv file and the connection is not working.

this is the log generate the connection:

Initializing Remote Session instance: 0
Device reports screen resolution 1330.0x998.0
Ensuring buttons are initialized, and positioning them where they should be
initAndShowOrHideKeyboardButtonDueToExternalKeyboard() Creating keyboard button
startSpiceSessionOnBackgroundThread(): Connecting SPICE session with console file /Users/jlaratomas/Library/Containers/com.iiordanov.aSPICE/Data/Documents/console.vv
initializeKeyboardButtonIfNotInitialized() Keyboard button already initialized
showOrHideKeyboardButtonDueToExternalKeyboard() Checking GCKeyboard.coalesced: Optional(<GCKeyboard 0x8ff823ac0>)
showOrHideKeyboardButtonDueToExternalKeyboard() Hiding keyboard button because external keyboard was found
setVisibilityOfOnScreenButtonsIfDrawing hidden: true
GStreamer successfully initialized
Done initializing SPICE session from file

Starting SpiceGlibGlue_ConnectWithVv
../src/channel-main.c:342:spice_main_set_property: SpiceMainChannel::color-depth has been deprecated. Property is ignored
GSocketClient: Starting new address enumeration
GSocketClient: Address enumeration succeeded
GSocketClient: Starting TCP connection attempt
setUpFirstResponderDepedingOnOS() Running on MacOS, keyboardButton resigning first responder
GSocketClient: Connection attempt failed: Connection refused
GSocketClient: Starting new address enumeration
GSocketClient: Address enumeration completed (out of addresses)
GSocketClient: Address enumeration failed: (null)
GSocketClient: Connection failed: Could not connect to proxy server 169.197.143.221: Connection refused
main channel: failed to connect
Will show error dialog with title: SPICE_SESSION_DISCONNECTED
Lazy disconnecting
Will show error dialog with title: SPICE_SESSION_DISCONNECTED
Lazy disconnecting
Connection failure, showing error with title SPICE_SESSION_DISCONNECTED.
(glue-connection.c:67):spice_connection_dispose: runtime check failed: (conn->channels > 0)
Scheduling disconnect
Lazy disconnecting
Connection failure, showing error with title SPICE_SESSION_DISCONNECTED.
disconnect(sender:) called
disconnect() called
Scheduling disconnect
Lazy disconnecting
Hiding keyboard.
disconnect(sender:) called
disconnect() called
Hiding keyboard.

If I try using Virt-Client on windows works ok

i iordanov

unread,
Nov 29, 2025, 3:43:50 PM (3 days ago) Nov 29
to José R. Lara, bVNC, aRDP, aSPICE, Opaque Remote Desktop Clients
Hi Jose,

The log file says that your MacOS cannot reach 169.197.143.221. This looks like a public IP, so I assume you have some block/allow list in your cloud configuration?

Is it possible this is a Network-Level configuration difference between your windows and Mac network environments?

Thanks!

The conscious mind has only one thread of execution.

--
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 visit https://groups.google.com/d/msgid/bvnc-ardp-aspice-opaque-remote-desktop-clients/acda934a-73a5-4f44-8227-b7ac07faa4a7n%40googlegroups.com.

José R. Lara

unread,
Nov 29, 2025, 5:58:18 PM (3 days ago) Nov 29
to bVNC, aRDP, aSPICE, Opaque Remote Desktop Clients
I make some tests, the error appear when I try to connect to a VM hosted on old Proxmox Server 7, when I try to connect to a Vm hosted on Proxmox 8  works great.

i iordanov

unread,
Nov 29, 2025, 6:01:11 PM (3 days ago) Nov 29
to José R. Lara, bVNC, aRDP, aSPICE, Opaque Remote Desktop Clients
Hi Jose,

That's great feedback - I don't believe I ever tested this app with a Proxmox version this old. Potentially I may have had a 7.4 server at the very outset but If I remember correctly, I upgraded it to 8.x soon after I started development.

Unfortunately, I don't think I have the means to fix issues with a Proxmox this old.

Thanks again!
iordan



--
Reply all
Reply to author
Forward
0 new messages