Search results

Hi, thanks for reporting this! That's curious, especially given your curl command works just fine. Not sure what homepage is doing here specifically, but I'll try to reproduce this. Can you maybe also post some logs from homepage itself if you have those? If you opened an issue with homepage...

Hi, this should be fixed in PBS 4.0.12-1, hope that helps :)

You should remove the repo from the /etc/apt/sources.list and keep the one in the /etc/apt/sources.list.d/proxmox.source file. The problem with your screenshot is not quite clear to me. You should move the old ceph.list file once the new trixie repo has been activated.

Thanks, yes it does, seems that our regex here does not pick up on this way of naming libsystemd-shared, send a patch: https://lore.proxmox.com/pve-devel/20250806134843.266183-1-s.sterz@proxmox.com/T/#u For now, it should be safe to ignore this warning in this case specifically. Since, this...

Hi, what systemd version does the container use? And what does the command find / -name "libsystemd-shared-*.so" 2> /dev/null return in the container (ideally you could run that as root)?

Can you post the logs of that? The log above look like you can't log in at all: This for example indicates that pam could not authenticate you at all.

I think this is probably unrelated to the issue with pam here though. If I remember correctly, we have changed some dependencies there, but I am not too familiar with the TFA part of our authentication code. Regarding the authentication error - lines, the still occur on PBS 4.0.11 or 4.0.10 for...

Hey again, a couple of questions just to clarify: - You can't log in at all or do you get logged out again immediately after you initially logged in? - Do the log lines with authentication error - SUCCESS (0) still happen when you log in after the update? If so did you reboot the machine? -...

Ok so the somewhat confusing log message makes sense now and I send a patch for it here [1]. I'll look into what exactly is happening here, though. [1]: https://lore.proxmox.com/pbs-devel/20250805154820.324167-1-s.sterz@proxmox.com/T/#u

Thank you, can you try to log in via ssh and update to the latest version right now? Installing from the ISO, it seems that PAM has some problem logging in. Especially this part: authentication failure; rhost=[::ffff:10.10.10.1]:42160 user=root@pam msg=authentication error - SUCCESS (0)...

Proxmox VE does not install auditd by default. If you want to use it, you should install it via apt install auditd. The message you see come from some other part of the kernel using a related mechanism to limit the amount of log messages. By default, the Linux kernel is configured so that the...

Depends, both are not stable releases at this point, so there aren't many guarantees about what will and will not work. That being said, in general the Proxmox VE API is fairly stable and there this should work at least in theory. Please note though, that you should use neither in production at...

Danke für die Infos, was sagt denn der Befehl df -h /var/tmp?

Wenn warten eine Option in dem Fall ist, dann ja. Am besten auf der Node mal journalctl -f ausführen während der Upload läuft und dann den Output hier posten. Bitte gerne!

ZFS over iSCSI hilft leider in dem Fall nicht viel, wenn Synology selbst nicht das ZFS anbietet. Leider ist die Benennung hier etwas verwirrend, aber ZFS over iSCSI bedeutet, dass auf einem Host ZFS Volumen via iSCSI an ein PVE Cluster zur Verfügung gestellt werden. Nicht, dass auf einer iSCSI...

Well I think the problem would be that we don't have many French-speakers on staff, so it'd be hard to moderate a French-language forum for us. But this is just my two cents.

Glad to hear that. You could try to debug this further, but to be honest, this is somewhat expected. You can mark this thread as “solved” by clicking the “Edit Thread” button on top and selecting the “Solved” prefix. This helps other user with the same problem find a solution. Thanks!

So I looked into the “CPU Flags” you mention here are “Hyper-V Enlightenments” (hv_spinlocks, hv_reset) [1]. Can you try simply adding this line to your config: args: -cpu...

I think you are just misunderstanding the format here. The documentation [1] here mentions that each flag you want to specify, needs to be prefixed by either a “+” or a “-”. If you prefix the flag with a “+” it will be enabled. If the flag is otherwise enabled, prefixing it with “-” would...

Yes that makes sense, I'm assuming this fixes the issue for you? If so, please mark this thread as solved by adding the “Solved” prefix via the “Edit Thread” menu above. Thanks!