hi @bsifue , is that system reachable from the outside world? what happen when you do telnet the address + port ?
at foreman side, check if the http service is up and running, and if iptables/firewalld is configured correctly to allow https traffic .
lets start with that
The installer automatically detect the FQDN of the machine. Chances are, the domain is not publicly accessible as @kalessin suggested. If you know the IP of the server, try accessing it with https://$theIP. Of course you’d need to accept the SSL exception. If that works, it’s likely DNS issue. If not, it can be the firewall issue.
I would like to see the full output of what you are doing to help you better and faster.
What I meant with the telnet, was to test https, not ssh. Please do:
telnet {f.q.d.n.} 443
where {f.q.d.n.} should be translated to the hostname you have set up for that system.
On the other hand, I feel you have not published your host/vm to the public. Try to publish it on azure to the public (limiting access), as far I can tell, your azurecentos.internal.cloudapp.net is internal only.