How do I get to the Foreman portal? I just installed it on a centos7 virtualbox

Support
1

Problem:
After successful foreman installation, I cannot go to the below link. No site is displayed when I got.

Success!

Expected outcome:
Follow link and get the Foreman Portal for the server installed it on

Foreman and Proxy versions:
2.4 on Centos7

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

2

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

1 Like
3

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.

1 Like
4

Hello,

Thank you both for getting back to me.

@Kalessin, for telnet, I get back that there is an invalid ssh
identification string. Additionally, iptables is not running.

I used Microsoft azure to host a Linux machine.

5

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.

6

It’s hard to understand your setup, on the subject you are saying ‘installed… on virtualbox’ while you are showing to have it on Azure.

You need to review how to access http/s content in Azure. It’s not a Foreman related problem so far. You normally need:

  • a public IP address, check doing a ‘ping your.ip.address’ .
  • a public DNS record, check doing ‘host the.hostname.on.internet’
  • an open port, check with ‘telnet the.hostname.on.internet 443’ or ‘telnet your.ip.address 443’
  • a routing rule to match your external port to your internal vm. check internal on azure portal.
1 Like