Search results

@duke8804 it should work as is, please let me know if not.

@Tacioandrade thanks for testing!

Please on github @ tizbac repo.

We/I NEVER run this on Darwin but here you go: https://github.com/jochumdev/proxmoxbackupclient_go/releases/tag/v0.0.0-alpha3 A big issue now is that big backup's don't work yet (Like whole system) and another known issue is that we don't remember Filesystem permissions yet.

Do you have a Mac arround to test? Intel or ARM?

This is a great way to backup Windows Clients! https://github.com/tizbac/proxmoxbackupclient_go/issues/9

I'm available from time to time.

Try to do Download+Convert the dmg again. Join the Proxdroid Discord server for fast help https://discord.gg/JEuXW8h

Yes, that should be doable. You have to backup /etc/pve/qemu-server/* /etc/pve/lxc/* and /etc/pve/storage.cfg - the best is to backup /etc/pve/* Where do you have Proxmox installed on which disk? Is it in ZFS? Take care that the installer creates a "rpool" this name needs to be unique, so when...

I'm using NoMachine for that.

Doesn't work aSpice only likes arguments to the spice:// protocol and it doesn't include "proxy" in that.

@tim I look at the code atm. very Nice what you did with those Builders.

No it adds "pve01:443:8006", doesn't seem to work atm. What about this https://github.com/iiordanov/remote-desktop-clients/blob/master/aSPICE-app/src/main/AndroidManifest.xml#L64 hmm ok np!

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é

Ich arbeite gerade an einem neuem Client.

Why do you have to install a new VM when you use OVMF?

Those API Tokens documented at [0] are a dream, thanks for pointing me to it. [0]: https://pve.proxmox.com/pve-docs/pveum-plain.html

Now I also added a NGINX TCP LoadBalancer for Spice Port 3128 See [0] for the doku on how to that, see also [1] if you have troubles with it. 0: https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/ 1...

Today I moved my Proxmox behind an Kubernetes NGINX Ingress, I did that because I want a CORS, a Let's Encrypt Cert with a single Public IP and port 443. The Service YAML apiVersion: v1 kind: Service metadata: annotations: field.cattle.io/ipAddresses: '["10.167.160.10"]' name: pve01...

Look at this: https://forum.proxmox.com/threads/all-the-gfx-passthrough-infos-from-the-forum.76145/