Search results

Another option would be to upload the ISO's via sftp (assuming you are running ProxMox on Linux), this will keep your webinterface clean

Hi all, i have a (current) standalone node with ProxMox where in advance of getting it into production to test i copies some VMs from the current prod server. However for some unknown reason backup fails at 100%, and theres no real errorcode i can investigate/solve. Both VMs are stopped, so...

If something like this were to be implemented i would (under certain circumstances) appreciate it in the following form : - add an additional button next to the regular (single) delete that says 'Multiple delete' , when pressed make a checkbox line for each backup/file appear with a button on...

I guess you installed off the ProxMox iso , i myself installed from Debian Buster and then moved to Proxmox, so i set up local storage by hand (and in /etc/fstab :) To get back to the issue this seems like a timing thing, as i had similar issues with shared storage i solved it by adding a...

i would be interested to know if something like a gradual cluster would be possible ie. : - having 2 clusters at different geographical locations with a failover from cluster #1 to cluster #2 , in essence having a cluster of clusters... (also referenced by some software vendors as a Business...

Mentioning the word 'single' and or 'manual' anywhere in your question means you have an issue at that point. in short: having 1 host means if its down you are out of the game having a cluster with only local storage means you are still screwed when one node is down High-availabillity would...

i used to limit ssh connections with geolocation stuff .. but as that worked over tcpWrappers .. and ssh dropped that support its no longer viable .. but just for reference : https://www.axllent.org/docs/view/ssh-geoip/ Additionally as @dietmar mentioned ... it is unwise to 'just expose' ssh to...

why are you not using /etc/fstab to take care of this storage to be mounted ?

Hi all, It has been a while and we have gone thru a set of updates on the services. After running the updates i noticed that my (manual) additions to some unitfiles from PVE were overwritten. Especially the ones on the pve-guests.service where a line was added to let the startup of VM's be...

@Alwin i understand the statement, but : This position goes against the concept of what most companies have in regards of management from a single point. As administering in non-intergration means additional tasks for IT-administration departments ( even if the PVE...

@Alwin as PVE has a default LDAP capabillity i would even go for an enhancement of this. As the current only is aimed at authentication, via a mapping of the UID (or whatever attribute is selected) extending it to include a groupmembership which then lists its rights ... This way the need for...

Not as far as i know, only indication i have of jobs running is the view of the webUI ( i must confess i have not looked into it deeper) Also a thing i have not found ( if it is even built-in) .. if a job is interrupted a way to start/continue where it left off. i mean for example...

Just a question : in conjunction with DNS we also have DHCP, so what provides your workstation of an IP ? ... i do assume that your proxmox host ( and guests) have a fixed ip ?

Yes they will interrupt the backup process, and if you enabled reporting per mail it will list it as failed When you issue a : init 6 shutdown -h shutdown -r reboot it will stop the service that is running the backup as its being overruled from system itself and in the report (if emailing it...

One is an Appliance based on SLES - Microfocus Access Manager Appliance The other is/seems Debian Based (will be replaced in short future) - Microfocus Advanced Authentication 5.4

seems as if your container is started before the storage is available (seeing the 865 No such file or directory - Failed to receive the container state) Have you checked if all your storage is avaiable to PVE ?

In my setup i am running some appliances which refuse to shutdown when i issue a host reboot. As these are 'closed' appliances i am not able to install helpers like the Qemu-guest-agent to get around this. So the only solution is to open a console, and shutdown them from there ( else Proxmox...

i use a reverse proxy with authentication and authorisation (including 2FA) to expose the management UI to the public side. this way i control whats being exposed.

I dont see an error, just a piece of information ... on my dl360G7's i also see it when i update kernel ( the pve-efiboot-uuids - message) .. but never have i had any issues.

or setup a VM/LXC for puppet (or similar) and let that control your node's crontab 1 point of administration , and its all synched