Re: Unable to connect to Proxmox. Failed to authenticate to Proxmox Virtual ENvironment. Please make sure you enter your username in user@realm format and

[i iordanov]

Hello,

Yes, it is expected to work and I would be very grateful if I get more information to help fix any issue. Reimbursement is not a problem at all. You are required to enter the user as user@realm as you have done.

Please attempt a connection and send me a (private) email with the adb logcat captured *after* the attempt at iiordanov at gmail dot com.

The adb logcat can be obtained from the menu on the main screen (Menu -> Copy Logcat).

Thanks!

iordan

On Wed, Jun 5, 2019 at 4:24 PM <rkkos...@gmail.com> wrote:

Hi, I just purchased Opaque in the hope to be able to connect to my VMs in Proxmox via Spice. 

But after entering the IP, username and password, when I try to connect it shows this exception:

"Failed to authenticate to Proxmox Virtual ENvironment. Please make sure you enter your username in user@realm format and that you password is correct"

I tried to set the username with the format:

user

as also as

user@pam

So now I'm out of ideas, is this app working or not? And if not how to reimburse?

--
You received this message because you are subscribed to the Google Groups "bVNC, aRDP, aSPICE, Opaque Android and BB10 Remote Desktop Clients" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bvnc-ardp-aspice-opaque-andr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bvnc-ardp-aspice-opaque-android-bb10-clients/3b64a2e0-a825-4616-bce5-1ca9af1d29f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

The conscious mind has only one thread of execution.

[n0bilis]

Had the same problem (I guess).

Took me hours to figure out the rootcause:

My pve does not run on IPv6 (only on IPv4), but for some reason my Adroid device had both (IPv4 & IPv6) addresss on the wifi-nic. It looks like the app is trying to use v6 at least at some parts if it is availeble on the client.

When I activate my VPN it has only an IPv4 and the app works fine.

I hope that helps to get rid of that problem or at least to work around it.

[iior...@gmail.com]

So you were using a hostname to connect, and because DNS AAAA (v6) records work at your location, the app was trying to connect to a ipv6 address?

If you just use an ipv4 address it would work, wouldn't it?

It doesn't seem right for Opaque to work-around such an issue - does it make sense to ask Proxmox why they don't listen on ipv6?

Thanks!

iordan

[n0bilis]

I'm using a DNS-recorded hostname solved by a local-dnsserver to a v4 IP-adress.

The app is connecting to the pve, I'm able to log me in and select the designated VM but the connection brokes directly after that selection.

When I use the ipv4 adress directly the behavior is the same.

My pve would be able to listen to v6 adresses, but my whole local network infrasturctur (DNS-server etc) is v4 based and not migrated to v6 so far. Therefor I've disabled it on every machine where it's possible.

I'm able to connect to the vm from debian via v4 using spice without the VPN workaround right out of the box. I'm there also using the DNS-name of the pve.

I hope that give you some helpfull information. Please feel free to contact me if there is something else you need or what I should test. Could me tanke some days for me to response but I'll do my best.

Thank you for your invested time so far.

BR nobilis

[i iordanov]

Hey,

Not a problem, I'm trying to understand the issue and what the root cause is.

So if you are able to select a VM, that means that the app has no
trouble connectin to PVE's API. The issue happens at a later stage
when it passes the console.vv file to the spice library and the spice
library tries to connect to an address that resolves to an ipv6 IP.

So based on your description, there is a setting somewhere in PVE (IDK
if it's exposed to users) that allows you to set the address of the
actual host that runs the VMs. That address is a name that resolves to
both ipv4 and ipv6 addresses, but the VMs themselves are not listening
on ipv6, just on ipv4.

I found a whole discussion on how to properly disable ipv6 server-side:
https://forum.proxmox.com/threads/proxmox-v7-1-disable-ipv6.101681/

I don't think the client is to blame for this configuration strangeness.

Thanks!
iordan

On Wed, Apr 6, 2022 at 8:30 AM 'n0bilis' via bVNC, aRDP, aSPICE,
Opaque Remote Desktop Clients
<bvnc-ardp-aspice-opaque...@googlegroups.com>
wrote:

> 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/8506de93-d86f-49ca-b124-9435cbcb0a9an%40googlegroups.com.

[n0bilis]

Hi,

I've disabled v6 on pve like discribed in the system documentation: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_disabling_ipv6_on_the_node

When I loog me in to pve via a browser and download the vv-file manualy and look into it with a text editor I can opserve the following:

- When I use the hostname the this will be used in the "proxy" line in the vv-file

- When I access the webside via ip that this will be used as "proxy" information in the vv-file

No matter what file I use and open it with the app the behavior is like described above (expact that there is no VM selection needed). This is also the case then I do it via VPN.

When I open the spice connection via the proxmox android app over the opaque app it bahaves like the direct connection in opaque.

When I copy the vv file that I've downloaded via the android browser over to my linux machine and open it with remote-viewer it runs right out of the box (like it should).

To me it looks like the problem is related to android or the app itself. ATM I've no idea how to test what of these two is the problem.