-
Notifications
You must be signed in to change notification settings - Fork 741
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
Comments
Hey Martin, could you please use the provided bug-report template? This way we can help you better. |
@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:
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 |
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! |
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. |
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
The text was updated successfully, but these errors were encountered: