Amazon ec2 傀儡服务器提供；服务器上出现错误400:找不到类；但是没有大师的作品

我有一个使用puppet provisioning和vagrant的工作环境。现在我在AWS EC2上设置了一个puppetmaster服务器，其中包含与vagrant相同的模块，但是当我尝试从代理访问它时，我获取

错误：无法从远程服务器检索目录：服务器上的错误400：在节点ip-172-31-34-78.us-west-2.compute.internal上找不到ip-172-31-34-78.us-west-2.compute.internal的类co_gocdserver

/etc/puppet/manifests/site.pp
目前看起来就像这样：

node default {
  include co_gocdserver
}

/etc/puppet/modules/co_gocdserver/manifests/init.pp
看起来像：

class co_gocdserver {
 include gocd::server

 file { "ssh":
   path => "/var/go/.ssh",
   source => "puppet:///modules/co_baseconfig/ssh",
   recurse => true,
   require => Package["go-server"],
 }
}

更新：这里是主机上的
/etc/puppet/puppet.conf
：

[main]
    # The Puppet log directory.
    # The default value is '$vardir/log'.
    logdir = /var/log/puppet

    # Where Puppet PID files are kept.
    # The default value is '$vardir/run'.
    rundir = /var/run/puppet

    # Where SSL certificates are kept.
    # The default value is '$confdir/ssl'.
    ssldir = $vardir/ssl

    #node_name = facter
    #node_name_fact = puppet_node

    basemodulepath = /etc/puppet/modules

[master]
    basemodulepath = /etc/puppet/modules

[agent]
    # The file in which puppetd stores a list of the classes
    # associated with the retrieved configuratiion.  Can be loaded in
    # the separate ``puppet`` executable using the ``--loadclasses``
    # option.
    # The default value is '$confdir/classes.txt'.
    classfile = $vardir/classes.txt

    # Where puppetd caches the local configuration.  An
    # extension indicating the cache format is added automatically.
    # The default value is '$confdir/localconfig'.
    localconfig = $vardir/localconfig

是否引入了任何明显的错误，或者如何调试此错误？
解决了此问题。问题是我把模块目录的权限搞砸了，而puppetserver作为用户puppet运行，没有读取权限

我怎么能把权限搞砸呢？正确的问题。简单回答：

rm -rf /etc/puppet/modules
ln -s /home/centos/puppet/modules /etc/puppet/modules

保留此线程作为引用