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

Running simple playbooks kills SSH connection #72

Open
htgoebel opened this issue Jan 8, 2016 · 3 comments
Open

Running simple playbooks kills SSH connection #72

htgoebel opened this issue Jan 8, 2016 · 3 comments

Comments

@htgoebel
Copy link
Contributor

htgoebel commented Jan 8, 2016

When setting up a fresh test system using

debops bootstrap --sudo -K -l server-test
debops yacy -l server-test   # this is my new playbook

the ssh connection get blocks as soon as "Apply iptables rules if ferm is enabled" is run.

The new playbook simply installs YaCr behind nginx.

@drybjed
Copy link
Member

drybjed commented Jan 8, 2016

debops.ferm uses data gathered by debops.core role to allow connections from Ansible Controller. debops.core is a required role, so if you only want to use specific playbooks with a host without running the common.yml playbook, you should at least include the core.yml playbook in your set of playbooks.

Alternatively, you can use ferm_ansible_controllers to tell ferm which hosts should be explicitly allowed to connect to the remote host without any restrictions.

@varac
Copy link

varac commented Dec 11, 2017

I ran into this as well. I agree with @drybjed but this behaviour should be documented in BIG LETTERS on the debops-ferm doc entry page pls !

@drybjed
Copy link
Member

drybjed commented Dec 11, 2017

You can do the PR yourself. :-) If you do, please do it against the DebOps monorepo so it can be included in the future documentation, when it's updated and exported from that repository.

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

3 participants