Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It's common for networks to block 172.16.0.0/12, since it's private IP space that shouldn't be routed on the public internet.
18.104.22.168, which your system is trying to connect to, is not in that block, but is "nearby". But if your network administrator (or ISP?) is blocking it anyway (due to incorrectly putting in the IP range), that would explain why you can't connect to it.
Thanks guys, it was a mistake made my self, I assigned a network with 22.214.171.124/16 for a group of containers in docker. I was doing everything wrong about assigning IPs to each project. I will fix that and do everything right!