After deployment, app says Couldn't find a template named "layout" or "layout"

Hi,

I deployed 2 meteor apps using same database (built them with iron-cli). The first one worked well, but the second one had error

Couldn't find a template named "layout" or "layout". Are you sure you defined it?

First app’s mup.js

module.exports = {
  servers: {
    one: {
      host: 'SERVER_IP',
      username: 'root',
      pem: 'ID_RSA_LOCATION'
    }
  },

  app: {
    name: 'app1',
    path: '../../app',

    servers: {
      one: {},
    },

    buildOptions: {
      serverOnly: true,
    },

    env: {
      ROOT_URL: 'https://sub.domain.com',
      MONGO_URL: 'mongodb://localhost/meteor',
    },

    docker: {
      image: 'abernix/meteord:node-8.4.0-base',
    },

    enableUploadProgressBar: true
  },

  mongo: {
    version: '3.4.1',
    servers: {
      one: {}
    }
  },

  proxy: {
    domains: 'sub.domain.com,www.sub.domain.com',
    ssl: {
      letsEncryptEmail: 'support@domain.com',
      forceSSL: true
    }
  }
};

Second app’s mup.js

module.exports = {
  servers: {
    one: {
      host: 'SERVER_IP',
      username: 'root',
      pem: 'ID_RSA_LOCATION'
    }
  },

  app: {
    name: 'app2',
    path: '../../app',

    servers: {
      one: {},
    },

    buildOptions: {
      serverOnly: true,
    },

    env: {
      ROOT_URL: 'https://domain.com',
      MONGO_URL: 'mongodb://mongodb:27017/app1',
    },

    docker: {
      image: 'abernix/meteord:node-8.4.0-base',
      args: [
        '--link=mongodb:mongodb'
      ]
    },

    enableUploadProgressBar: true
  },

  proxy: {
    domains: 'domain.com,www.domain.com',
    ssl: {
      letsEncryptEmail: 'support@domain.com',
      forceSSL: true
    }
  }
};

I’ve no idea how to troubleshooting this problem.
Really appreciate your helps.
Thanks!

Another information, I checked mup docker ps then there’s only first app running. So I tried to set the port for app2, but mup said “app.env.PORT can not be set when using proxy”

Finally found the solution. It because of the plugin lookback:seo that I added. Removing it fixed the problem.