The current problem is when I try to connect to a ssh server (from a university I am currently attending) with the following (example) command:
ssh -Y root@example.com
Then I get the following error:
Too many recursive configuration includes
Beforehand, I could connect to the server without any problem. However, I tried to enable X11 forwarding to run graphics applications. I did this by using the nano editor:
nano -w /etc/ssh/ssh_config
In the nano editor, I removed "#" from ForwardX11 and also changed "no" to "yes". Afterwards, I saved and closed the nano editor by pressing ctrl + O and ctrl + X respectively. Finally, I tried numerous ways to restart "ssh(d) service" (to be honest, since I am new to nano editor and ubuntu in general, I just followed the different sites that explains how to enable ForwardX11). I have tried using the following commands:
systemctl restart sshd.service
systemctl restart sshd
sudo systemctl restart sshd
sudo systemctl restart ssh
service sshd restart
sudo service ssh restart
When trying to restart sshd (not ssh), I get the following message:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
This could be a seperate problem not relating to the problem stated in this question. However, I just wanted to tell you what I did before I couldn't connect the university's ssh server anymore.
But after I did everything mentioned above, I couldn't connect to the university's server anymore. Again, the error message I receive is:
Too many recursive configuration includes
What have I done wrong? I suspect I did something wrong in the nano editor.
P.S. My current Ubuntu version is 20.04
systemctl
commands on your local computer, or on the remote system? Is your local system WSL? Changes to/etc/ssh/ssh_config
shouldn't have affected the ssh server at all (since that's the system-wide ssh client configuration file).ssh localhost
on my computer, I got the same messageToo many recursive configuration includes
. As a ssh client, I cannot connect to the ssh server of my university anymore.ssh -Y -v root@example.com
orssh -Y -vv root@example.com
) and see if that narrows down the issue - in particular look at any and all debug lines related to client config files.