• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 114785, created on Sep 18, 2012, last review on May 10, 2014

  • Applies to:
  • Plesk 11.x for Linux
  • Plesk 10.x for Linux
  • Plesk 11.x for Windows
  • Plesk 10.x for Windows


This article provides the log and configuration file locations for Parallels Panel Server Manager and Parallels Panel Server Monitor, on the Parallels Plesk Panel side.

Parallels Panel Server Manager and Parallels Panel Server Monitor are considered separate applications. They use different files to store configuration settings and logs. File names and their purposes are presented in the table below:

  Description Manager Monitor
Log file Contains logging of the interactions between the mobile application and Parallels Plesk Panel server MobileConnector.log MobileConnector-Monitor.log
Configuration file Contains internal connection parameters: protocol, database, log level, etc. config.json monitor-config.json
SQLite database Contains mobile application settings MobileConnector.sqlite MobileConnector-Monitor.sqlite

These files are all located in the same directory. The directory's location may vary depending on the mobile application and the Parallels Plesk Panel version.
Since version 1.2, Parallels Panel Server Manager uses the Plesk Mobile module to connect to Parallels Plesk Panel version 11.x and higher versions.

  Parallels Plesk Panel 10.4 Parallels Plesk Panel 11.x
Monitor 1.0
Manager 1.0
Linux: /usr/local/psa/tmp/
Windows: %plesk_dir%/tmp/
Linux: /usr/local/psa/tmp/
Windows: %plesk_dir%/tmp/
Monitor 1.1
Manager 1.1
Linux: /usr/local/psa/tmp/
Windows: %plesk_dir%/tmp/
Linux: /usr/local/psa/tmp/
Windows: %plesk_dir%/tmp/
Manager 1.2 Linux: /usr/local/psa/tmp/
Windows: %plesk_dir%/tmp/
Linux: /usr/local/psa/var/modules/plesk-mobile/
Windows: %plesk_dir%/tmp/var/modules/plesk-mobile/

bd7fc88cf1b01f097749ae6f87272128 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 dd0611b6086474193d9bf78e2b293040 29d1e90fd304f01e6420fbe60f66f838 c796c01d6951fa24ed54c7f1111667c6 0a53c5a9ca65a74d37ef5c5eaeb55d7f 0efe2234e2ce513f2186f26c68447702

Email subscription for changes to this article
Save as PDF