Looking at recently installed machine I can see that the default https port for smart proxy was changed from 8443 to 9090, check which port your proxy should listen on with cat /etc/foreman-proxy/settings.yml | grep https_port.
Hope this helps Adam On Wed, Nov 16, 2016 at 12:51 PM, Duncan Innes <[email protected]> wrote: > Built my test rig with the latest Katello 3.2 release and looking into the > Remote Execution plugin. I can get it working by manually copying the .pub > key into the client's authorized_keys file, but I'm not seeing the key > published via the API as is claimed in the manual: > > https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#2. > 2RemoteHostsConfiguration > > claims > > curl https://myproxy.example.com:8443/ssh/pubkey >> ~/.ssh/authorized_keys > > is a method for pulling the relevant key onto the host. But I get nothing > back from that URL and can find nothing in the API docs about pubkey. Has > this method been dropped? > > Cheers > > D > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
