Error 406 while communicating with puppet on port 443

[Ed Lima]

I'm using puppet enterprise 3.3.1 and all my nodes/master are running on Ubuntu 14.04.1. This is my puppet.conf:

root@puppet:~# cat /etc/puppetlabs/puppet/puppet.conf
[main]
certname = puppet.openstacklocal
dns_alt_names = puppet,puppet.lan
vardir = /var/opt/lib/pe-puppet
logdir = /var/log/pe-puppet
rundir = /var/run/pe-puppet
basemodulepath = /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules
server = puppet.openstacklocal
user = pe-puppet
group = pe-puppet
archive_files = true
archive_file_server = puppet.openstacklocal

[master]
certname = puppet.openstacklocal
ca_name = 'Puppet CA generated on puppet at 2014-08-14 05:03:59 +0000'
reports = console,puppetdb
node_terminus = console
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
storeconfigs = true
storeconfigs_backend = puppetdb

[agent]
report = true
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
graph = true
pluginsync = true
environment = production

I'm have 7 nodes so far but there are 2 of them giving me lots of grief. I cannot get them to work properly with the current puppet master. I used them with the free version in the past and they worked fine. Since there are 2 different problems I'll mention one of them here and will create another topic for the second one. I already looked all over google to try and fix it but couldn't find anything helpful.

Basically this is what I get:

root@search:~# puppet agent -t
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Error 400 on SERVER: Error 406 while communicating with puppet.openstacklocal on port 443:
Info: Retrieving plugin
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/platform_tag.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/postgres_default_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_puppetdb_server_status.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/staging_http_get.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/custom_auth_conf.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/windows.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/root_home.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_postgres_default_version.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/pe_build.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/opt/lib/pe-puppet/lib/facter/iptables_version.rb
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node search.openstacklocal: Error 406 while communicating with puppet.openstacklocal on port 443:
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I can get to port 443 on the master fine from the node:

root@search:~# telnet puppet.openstacklocal 443
Trying x.x.x.x...
Connected to puppet.lan.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

The node shows up on the dashboard however the catalog is empty. I also cannot execute any manifests from the master on it.

I already tried several times to remove puppet from the node and reinstall from scratch, same thing with the master but I always get the same error.

Any ideas?

[Felix Frank]

On 08/22/2014 05:52 AM, Ed Lima wrote:

I can get to port 443 on the master fine from the node:

Well, that's nice and all, but are you aware that Puppet uses port 8140 by default?

Are you using Passenger? Please check your Apache configuration then.

If you are not using Passenger, then 443 is most definitely wrong, because your master is not overriding the masterport setting.

Is masterport=443 set in the puppet.conf of your agent? It is not quite clear to me why your agent tries that port at all.

Thanks,
Felix