Search results

  1. O

    [SOLVED] Proxmox VE Helper-Scripts - Not Updateable

    Vielleicht "schläft" der benutzte Mirror noch oder Dein DNS der VM geht ins Leere, denn
  2. O

    [SOLVED] Proxmox VE Helper-Scripts - Not Updateable

    Ich habe von dort Home Assistant seit gut einem Jahr laufen und das lässt sich ganz normal updaten. Für mich sieht das eher so aus, dass Ubuntu ggf. an den URLs geschraubt hat... Guck mal hier, ob Dir das weiterhilft.
  3. O

    Proxmox Backup Server 3.3 released!

    The now stable "change detection modes" are hell fast! After changing that setting from "none" to "metadata", the first next backups took two up to three time more as usual, but all following backups were done in half the time as in the past, if not much lower than in half the time. Stunning!
  4. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    Humm, you're right, but then the corresponding entry is missing in post #7. We'll see what his upgrading procedure will bring on.
  5. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    I'm not saying you were wrong with post #11, but I can't see any plan or source that the OP is using/tries to use the official PBS client repository - yet.
  6. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    Not really correct. Proxmox itself is providing a client for x86-64 only, but there are some working and well maintained packages for aarch64, namely ArchLinux/aarch64 or self baked
  7. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    "bookworm", not "bookwork". The latter won't run any update :) Will this fix the issue? It should, as long there aren't already any messed up dependencies between the 3rd party sources and/or Debian. To be sure take your SD card before update, insert it into a handsome and friendly OS and create...
  8. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    You are having a mixup of "bullseye" (Debian 11) and "bookworm" (Debian 12), at least for tailscale. This may work but isn't recommended at all. Also have a look at docker.list where the wrong armhf is shown. And better to post text output as "code" than as a not searchable picture ;)
  9. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    For the 1st step please post the content of your /etc/apt/sources.list and, if applicable, the content(s) of all files under /etc/apt/sources.list.d/ These are the sources where the OS will download all packages from.
  10. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    Oi, but your snippet above is showing "...doesn't support architectue 'armhf' "!? Looks like that you have a wrong setting in one of your sources under /etc/apt/
  11. O

    [SOLVED] Proxmox-Backup-Client not working on RaspberryPi

    Proxmox-Backup-Client is only available (and working) for aarch64 but NOT for 32 bit Distros (armhf).
  12. O

    Smart(d) Script zum Festplattencheck und Resultat per Mailverschicken

    Nein. Der erste Block/Zeile wäre für "normale" Festplatte(n)/SSD(s), der zweite Block ist stellvertretend für meinen MegaRAID/SAS-Controller. Sind beides also nur Beispiele. Im Zweifel mit den smartmontools einfach herumspielen und/oder manpage lesen, passieren kann da nix.
  13. O

    Smart(d) Script zum Festplattencheck und Resultat per Mailverschicken

    Ich habe es ganz simpel laufen: Ein MTA (postfix) auf dem PVE, der jedweden Bla an mich sendet und in /etc/smartd.conf (smartmontools) die Zeile DEVICESCAN -d removable -n standby -m mich@example.org -M exec /usr/share/smartmontools/smartd-runner bzw. /dev/sda -d megaraid,0 -a -m...
  14. O

    LXC and tvheadend - Continuity counter error

    Yeah, thanks, already seen this thread (I think), but not tested as this seems to be not a Fix to me but a Crutch ;)
  15. O

    LXC and tvheadend - Continuity counter error

    Thread starter here... At least for my situation, unfortunately no. I've re-tried this a few months ago but still failed. Never tried again w/ PVE 8 because I'm using a dedicated small NUC-like box for tvheadend and never had any issue since then.
  16. O

    PVE 8.0 – fail2ban log locations missing?

    Great to hear that it's working, thanks for confirmation. I'm relatively sure that the port line can be removed, but I kept it for now for safety reasons. This line is a takeover from Bullseye. My backend is "auto" and looks like to work. Can't remember if that was the default or not.
  17. O

    PVE 8.0 – fail2ban log locations missing?

    @MinishMan Glad I could give at least some help. What about this jail and filter? (fresh and so not yet intensively tested) /etc/fail2ban/jail.d/proxmox.conf [proxmox] enabled = true port = https,http,8006 filter = proxmox maxretry = 3 bantime = 3600 findtime = 300...
  18. O

    PVE 8.0 – fail2ban log locations missing?

    Correct. Keep in mind that these are my general values and only exemplary, but a somewhat good starting point. And you can take them over and adjust them in your jails for your own sake.
  19. O

    PVE 8.0 – fail2ban log locations missing?

    I had the same issue but solved it by investigating some 'lil time with ArchLinux' wiki as mentioned in #3 and created a file named /etc/fail2ban/jail.local with the exemplary content of [DEFAULT] ignoreip = 127.0.0.1/8 ::1 AND OTHER IP ADDRESSES backend = systemd bantime = 3600 findtime =...