Ygtjki

Update: I found this question which seems to be very related. Not sure how exactly.

What am I missing? I can only use ssh when it resolves through https hostnames? Normal ssh it hangs kinda like encryption keys aren't working, but I am using keys that I know have worked in the past.

ssh -v server

OpenSSH_7.9p1, OpenSSL 1.1.1b 26 Feb 2019
debug1: Reading configuration data /home/user/.ssh/config
debug1: /home/user/.ssh/config line 39: Applying options for server
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to x.x.x.x [x.x.x.x] port 22.

my config

Host server
User user
HostName x.x.x.x
IdentityFile ~/.ssh/id_key 

I don't recall ever changing my /etc/ssh/ssh_config and my firewall is set to allow ssh.

If you want to connect to a particular port on the remote system with ssh, you should be using the -p option:

ssh -p 2222 j@10.0.0.231

When the target address does not look like an IP number, which it does not do if you add :2222 to the end of it, ssh will try to resolve the whole string 10.0.0.231:2222 as a hostname using DNS.

If you find yourself connecting to this host on this port often, you may want to set up a configuration for it to make it easier. Edit (or create) your ~/.ssh/config file and add

Host thehost
 User j
 HostName 10.0.0.231
 Port 2222

and then use

ssh thehost

This isn't the full answer, but my encryption keys work with ipv6.

so two possibble answers. I'm dumb and got ssh keys mixed up a billion times a long with my ip addresses, (very likely), but I still can't connect when I try an ipv4 address with encryption keys

So I did something to make ssh only allow encryption keys with ipv6? I don't know if that is even a thing, or how or why. And why would ipv4 work without encryption?