@zack949, could you report back after you got it solved? I think this is an interesting use case, which might be relevant for more people.

If you start your mirror with pm2 as suggested in documentation, then you can use commands like pm2 stop mm, pm2 restart mm, pm2 start mm to control your mirror.

I would make three different start scripts, e.g. mm1.sh, mm2.sh, and mm3.sh, where each one starts one specific instance. This is in line with @ninjabreadman’s suggestion to have three install directories.

I think there is also a zoom factor setting in config.js. Would this help?

See documentation on zoom config setting:

This allows to scale the mirror contents with a given zoom factor. The default value is 1.0

One syntax error I spot is in uptimeroot module. The curly bracket of config: is not matched. @Mykle1 writes there is even more which I don’t spot immediately.

  {
  	module: 'uptimerobot',
  	position: 'top_right',
        		config: {
  	useColors: true
  	api_key:'u505342-b40737465f0eada9bb8a',
  },

In such cases it is good to do a syntax check of the config. Please run npm check:config to do so. You’ll get a detailed statement of what is wrong where syntactically. The reference @Mykle1 gives above is a must read. It shows an example of what the syntax check provides you.

If a syntax check does not solve the issue, I’d comment out all modules but one and start the mirror. Use /* commented out module */ to make multi-line comments. If start-up works, you add the next module and restart. Repeat this until start-up fails which means you’ve found a(!) module that causes the issue. Please note that there might be more than one wrong module.

If you have the module, copy the desired config elsewhere and redo the module’s configuration with the simplest possible config, which you often find in the ReadMe file of the same module.

Good hunt.