New Mobile App for Proxmox VE!

martin

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,742
223
We have just released the new Proxmox Virtual Environment mobile app, designed for use on Android devices (smartphones and tablets). The app allows you to log in to your Proxmox VE server from your phone or tablet and manage virtual machines, containers, hosts, and clusters on the go. It is based on the cutting edge Flutter framework, which enables us to provide a sleek interface, in addition to a blazing fast experience.

The Proxmox VE mobile client is meant as a helpful companion for administrators.

Key Features
  • Overview dashboard of the Proxmox VE cluster or node, including status and resource usage
  • Login manager to connect to different Proxmox clusters or nodes
  • Search and filter functionality for guests, storage, and nodes
  • Overview of users, API tokens, groups, roles and domains
  • Control VM/container power state (Start, Stop, Reboot, etc.)
  • RRD diagrams for nodes and guests
  • Migration of guests (online or offline) between cluster nodes
  • Back up data to different storages, including Proxmox Backup Server
  • Storage view to search and access content
  • Task history and current task overview
  • and more...
You can download the Proxmox Virtual Environment app from the Google Play Store

https://play.google.com/store/apps/details?id=com.proxmox.app.pve_flutter_frontend
__________________
Best regards,

Martin Maurer
 
  • Like
Reactions: cave, Fathi, tchucho and 44 others
r.jochum said:
Feedback:

Very nice design! Great work.

Suggestions:
- allow port 443 Remotes for proxied Proxmox Servers (Type https://pve01....:443 should work).
- I have "aSpice pro" installed but it doesn't like it (No Spice Client Installed).
- No way to go back from Sites

Thank you,

René
Click to expand...
- using a custom port should work, just add the port to your ip/hostname e.g. hostname:1234

- aSpice does not support the virt-viewer mime type, because the developer decided that this is only supported via the paid version of his app (Opaque)
- the sites screen displays your active sessions, if you want to go "back" click the session you want to go back

thanks for your nice feedback about the design!
 
  • Like
Reactions: World Tech
tim said:
- using a custom port should work, just add the port to your ip/hostname e.g. hostname:443
Click to expand...

No it adds "pve01:443:8006", doesn't seem to work atm.

tim said:
- aSpice does not support the virt-viewer mime type, because the developer decided that this is only supported via the paid version of his app (Opaque)
Click to expand...

What about this https://github.com/iiordanov/remote...r/aSPICE-app/src/main/AndroidManifest.xml#L64

tim said:
- the sites screen displays your active sessions, if you want to go "back" click the session you want to go back
Click to expand...

hmm ok

tim said:
thanks for your nice feedback about the design!
Click to expand...

np!
 
  • Like
Reactions: World Tech
  • Like
Reactions: Altrove and World Tech
Nice APP!

How to enable this for Users (not root). Are there any Roles a User needs to access the Environment ?

Eg.
gave permission to User - "PVEVMUser" for a specific VM
can access the Environment (via Browser 10.20.30.40:8006) and only sees the VM
But cannot access the App, error: '403: Permission check failed (\, Sys.Audit)'
 
Last edited:
  • Like
Reactions: Altrove and World Tech
Ronny Aasen said:
Does not connect. just shows:
"API Error"
401: no ticket.
Tried with both PVE and PAM user.



EDIT:
It seems that it works on a proxmox node that have an legacy ip address as well as an ipv6 address. (dual stack)
allmost all of our proxmox servers are ipv6 only.
Click to expand...
Please post the output of "pveversion -v" from a host you can't connect to
 
  • Like
Reactions: World Tech
Looking at the status of running VMs with the app works fine, but with containers I get errors:
Deserializing '[xyz, (various other strings), ...' to 'PveNodesLxcStatusModel' failed due to: Deserializing '1' to 'num' failed due to: '_OneByteString' is not a subtype of type 'num' in type cast.
where xyz is vmid or cpus or template or disk or ... My Proxmox VE 6.2-11 machine and the app are without any updates pending.
arch: amd64 console: 0 cpulimit: 1 cpuunits: 256 hostname: email10 memory: 192 net0: name=eth0,bridge=vmbr3,firewall=1,gw=172.17.3.1,hwaddr=52:54:56:17:03:10,ip=172.17.3.10/24,type=veth onboot: 1 ostype: debian protection: 1 rootfs: local-zfs:subvol-110-disk-0,mountoptions=noatime,size=3G swap: 24 unprivileged: 1
 
  • Like
Reactions: World Tech
avw said:
Looking at the status of running VMs with the app works fine, but with containers I get errors:
Deserializing '[xyz, (various other strings), ...' to 'PveNodesLxcStatusModel' failed due to: Deserializing '1' to 'num' failed due to: '_OneByteString' is not a subtype of type 'num' in type cast.
where xyz is vmid or cpus or template or disk or ... My Proxmox VE 6.2-11 machine and the app are without any updates pending.
arch: amd64 console: 0 cpulimit: 1 cpuunits: 256 hostname: email10 memory: 192 net0: name=eth0,bridge=vmbr3,firewall=1,gw=172.17.3.1,hwaddr=52:54:56:17:03:10,ip=172.17.3.10/24,type=veth onboot: 1 ostype: debian protection: 1 rootfs: local-zfs:subvol-110-disk-0,mountoptions=noatime,size=3G swap: 24 unprivileged: 1
Click to expand...
This is caused by cpulimit which should return as num, but is returned as String from the API.
WIll be fixed in the next app update, thanks for reporting.
 
  • Like
Reactions: World Tech and leesteken
Is it possible to add SSL client certificate auth ?
I'm using nginx proxy, with Chrome it can ask for client certificate installed on the phone.
 
could certainly be too old version proxmox. (5.4-2)

tim said:
Please post the output of "pveversion -v" from a host you can't connect to
Click to expand...

# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-25-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-16
pve-kernel-4.15.18-27-pve: 4.15.18-55
pve-kernel-4.15.18-25-pve: 4.15.18-53
pve-kernel-4.15.18-24-pve: 4.15.18-52
pve-kernel-4.15.18-18-pve: 4.15.18-44
ceph: 12.2.13-pve1~bpo9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
root@node-a:~#
 
Ronny Aasen said:
could certainly be too old version proxmox. (5.4-2)



# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-25-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-16
pve-kernel-4.15.18-27-pve: 4.15.18-55
pve-kernel-4.15.18-25-pve: 4.15.18-53
pve-kernel-4.15.18-24-pve: 4.15.18-52
pve-kernel-4.15.18-18-pve: 4.15.18-44
ceph: 12.2.13-pve1~bpo9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
root@node-a:~#
Click to expand...
Sorry but PVE 5 isn't supported anymore, but with the next update you will get this info right in the app on login when you try to connect to a host which doesn't has the required PVE version.

Updating your hosts to a recent 6.2-x version should fix the issue.
 
tim said:
Sorry but PVE 5 isn't supported anymore, but with the next update you will get this info right in the app on login when you try to connect to a host which doesn't has the required PVE version.

Updating your hosts to a recent 6.2-x version should fix the issue.
Click to expand...

awesome thank you, upgrading is on the roadmap
 
  • Like
Reactions: tim
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom