Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: User interaction is not allowed #88

Open
fleadope opened this issue Sep 26, 2017 · 6 comments
Open

Error: User interaction is not allowed #88

fleadope opened this issue Sep 26, 2017 · 6 comments

Comments

@fleadope
Copy link

Thought I had it licked with I read this issue: #85, but no such luck.

I'm using Bootleg to attempt to deploy a phoenix app, and am getting this error trying to connect to a Debian host. HashKnownHosts is 'no' on the server AND client, I can connect using ssh, and I added silently_accept_known_hosts.

Not sure what further info I can give you (is there a way to increase verbosity?), please advise.

Thank You!

@klappradla
Copy link
Member

Hey @fleadope thanx for reporting 🙏

We're currently quite busy with client work, so it might take us a while until we can dig into this. In order to be able to understand this it would be nice though if you could give us the details of which version of Debian you're running, which changes you made to the default ssh config, etc.
At best, provide me with a Dockerfile so that I can set up a simple container with your setup ✌️

@snewcomer
Copy link

snewcomer commented Nov 10, 2017

Also getting this. Trying to build on localhost on Ubuntu 17.10 w/ bootleg

role :build, "localhost", user: "snewcomer", workspace: "/tmp/bootleg/build"

(~/Github/project)$ mix bootleg.build production
Creating remote context at '/tmp/bootleg/build'
[localhost ] (export REPLACE_OS_VARS="true" && /usr/bin/env mkdir -p /tmp/bootleg/build)
** (SSHError) SSHKit returned an internal error on localhost: 'User interaction is not allowed'
    lib/bootleg/ssh.ex:70: anonymous fn/2 in Bootleg.SSH.run/2
    (elixir) lib/enum.ex:1255: Enum."-map/2-lists^map/1-0-"/2
    lib/bootleg/ssh.ex:163: Bootleg.SSH.run!/2
    lib/bootleg/ssh.ex:87: Bootleg.SSH.validate_workspace/3
    lib/bootleg/ssh.ex:51: Bootleg.SSH.init/2
    lib/strategies/build/distillery.ex:9: Bootleg.Strategies.Build.Distillery.init/0
    lib/strategies/build/distillery.ex:16: Bootleg.Strategies.Build.Distillery.build/0
    lib/bootleg/config.ex:356: Bootleg.Config.invoke/1

A couple of things I tried:

  1. Add 127.0.0.1 to known_hosts
  2. set HashKnownHosts to no

@snewcomer
Copy link

Changing to

role :build, "127.0.0.1", user: "snewcomer", workspace: "/tmp/bootleg/build"

works 🤷‍♂️

@snewcomer
Copy link

snewcomer commented Nov 11, 2017

@klappradla So what that makes me think is localhost is looked up and finds the ipv6 address. Whereas 127.0.0.1 is the ipv4 address. Former doesn't work, latter does. Trying on remote digital ocean server and getting the same 'User interaction is not allowed'; however, after adding silently_accept_hosts: true, it worked.

@pmeinhardt
Copy link
Contributor

Thanks a lot for posting your solution to the problem 🎉

To maybe narrow it down further: In which way, did you provide the host for the digital ocean server: Using a hostname or the IP address? Which of these did you use when first connecting via the ssh command?

Cheers 😃

@snewcomer
Copy link

So the build step was locally on my ubuntu machine. The deploy step was an easy fix w/ silently_accept_hosts. And to deploy, the host was the IP address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants