• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Plesk 12.0.18 & Plesk Mobile Manager 1.5 Internal Error

J.Wick

Regular Pleskian
Currently tried everything to get Mobile Manager working and having no luck. I'm getting an internal error every time I try to setup the connection. I worked last week, have no idea why it decided to stop.

I have exhausted http://kb.odin.com/en/112730

There are no entries in the log file to indicate the a problem other than a missing apple-touch-icon file and
2015/09/28 13:39:19 [warn] 28143#0: duplicate value "TLSv1.1" in /etc/sw-cp-server/conf.d/pci-compliance.conf:2

When I visit https://Server_IP_Address:8443/enterprise/mobile-manager/ all I get is a blank page, both on the phone and desktop browser.

I have deleted the Mobile Manager Server from Plesk, re-cycled Plesk, re-installed the extension, deleted the settings on the mobile app and re-entered all settings and reproduce the same error every time.

What's my next course of action?


 
Hi SpyderZ,

first of all, even that it is only a warning, please delete the double entry "TLSv1.1" at: "/etc/sw-cp-server/conf.d/pci-compliance.conf". Please keep in mind, that other configuration files at "/etc/sw-cp-server/conf.d/*", or "/etc/sw-cp-server/*" may already contain such restrictions, which may as well cause such issues.

Even that I have no proof at the moment, because of missing log - files ( and depending configuration files ... and in your case webserver configuration templates as well?!? ), I'm pretty sure, that you were configuring your "security" definitions too strict now ( this conclusion is done, because of reading all your previous posts of PCI - compliance settings). I would suggest to stick with the standard settings, if you are not really aware of the causes, that your setting might have. Especially because of missing configuration files for investigations, regarding to your made changes, it is nearly impossible to suggest something, because we do not know, what and were you changed settings.
 
Back
Top