SSH is not working
-
Hello,
I'm using pfSense 2.8.1 and I enabled SSH via WebGUI:
I also wrote a firewall rule for it:

But I still can't connect to the server via SSH. Why?
Thank you.
-
@hack3rcon your rule is wrong, the source must be LAN subnets and not address.
-
Hello @slu,
I changed it to subnets, but doesn't matter. -
@hack3rcon SSH service is running?
Status -> Services?Delete the old states after you changed such a rule:
Diagnostics -> Statues -> Reset States -
-
@hack3rcon no your states (open connections).
-
@slu I did, but I can't connect to the server via ssh command.
-
@hack3rcon error is timeout?
You are connected to LAN with you client? -
@slu Yes. I was able to connect to version 2.7.2 with SSH. This happened after the upgrade.
-
@hack3rcon said in SSH is not working:
I also wrote a firewall rule for it:
Why would you need a rule - the default anti-lock out rule would allow anything on lan to talk to your webgui port and your ssh port
Did you disable this rule?

Even if you did - the default any any rule on lan would also allow it. Please post up your lan rules.
If you test port to pfsense lan IP that your trying to ssh to - does this come back as up?

-
Hello @johnpoz,
I guess pfSense is not stable. I got some odd errors. -
@hack3rcon what errors?
-
ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg" -
@hack3rcon posting that error again will confuse people, if then refer to the other thread you opened.
Please provide a network diagram, if that is the same installation like in the other thread, then it is an unusual setup with only one interface. Without reading your other threads, people won't know that.
-
@hack3rcon so you are trying to get to ssh to fix that error.. you can run commands via the gui
diagnostics / command prompt
But if only a lan - not sure how pfsense would get to the internet, normally with a single interface pfsense install the interface is the "wan" in pfsense.
-
Hello @johnpoz,
In pfSense 2.7.2 I was able to connect to the server via SSH without any problems. After upgrading to 2.8.1 this problem occurred.

