Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have installed Fedora 36 server addition in my spare laptop. How can I access it from another machine remotely ? Is there any documentation for that ? My goal is to test various Ansible commands to this server. I can create small VM using DigitalOcean , Amazon Web Services or Linode. However since I have an extra physical machine I wish set it up as a remote server. Any suggestions ?
I have installed Fedora 36 server addition in my spare laptop. How can I access it from another machine remotely ? Is there any documentation for that ? My goal is to test various Ansible commands to this server. I can create small VM using DigitalOcean , Amazon Web Services or Linode. However since I have an extra physical machine I wish set it up as a remote server. Any suggestions ?
Install and run sshd on it. Then ssh to it. Lots of about using ssh and sshd online.
SSH is the way to go. You will have full access to the shell through it and that will give you all the capabilities you would have had sitting at the console itself. The shell is the main system interface which has been refined and advanced for over four decades.
If the server is publicly facing, it would be recommended to use either SSH keys or SSH certificates for authentication and then turn off password authentication.
SSH is the way to go. You will have full access to the shell through it and that will give you all the capabilities you would have had sitting at the console itself. The shell is the main system interface which has been refined and advanced for over four decades.
If the server is publicly facing, it would be recommended to use either SSH keys or SSH certificates for authentication and then turn off password authentication.
I tried to access my server machine ( Fedora 36 ) from my work station with the command : ssh root@ip_address_of_my_server_machine.Every time I try to log in I am getting an error message :
WARNING : REMOTE HOST IDENTIFICATION HAS CHANGED !
Please note that I have installed fedora 36 server addition in my spare laptop and trying to ssh it from my another laptop. Is there anything I am missing here ?
Distribution: Ubuntu based stuff for the most part
Posts: 1,173
Rep:
Is the server using an IP you have used before? The error you are getting seems to indicate that it is expecting a different SSH server.
Look in your .ssh/known_hosts for that IP and if you see it, remove its entry. You should be able to connect afterwards.
Is the server using an IP you have used before? The error you are getting seems to indicate that it is expecting a different SSH server.
Look in your .ssh/known_hosts for that IP and if you see it, remove its entry. You should be able to connect afterwards.
In my server machine I ran this command : ip addr show | grep "inet " and from there I got the inet address. then I tried to ping the server from my workstation using this command :
ping -c1 10.1.1.5 {my inet address is different } and here is what I got as an output :
PING 10.1.1.5 (10.1.1.5) 56(84) bytes of data.
64 bytes from 10.1.1.5: icmp_seq=1 ttl=64 time=6.94 ms
--- 10.1.1.5 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 6.943/6.943/6.943/0.000 ms
but when I tried to ssh 10.1.1.5 I am getting the same error message . please note that I have never connected via ssh from my workstation to the server before.
but when I tried to ssh 10.1.1.5 I am getting the same error message . please note that I have never connected via ssh from my workstation to the server before.
Perhaps not, but is seems that you connected to some other machine with that IP before. Did you check your ~/.ssh/known_hosts file?
Perhaps not, but is seems that you connected to some other machine with that IP before. Did you check your ~/.ssh/known_hosts file?
Evo2.
I think you are right! I found two files in my work stations ~/.ssh/ location : known_hosts and known_hosts.old ! now should I remote the IP address of the server from both file ?
I think you are right! I found two files in my work stations ~/.ssh/ location : known_hosts and known_hosts.old ! now should I remote the IP address of the server from both file ?
Never mind . the IP address was stored in known_hosts and I have removed that. now I tried to ssh {IP ADDRESS } again and this time getting this error message : permission denied try again !
Never mind . the IP address was stored in known_hosts and I have removed that. now I tried to ssh {IP ADDRESS } again and this time getting this error message : permission denied try again !
So that likely means one of 3 things.
1. Wrong password
2. Wrong username
3. Wrong IP address
I am in ! Actually I have to run an extra command in the server machine : sudo systemctl enable --now sshd
I don't think that was the solution. That just ensures that sshd will automatically start. It would have already been running otherwise
you wouldn't have seen the permission denied error messages that you reported.
I tried to access my server machine ( Fedora 36 ) from my work station with the command : ssh root[b][/b@]ip_address_of_my_server_machine.
Now that you are in, the first thing you need to do is start using SSH keys for authentication and then, once you have confirmed that they work, turn off password access. Note that by default root denies password access and uses only keys for remote login.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.