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

After os_hardening ssh not working #663

Closed
maddin79 opened this issue Apr 18, 2023 · 4 comments
Closed

After os_hardening ssh not working #663

maddin79 opened this issue Apr 18, 2023 · 4 comments

Comments

@maddin79
Copy link

Hello everyone,

I'm pretty new to Ansible and Server administration. I used the role os-hardening on a fresh install of Debian 11. After this, the SSH Server is not reachable anymore (no route to host). The problem is, the server is hosted by, I think, the worst hoster in the world and I can not get the rescue mode to run. Unfortunately, I can not change the hoster at the moment. I did a new install and the same problem happens.

I used that role on several other Debian servers (10 and 11) and never had that problem. Maybe one of you has a clue what it could be.

Thanks for your work.

Best
Martin

@rndmh3ro
Copy link
Member

Hey Martin,

could you please use the provided bug-report template? This way we can help you better.

@maddin79
Copy link
Author

@rndmh3ro When I clicked on New Issue, it did not show the mentioned templates. Here is the info:

Description: see above

Reproduction: Setup Debian 11 and run the role os-hardening

Current Behavior: SSH : no route to host

Expected Behavior: SSH working

OS / Environment: Debian 11

Ansible Version:

ansible [core 2.14.4]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/mdrees/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.10/site-packages/ansible
  ansible collection location = /home/mdrees/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.10.10 (main, Mar  5 2023, 22:26:53) [GCC 12.2.1 20230201] (/usr/bin/python)
  jinja version = 3.1.2
  libyaml = True

Collection Version: 8.3.0

Additional Info: Can not give more at the moment, because I can not connect to the server. Maybe anyone has a hint what could it be

@rndmh3ro
Copy link
Member

I just tested this on a Vagrant-VM and cannot reproduce it. In general I haven't seen this anywhere where we use this role..

If you can somehow provide us with a valid reproduction case (maybe in the cloud with a specific image), we can try to help you more. Feel free to reopen this then!

@maddin79
Copy link
Author

maddin79 commented May 1, 2023

Hi @rndmh3ro ,

I thought that. I used this role on over 20 other Debian 11 Server and never had any problems. I guess because this is a different server hoster, that the config with this role clashes somehow with the hoster config. No idea why or how.

Thanks for checking.
Best Martin

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

2 participants