Closed eyoboue closed 1 month ago
The timeout looks like an issue on your end and not ours - especially if it works on another port! Closing as we don’t believe this is an issue in our code (according to the logs) but feel free to object if you find evidence to the contrary.
The timeout looks like an issue on your end and not ours - especially if it works on another port! Closing as we don’t believe this is an issue in our code (according to the logs) but feel free to object if you find evidence to the contrary.
@aeneasr,
I think you should take a look. It works only with https default port (443
). My sms gateway works fine and I have not timeout when make request with Postman or from other deployed services. So I tried Ory Kratos SMS sending on other services which have custom ports other than 443 and it doesn't work (same timeout issue). I'm unable to explain why that happened.
Many companies have own SMS gateway exposed on custom https port and I think that's real issue.
It‘s probably a firewall issue. If it works with one port it works with all ports, we don’t discriminate on ports ;) Also, we‘re using random ports in our tests.
Thanks, you are probably right.
But I disable all firewall and the issue still persists.
I have another service (write with Golang) in the same docker-compose file, deployed on same stack and It's able to send successful SMS where the Kratos service fails.
I will use another SMS gateway exposed on 443 https port for now and I will keep looking.
Preflight checklist
Ory Network Project
No response
Describe the bug
I configured phone & password registration flow with SMS verification MFA on custom HTTPS SMS gateway. When submitted registration, It's unable to send SMS after max attempts reached. Hint: My SMS gateway has custom port for instance
9443
. I get success sms sending when I tried on other endpoints with defaulthttps
port. But I get failed with customhttps
ports like8843
, etc.Reproducing the bug
Relevant log output
Relevant configuration
Version
v1.2.0
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker Compose
Additional Context
No response