Search results

I added these two headers and now have a different error message: sync group vm/101 failed - invalid protocol name reverse_proxy https://192.168.2.58:8007 { transport http { tls_insecure_skip_verify } header_up Connection...

@McTwist did you find a solution w/Caddy?

I'm joining in with the same problem. The bug report is marked fixed, but it's still broken for me. (headers) { header -x-powered-by header -server header Content-Security-Policy "frame-ancestors 'self'; upgrade-insecure-requests;" header X-LB-Server...

I'm joining in with the same problem, but behind Caddy instead of traefik. (headers) { header -x-powered-by header -server header Content-Security-Policy "frame-ancestors 'self'; upgrade-insecure-requests;" header X-LB-Server {system.hostname} header...

I'm joining in with the same problem, but behind Caddy instead of nginx. (headers) { header -x-powered-by header -server header Content-Security-Policy "frame-ancestors 'self'; upgrade-insecure-requests;" header X-LB-Server {system.hostname} header...

Hi, I am trying to setup a remote sync job with two PBS's. It was able to see the remote datastore, and I setup a new sync job. When trying to run the job, I am receiving errors "Missing upgrade header". See screenshot: I am not certain what this is referring to. At first thought, I...

Any movement on this yet? I'm needing to PUSH instead of PULL...

Hi guys, PBS 2.1 Two servers: remote => located at another datacenter off-site nexus => located on-site My goal is for our 3-node Proxmox cluster to backup to the local PBS ('nexus'), and then for 'nexus' to replicate to the remote server 'remote'. It seems that PBS uses a "pull" method as...