Port refuses to open, Debian 11, ufw & postgres >:(

[real harness]

I'm running debian11 with postgres15.2 and ufw installed. Ive tried opening port 22 (which I can connect to no problems), 5432 (and eventually 8894) through ufw at first by running the following as root: ufw allow $PORT and restarting the ufw service by running systemctl restart ufw. As for the postgresql.conf I've set listen_addresses = '*' and updated the port = $PORT (where $PORT is the above ports listed). In my pga_hba.conf I've added host all all 0.0.0.0/0 md5. and restarted postgres using systemctl restart postgres. Despite all this, the port itself isn't open, it seems like something is interfering with the ufw command but Im not even sure where to begin looking outside of iptables entries and ufw status entries which Ive checked and they look good. Does anyone know why this freaking port won't open?

(Using ionos as a VPS provider btw, not sure how relevant that is but Ive been able to do this no problem with different hosting providers before, also have fail2ban installed)

[cedar walrus]

have you tried thinking hard?

[real harness]

Ive tried thinking really hard for the past 4 hours

[cedar walrus]

hm, well that’s all i’ve got. good luck!

[plain egret]

Can you show what lsof -i gives?

[real harness]

yup yup!

COMMAND   PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dhclient  666     root    9u  IPv4  15091      0t0  UDP *:bootpc 
dhclient  712     root    8u  IPv6  15127      0t0  UDP [fe80::250:56ff:fe24:2fe8]:dhcpv6-client 
sshd      780     root    3u  IPv4  15289      0t0  TCP *:ssh (LISTEN)
sshd      780     root    4u  IPv6  15300      0t0  TCP *:ssh (LISTEN)
sshd      941     root    4u  IPv4  18921      0t0  TCP 162.222.205.26:ssh->S0106848dc7ebd367.ed.shawcable.net:40866 (ESTABLISHED)
openvpn  5066   nobody    7u  IPv4  37670      0t0  UDP *:8894 
postgres 5325 postgres    5u  IPv4  39080      0t0  TCP *:8944 (LISTEN)
postgres 5325 postgres    6u  IPv6  39081      0t0  TCP *:8944 (LISTEN)

was trying out some different ports lol

[plain egret]

And you're trying to connect to the postgresql server and it doesn't work? It's weird. Have you created a user that ad the right to connect to another host than localhost?

[real harness]

Yup trying to remotely connect and its failed with connection timing out. Yeah I tried creating a user and setting permissions for that but still running into issues. I just reimaged the machine tho so Ill see how it goes this time

[plain egret]

What I meant is, does the user in the users table has the hostname set to localhost or 0.0.0.0 or an actual IP

[real harness]

not sure how the postgres users table is relevent, Im trying to connect through dbeaver and Ive created the postgres users with encrypted passwords. Are you maybe talking about the pg_hba.conf?

[plain egret]

Yes sorry, I was answering fast while I had internet haha

[real harness]

haha I see I see, and yeah my full pg_hba.conf looks like this:

# Database administrative login by Unix domain socket
local   all             postgres                                peer

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            scram-sha-256
# IPv6 local connections:
host    all             all             ::1/128                 scram-sha-256
# Allow replication connections from localhost, by a user with the
# replication privilege.
local   replication     all                                     peer
host    replication     all             127.0.0.1/32            scram-sha-256
host    replication     all             ::1/128                 scram-sha-256
host    all             all             0.0.0.0/0               md5
host    all         all                 0.0.0.0/0               scram-sha-256

ive tried quite a few variations as well

[plain egret]

Mmh

[real harness]

I really think its a weird firewall problem tbh

[plain egret]

Seems like it yes

[real harness]

LOL

yeah

seems like ionos is messing with me

works on port 80

lmao

[plain egret]

That's weird. Maybe it's a security thing?

[real harness]

yeah idk, Im gonna get in touch with them and ask about that though cause I dont want my db on port 80 lol

Im an idiot lmfao

they have a firewall policies page

[oblique spoke]

You did not activated the Ticket System | %ticketsetup enable

[real harness]

hm

[plain egret]

You want to close the post?