F5F Stay Refreshed Software Operating Systems Setting up a Linux home server for remote SSH access.

Setting up a Linux home server for remote SSH access.

Setting up a Linux home server for remote SSH access.

A
AthenasLight
Posting Freak
781
03-22-2023, 01:31 PM
#1
You're looking to configure a Linux home server for remote SSH access. There are videos available that cover this process, often focusing on setting up ports, configuring firewalls, and securing your server. If you prefer hands-on guidance, someone can walk you through each step in real time. Let me know which option suits you best!
A
AthenasLight
03-22-2023, 01:31 PM #1

You're looking to configure a Linux home server for remote SSH access. There are videos available that cover this process, often focusing on setting up ports, configuring firewalls, and securing your server. If you prefer hands-on guidance, someone can walk you through each step in real time. Let me know which option suits you best!

K
kookoo14
Junior Member
19
03-25-2023, 05:01 PM
#2
Package commonly known as OpenSSH is typically installed on server operating systems. The command is usually something like ssh [email protected]. If your Linux name matches the server's, using 127.0.0.1 should work. It’s a good idea to generate both public and private keys for simpler login without a password. You might not remember the details, but searching online should help clarify.
K
kookoo14
03-25-2023, 05:01 PM #2

Package commonly known as OpenSSH is typically installed on server operating systems. The command is usually something like ssh [email protected]. If your Linux name matches the server's, using 127.0.0.1 should work. It’s a good idea to generate both public and private keys for simpler login without a password. You might not remember the details, but searching online should help clarify.

O
opq_the_best
Junior Member
30
04-13-2023, 09:14 PM
#3
Thank you
O
opq_the_best
04-13-2023, 09:14 PM #3

Thank you

C
CrewCraftFTW
Junior Member
3
05-04-2023, 10:06 AM
#4
SSH typically runs on port 22, but when you set up port forwarding, choose a different port. Botnets may attempt to force port 22 expecting an SSH server there. As @BoomerDutch noted, use private keys and turn off password login for better security.
C
CrewCraftFTW
05-04-2023, 10:06 AM #4

SSH typically runs on port 22, but when you set up port forwarding, choose a different port. Botnets may attempt to force port 22 expecting an SSH server there. As @BoomerDutch noted, use private keys and turn off password login for better security.

M
missingmetal
Member
181
05-05-2023, 11:40 AM
#5
M
missingmetal
05-05-2023, 11:40 AM #5

Y
yKanekiPvP
Junior Member
41
05-05-2023, 12:35 PM
#6
Yes that's easier way. Although I'm doing the old way. Both works.
Y
yKanekiPvP
05-05-2023, 12:35 PM #6

Yes that's easier way. Although I'm doing the old way. Both works.

N
NorthwestSun
Member
202
05-07-2023, 04:10 AM
#7
For connecting a home server to the internet from outside your local network, you'll likely face an IP-related challenge. Most residential connections don't provide a fixed IP address, so you'll need to contact your ISP for one or configure a dynamic DNS service. Without this, your server's public IP might shift frequently.
N
NorthwestSun
05-07-2023, 04:10 AM #7

For connecting a home server to the internet from outside your local network, you'll likely face an IP-related challenge. Most residential connections don't provide a fixed IP address, so you'll need to contact your ISP for one or configure a dynamic DNS service. Without this, your server's public IP might shift frequently.

S
someguy220
Member
70
05-07-2023, 06:49 AM
#8
It's not a big deal. Most people use routers, and your IP address stays consistent. I have the same public IP for months. There are free DNS options like noip, and I've got a guide for it.
S
someguy220
05-07-2023, 06:49 AM #8

It's not a big deal. Most people use routers, and your IP address stays consistent. I have the same public IP for months. There are free DNS options like noip, and I've got a guide for it.

Y
YouriiruoY
Member
212
05-07-2023, 07:21 AM
#9
Interesting. I recall fond memories of my public IP shifting three times within a week during my home server experiments, though that was years ago. Perhaps things have evolved. NOIP seems to address the problem, and it isn’t an impossible challenge if it arises—I just found it somewhat bothersome when I first set up the home server.
Y
YouriiruoY
05-07-2023, 07:21 AM #9

Interesting. I recall fond memories of my public IP shifting three times within a week during my home server experiments, though that was years ago. Perhaps things have evolved. NOIP seems to address the problem, and it isn’t an impossible challenge if it arises—I just found it somewhat bothersome when I first set up the home server.

K
kervinc
Posting Freak
804
05-07-2023, 10:55 AM
#10
You must enable and redirect port 22 instead of 443 and 80 for remote SSH access.
K
kervinc
05-07-2023, 10:55 AM #10

You must enable and redirect port 22 instead of 443 and 80 for remote SSH access.