Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 12:37
    scofield-ua commented #288
  • 12:37
    scofield-ua commented #288
  • Jan 21 00:31
    louis-lau commented #288
  • Jan 20 22:43
    scofield-ua commented #288
  • Jan 20 22:38
    scofield-ua commented #288
  • Jan 20 21:50
    louis-lau commented #288
  • Jan 20 21:42
    scofield-ua commented #288
  • Jan 20 21:26
    louis-lau commented #288
  • Jan 20 21:24
    scofield-ua commented #288
  • Jan 20 20:43
    louis-lau commented #288
  • Jan 20 20:38
    scofield-ua commented #288
  • Jan 20 20:02
    louis-lau commented #288
  • Jan 20 19:59
    louis-lau commented #288
  • Jan 20 19:57
    scofield-ua commented #288
  • Jan 20 11:41
    Berndinox commented #363
  • Jan 18 15:41
    louis-lau commented #98
  • Jan 18 15:39
    CheyenneForbes commented #98
  • Jan 17 22:17
    jhayesdev commented #375
  • Jan 17 22:14
    louis-lau commented #375
  • Jan 17 22:13
    jhayesdev closed #375
Mohammed M R Zourob
@dash7ou
@louis:laureys.me Ya I have disabled the proxy dns only
Louis
@louis:laureys.me
[m]
Ah. Try curl -v smtps://example.com
Replace example.com with your smtp host
Mohammed M R Zourob
@dash7ou
  • Trying x.x.x.x:465...
  • TCP_NODELAY set
  • connect to x.x.x.x port 465 failed: Connection refused
  • Failed to connect to x.email port 465: Connection refused
  • Closing connection 0
    curl: (7) Failed to connect to x.email port 465: Connection refused
    @louis:laureys.me
Louis
@louis:laureys.me
[m]
Seems port 465 isn't open on that ip
Mohammed M R Zourob
@dash7ou
No its opened see this ss: and when I try smtp connection to ip address directly its working fine.
@louis:laureys.me
Louis
@louis:laureys.me
[m]
Curl doesn't lie I'm afraid ;)
Are the ip you're connecting to and the one resolved by curl the same ip?
Mohammed M R Zourob
@dash7ou
Ya same Ip bro @louis:laureys.me
Louis
@louis:laureys.me
[m]
And you're connecting to 465 on that ip?
You can use the curl command with an ip as well
Mohammed M R Zourob
@dash7ou
Nope to 587 because this is port in docker, but this one 465 from reverse proxy by treafik
Louis
@louis:laureys.me
[m]
There's no point in testing two different things haha
Like I said, something is blocking access to port 465
Mohammed M R Zourob
@dash7ou
@louis:laureys.me let me explain to u the direct port in instance ip is 587 and working fine, but when I try to connect to smtp on domain name use traefik its not working because container work on 587 port but treafik config to connect to this container is 465
Louis
@louis:laureys.me
[m]
That's not why
Traefik listens on port 465, and forwards the traffic to the container on port 587
Mohammed M R Zourob
@dash7ou
Yup I know that
Louis
@louis:laureys.me
[m]
Either Traefik isn't running
Or something is blocking access to port 465
Mohammed M R Zourob
@dash7ou
no when I try to open wildduck webmail its working
port 443 working fine
Louis
@louis:laureys.me
[m]
Then traefik is running
Mohammed M R Zourob
@dash7ou
ya I know that why I can not know what exactly the problem
Louis
@louis:laureys.me
[m]
Maybe something else was already listening on port 465?
So docker couldn't let Traefik listen on it
You would have gotten a warning from docker
Mohammed M R Zourob
@dash7ou
Nope because if that right traefik container will not working and told me this port already used
Louis
@louis:laureys.me
[m]
Yep
So, something must be blocking port 465
Only answer I have for ya ;)
Mohammed M R Zourob
@dash7ou
Nope all containers working fine, I told u when I try ip instance direct emails send and smtp connect success
Louis
@louis:laureys.me
[m]
I'm talking about networking though. Not containers.
Could be a firewall for example
Mohammed M R Zourob
@dash7ou
I am not sure maybe the problem with cloudflare because I can not see any thing in logs
Louis
@louis:laureys.me
[m]
Because you're never connecting
Mohammed M R Zourob
@dash7ou
No I have disabled ufw because I am using amazon network
Louis
@louis:laureys.me
[m]
Are you sure amazon doesn't block port 465?
Mohammed M R Zourob
@dash7ou
hm let me check that again to make sure no problem with 465 port
wait there is something strange that happened, when I run curl -v smtps://my.domain from same instance its give me success response @louis:laureys.me
Louis
@louis:laureys.me
[m]
You mean the same instance that's hosting containers?
Mohammed M R Zourob
@dash7ou
yup but not used smtp://localhost, using domain name smtps://my.domain
Louis
@louis:laureys.me
[m]
Linux should route that internally if the hostname is set correctly. So that probably means amazon is indeed blocking port 465
Mohammed M R Zourob
@dash7ou
I do not think so there is anything on internet says aws block port 465
Andris Reinman
@andris9
you can also use openssl to test tls ports
$ openssl s_client -crlf -connect smtp.gmail.com:465
...
220 smtp.gmail.com ESMTP h19sm1432911lfu.138 - gsmtp
any other response - you are firewalled and can't use these ports
Mohammed M R Zourob
@dash7ou
@andris9
139933307688256:error:0200206F:system library:connect:Connection refused:../crypto/bio/b_sock2.c:110:
139933307688256:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111:
connect:errno=111
Louis
@louis:laureys.me
[m]
Same error unsurprisingly haha
Mohammed M R Zourob
@dash7ou
@louis:laureys.me Is there any config i need to check it in config folder ?
Louis
@louis:laureys.me
[m]
Your wildduck config is correct.