Search results

Thank you. I understand your point, you just didn't understand the conditions sufficiently to comment. I don't know what to tell you to help you understand. I did not change how I referred to the hosts, I was always referring to the hosts by their correct full DNS name, not the short name. I...

@fabian I think you may have misread this thread or have otherwise understood the problem. The only time I reference the host by it's full DNS name was when I connected to it. The symlink/directory copy was merely a diagnostic step to see if it changed the outcome at all. It did not, and was...

@fabian - if you're referring to the symlink escapade, that had nothing to do with the underlying problem/was a misdirection. (And, if the short path name should be used, it's curious that there would be that error message in the logs while using it, yes?) The bug I was referring to was the...

This is probably a bug in how proxmox responds.

Sorry - yes, this error (certificate error) is a misdirection; it's not the underlying cause (or wasn't in my case). I ended up adding a Role and assigning these permissions. This fixed it for me.

Yeah, I'm aware of journalctl, and that's helpful when diagnosing service-level issues. I'm looking more for trying to get more advanced/detailed logs on API transactions. For instance, underneath /var/log/pve , there are records of all attempted modifications, presumably going back to the...

I'm trying to identify how I can get more detail on specific errors, eg. specifically as it relates to logging API calls. As near as I can tell, proxmox only logs to: syslog - for issues pertaining to things like credential problems, service restarts, various indication of cluster operations...

I also ran: pvecm updatecerts -f This, however, didn't help: the above error about remote node certificate verification stopped printing to logs, but requests still results in a 596 response.

Have you checked syslog for the associated/related failure is there? There should be some indication as to the underlying cause in that, or some other, log which could be used for correlation.

I created a `bastion.my.domain.net` directory and copied the pve-ssl.pem file into it. However, while the complaint about the pve-ssl.pem file not existing went away, the following log persisted (as does the HTTP 596 response code) - Dec 29 21:55:35 bastion pveproxy[3576]: Could not verify...

I'm running proxmox 6, fully up to date. (pve-manager/6.4-13/9f411e79 (running kernel: 5.4.157-1-pve) When trying to use the API to deploy VMs using terraform using an API key, I get this error from Terraform: │ Error: error creating LXC container: 596 tls_process_server_certificate...

I have now had this problem again, but I'm unsure how to produce it or provide diagnostic information - is there any way to file a bug officially with a core by non-paying customers? This is all 'professional' equipment (Dell 410s) which has been largely upgraded since the last time I had the...

It doesn't, unless I use a "sacrificial" VM using NFS storage, which I don't care about starting, and then make it so the others all delay 60s+ from that one. It's a really ugly fix, and doesn't work consistently. For what it matters, this issue is not tied to DNS - NFS is mounted via IP.

I've got a problem with proxmox 4.1 (which also existed on 3.3) where VMs try to start before the NFS filesystems have mounted, specifically on a host reboot. On 3.3, I worked around the issue by increasing the NFS server threads, but that appears to do nothing for 4.4. For instance, if I...

I had this problem when i was using bridged networking w/ an old crappy unmanaged switch. New VMs or restarted VMs had no network connectivity. Never figured it out precisely but haven't had the problem in months - i've since upgraded and replaced the switch.