Search results

Hi, Proxmox sends alert emails by default to root, for things like smartctl warnings (disk failures), and HA failover etc. Is it possible to setup a CC list for these alerts, so that it can email multiple people? Thanks, Victor

I plan on naming the node the same. How do I resolve the SSH key conflicts?

OK, I'm happy to reinstall Proxmox and rejoin. I noticed Proxmox 5.4 just came out - so we could create a new USB installer for that. This node was node #1 (i.e. the first node in the cluster) - but I assume that's not relevant now. I can the rejoin the Proxmox cluster. How about on the Ceph...

Right - so I can re-create the LVM setup, then use something like pvmove. I was thinking of doing ZFS, actually. Is there some way of re-installing via the ProxMox installer (to get partitions setup), then somehow overwriting it with the config from the old disk? Or is that a stupid idea?

I believe Cloudflare tunnel simply does this for performance reasons, and assumes the HTTP daemon can handle it. Not sure the priority - but will the Proxmox HTTP daemon ever handle chunked transfer encoding in the future?

OK - so boot to a live Linux DVD/CD. And then run rsync? How does this work though, if Proxmox is setup on an LVM drive etc?

Also - I just realised the new M.2 disk is smaller (i.e. 1TB) versus the old 2.5" disk (2TB). So a 1:1 bit copy won't work. Is there another way to migrate a Proxmox installation from one disk to another? Or an easy way to reinstall Proxmox, say, and re-import all the configuration, including...

We have a 3-node Proxmox cluster, with Ceph HA storage. The primary OS disk (i.e. Proxmox) is one of the nodes is failing. We are hoping to replace it - but will be going from a 2.5" SSD to a M.2 SSD. What is the safest way of doing this? Will a 1:1 copy of the disk suffice, and we simply...

I ran cloudlfared with debug logging - I see this: DEBU[0101] 501 chunked transfer encoding not supported CF-RAY=4bf3856bd8795d96-BNE Does that mean something? Is it possible pveproxy is choking on some "chunked transfer encoding" thing? Full output around that request is: DEBU[0101]...

The thing is - the issue only seems to occur when going via Cloudflare's Argo Tunnel. Yet the issue seems to be within Proxmox itself. Are you thinking of using mitmproxy as a reverse proxy instead of Cloudflare?

OK, I did a tail -f on /var/lob/pveproxy/access/log, as I was hitting the "Start" button in the UI - I do see a 501 in the access log: 127.0.0.1 - - [29/03/2019:05:32:26 +1100] "POST /api2/extjs/nodes/syd1/qemu/102/status/start HTTP/1.1" 501 - 127.0.0.1 - - [29/03/2019:05:32:27 +1100] "GET...

OK, I captured traffic on the Proxmox node as follow: root@syd1:~# tcpdump -i lo -v -w proxmox_cloudflare_issue.pcap 'port 85' tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes ^C142 packets captured 296 packets received by filter 0 packets dropped by kernel I...

Wait - tcpdump locally will show the traffic between pveproxy and pvedaemon? =) How does that work? What command variant can I use there?

I checked /var/log/pveproxy/access.log but it didn't reveal much. Is there a way to reveal more verbose information on the HTTP server side?

Hmm - do you know of any way to get the original answer from the node? Or is this something I need to get from the proxy itself?

Hi, The response is empty, here is the response headers: cache-control: max-age=0 cf-ray: 4bc2ad40d8155203-MEL content-length: 0 date: Sat, 23 Mar 2019 19:05:25 GMT expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" expires: Sat, 23 Mar 2019...

Hmm, I checked a working and non-working request - the csrfpreventiontoken is present in both. Failed request: :authority: syd1.example.dev :method: POST :path: /api2/extjs/nodes/syd1/qemu/101/status/start :scheme: https accept: */* accept-encoding: gzip, deflate, br accept-language...

Hi, I'm using Cloudflare Argo Tunnel to provide a reverse web-proxy in front of the Proxmox UI. (We are using this to provide integration with our SSO). I've setup the tunnel, and I can load the Proxmo UI, but certain actions seem to fail - for example, starting VMs returns a HTTP 501...

Actually, I was able to grant the telegraf user permission to those files by adding it to the www-data group. root@syd1:/etc/ceph# usermod -a -G www-data telegraf root@syd1:/etc/ceph# groups telegraf telegraf : telegraf www-data ceph However, I then hit a second issue around permissions...

Aha, so you're saying I could do this via the API? The wiki article isn't very clear on how to setup authentication realms - it seems to imply you need to setup a /etc/pve/domains.cfg file. I'm searching, but the documentation on this is rather sparse - happy to contribute to the wiki...