Ok, great! Your welcome.
Yeah hope also so, they seem to be a bit slow with merging the pull requests at the moment.
Yeah hope also so, they seem to be a bit slow with merging the pull requests at the moment.
API debug: Vagrant-proxmox and LXC = 400 Bad Request
- Thread starter Denny Fuchs
- Start date
hi,
sorry to disturbing you again. I have a very small question: do you remember which IP address vagrant wants to use for SSH and doing the rest?
In my case: Vagrant uses the nodes address and a high port, instead of the IP configured with
ublic_network ip: 1.2.3.4 ...
I forked the vagrant-proxmox to apply the patches .. so our devop wants to create a patch to solve the problem.
sorry to disturbing you again. I have a very small question: do you remember which IP address vagrant wants to use for SSH and doing the rest?
In my case: Vagrant uses the nodes address and a high port, instead of the IP configured with
ublic_network ip: 1.2.3.4 ...I forked the vagrant-proxmox to apply the patches .. so our devop wants to create a patch to solve the problem.
Uhm, from the top of my head not quite, sorry, I hadn't a vagrant pre configured template available so it let the connection be as it was, didn't gave much attention if the IP was correct (should have though), but I remember the high port. If I try it now I get:
It looks like it wants a forwarded port on the host here, strange, I'm to less involved into Vagrant to check if your solution in the issue tracker is correct.
Ok cool, sad that the original repo seems quite dead at the moment, I can give it a look if its something Proxmox related.
Code:
DEBUG ssh: Checking whether SSH is ready...
INFO machine: Calling action: read_ssh_info on provider Proxmox (uno/90006)
INFO interface: Machine: action ["read_ssh_info", "start", {:target=>:box}]
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_read_ssh_info #<Vagrant::Action::Builder:0x00000001e28208>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000001e3f908>
ERROR warden: Error occurred: There are errors in the configuration of this machine. Please fix
the following errors and try again:
vm:
* Ports to forward must be 1 to 65535
...It looks like it wants a forwarded port on the host here, strange, I'm to less involved into Vagrant to check if your solution in the issue tracker is correct.
Ok cool, sad that the original repo seems quite dead at the moment, I can give it a look if its something Proxmox related.