Article ID: 112730, created on Nov 7, 2011, last review on Feb 5, 2016

  • Applies to:
  • Plesk 11.x for Linux
  • Plesk 10.4 for Linux/Unix
  • Plesk 11.x for Windows
  • Plesk 10.4 for Windows


This article describes troubleshooting steps for a connection failure from the mobile application to the Parallels Plesk Panel (PP) server.

Connection to the server from the mobile device fails with the error:
The internal error has occurred. Please contact our support services.


1. Make sure that you can access the PP control panel from the browser with the URL https://Server_IP_Address:8443.
Also check that you are able to see the page https://Server_IP_Address:8443/enterprise/mobile-manager/.

2.  Check that the access to the Administration Panel is not denied from the IP address
Home > Tools & Settings > Restrict Administrative Access

3. Review the mobile connector log file on the PP server. The log file location can be found at the article:

#114785  Log and configuration files location for Parallels Panel Server Manager

If the log file does not contain any error message, increase the log level using the instructions described in this article:

#112723 How to change log level for mobile connector

With the increased log level, initiate connection from the mobile device and check the error. Determine the reason of the connection failure by the error message.

If there is still no any error message, follow the further steps to re-add the PP server in the application.

4. Delete the server from the application and add it again. If the connection fails again, perform a complete re-registration as described in Step 5.

5. For a complete server re-registration, follow these steps:

- Delete the server from the application;
- Delete the mobile connector configuration file and the database file. At the following article you can find the exact file names and paths:
          #114785  Log and configuration files location for Parallels Panel Server Manager

- Add the server again.

6. If the application still fails to connect to the server, contact technical support by submitting a support request.

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

Email subscription for changes to this article
Save as PDF