Hostinger randomly decides to close https port - 443 and support is not doing anything

edwinclement08

I have been using hostinger for close to 4 years now and one day they randomly decided to close port 443.

port 80 is open from the public internet. Port 22 is open.
I can ssh into the machine and check curl locally and the ports are open as far as the machine is concerned.

I have been trying to get this resolved for days and honestly - this is pathetic that a web-hosting company doesn't solve the web hosting issue for so long.

My website is hosted at https://blog.edwinclement08.com

Note that http://blog.edwinclement08.com works as expected.

JabJab

Don't worry!

Nor http nor https works here.

However it is a crazy idea that webhosting would drop traffic on 443 port.
You sure that support agent understood the issue?
Was you idk, pointed into getting CloudFlare and MITM traffic there?
Can you share the ticket?

Obelous

How do you know this isn't PEBKAC?

barbarza

@JabJab said:
Don't worry!

Nor http nor https works here.

However it is a crazy idea that webhosting would drop traffic on 443 port.
You sure that support agent understood the issue?
Was you idk, pointed into getting CloudFlare and MITM traffic there?
Can you share the ticket?

What he said

JabJab

Wait, he said he can ssh into machine, so it's not webhosting. It's his VPS.
It's most likely his firewall and PEBKAC.

forest

@JabJab said:
Wait, he said he can ssh into machine, so it's not webhosting. It's his VPS.
It's most likely his firewall and PEBKAC.

Probably firewalled, yeah.

root@forest-vpstc-1-tr:~# for port in 80 443 22; do nc -w5 -vz blog.edwinclement08.com $port; done
Connection to blog.edwinclement08.com (141.136.42.51) 80 port [tcp/http] succeeded!
nc: connect to blog.edwinclement08.com (141.136.42.51) port 443 (tcp) timed out: Operation now in progress
Connection to blog.edwinclement08.com (141.136.42.51) 22 port [tcp/ssh] succeeded!

---

@edwinclement08 Run tcpdump -i eth0 -p tcp port 443 on your server then try to connect to HTTPS. Does it show anything when you try to connect? If yes, then it's your fault. If no, then the fault is something upstream.

yoursunny

@edwinclement08 said:
My website is hosted at https://blog.edwinclement08.com

Note that http://blog.edwinclement08.com works as expected.

Many users would blame the provider while refusing to disclose their website.
You are doing it right and honestly.

However, we cannot connect to open either 443 or 80.

LEBUserJoe

Easy recommendation, quick backup.

Check if your restarted, or the host is restarted then stay / leave.

edmarhub

@JabJab said:
Wait, he said he can ssh into machine, so it's not webhosting. It's his VPS.
It's most likely his firewall and PEBKAC.

fyi: some of hostinger web hosting plans also supports ssh login

edwinclement08

Hey @forest ,

Thanks for that command.

After checking with that command -> I saw that there was some traffic

Further checking in swag container showed an error for letsencrypt cert provisioning issue.

After fixing that, there was some docker, nft, iptables, iptables-legacy firewall issue.

Hardcoded the IP addresses for all the containers and now everything is good.

Thanks!!

Hostinger -> I am pretty sure you did fix something as well in the meantime as well - so thanks

edwinclement08

Thanks @Edmond @LEBUserJoe @edmarhub @yoursunny @JabJab @barbarza @Obelous
for your time as well

JabJab

LMAO

some letsencrypt, docker, nft, iptables, iptables-legacy firewall issue.
Hostinger you did fix something

jmgcaguicla

@edwinclement08 said:
Hostinger -> I am pretty sure you did fix something as well in the meantime as well - so thanks

forest

@edwinclement08 said: Hey @forest ,

Thanks for that command.

After checking with that command -> I saw that there was some traffic

You're welcome.

@edwinclement08 said: Hostinger -> I am pretty sure you did fix something as well in the meantime as well - so thanks

If you saw traffic on 443 then it was purely a misconfiguration on your side.