Recent content by mruepp

  1. M

    Saltstack LXC Deployment not working

    This is interesting, because in the API Documentation this is stated otherwise: http://pve.proxmox.com/pve-docs/api-viewer/index.html
  2. M

    Saltstack LXC Deployment not working

    Now did a deployment try with the api. curl --insecure --cookie "$(<cookie)" https://$APINODE:8006/api2/json/nodes/$TARGETNODE/status | jq '.' is returning meaningfull things like: { "data": { "cpuinfo": { "mhz": "2662.859", "user_hz": 100, "hvm": 1, "cpus": 48...
  3. M

    Saltstack LXC Deployment not working

    Bump. Any ideas? Found this: https://github.com/saltstack/salt/issues/28048 It suggests that host: value has to be NOT the FQDN, but the pve hostname. So I come back to The following exception was thrown when trying to run the initial deployment: 400 Client Error: Parameter verification...
  4. M

    Saltstack LXC Deployment not working

    Sorry wrong copy/paste: Also getent works: admin@pve01:~$ getent hosts pve01 10.66.4.121 pve01.p.fir.io pve01 pvelocalhost admin@pve01:~$ getent hosts pve01.p.fir.io 10.66.4.121 pve01.p.fir.io pve01 pvelocalhost admin@pve01:~$ getent hosts 10.66.4.121 10.66.4.121 pve01.p.fir.io...
  5. M

    Saltstack LXC Deployment not working

    Could there be a problem with ipv6? We do not configured ipv6 but proxmox configures local link addresses. Tested Name Resolution, Connectivity, everything. Cluster communication works perfectly. Interfaces file looks like: auto lo iface lo inet loopback iface eth0 inet manual iface eth1...
  6. M

    Saltstack LXC Deployment not working

    When I try to use another deployment host (api host where i connect is still pve01) by using: host: pve02.p.fir.io i get the following error: [ERROR ] Error creating testubuntu on PROXMOX The following exception was thrown when trying to run the initial deployment: 500 Server Error: proxy...
  7. M

    Saltstack LXC Deployment not working

    Hi, yes that is the case. Everything works fine so far.
  8. M

    Let’s Encrypt with Proxmox VE

    Yes, acme.sh supports route53 or other dns providers which provides fully automated renewal by creating txt records automatically
  9. M

    Saltstack LXC Deployment not working

    Hi, the Certificates are the generated ones - see screenshot. The System is a cluster of 10 Nodes. The difference in the Error is: host: pve01 vs host: pve01.p.fir.io
  10. M

    Let’s Encrypt with Proxmox VE

    Cool I just saw that acme.sh will support dns-01 mode which doesnt rely on port 80. Will try and report back!
  11. M

    Let’s Encrypt with Proxmox VE

    Hi, thx. You have to have Split DNS though, I guess? So if i have host pve01.company.domain pointing to 10.x.x.x on our external dns which is never resolvable, it won´t work, right? Or are you issuing the same cert to all hosts in the cluster? E.g. do you define for instance...
  12. M

    Let’s Encrypt with Proxmox VE

    I guess with proxmox hosts behind firewall and private ip space, letsencrypt does not work. Am I right? So if i have host.internal.domain with 10.x.x.x, is there a best practice to get a proxmox cluster working with lets encrypt behind firewall?
  13. M

    Saltstack LXC Deployment not working

    I filed an Issue on Github: github.com/saltstack/salt/issues/39755 When I use the fqdn of the deployment host instead of the hostname without domain, the error changes to: HTTPError: 596 Server Error: ssl3_get_server_certificate: certificate verify failed This occurs when I use "verify_ssl...
  14. M

    Saltstack LXC Deployment not working

    Seems I can not get the whole response from the debug or even trace message of salt-cloud. Is there any api log on the proxmox I can debug? Thx
  15. M

    Saltstack LXC Deployment not working

    Hi, we want to use salt cloud provider to deploy lxc & qemu. I am able to connect to the proxmox host, am able to list images and nodes, but when I try to deploy a container, I get following error: [DEBUG ] MasterEvent PULL socket URI: /var/run/salt/master/master_event_pull.ipc [DEBUG ]...