• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Recent content by Johan_K

  1. J

    Issue Plesk 12.5.30 suddenly won't show login screen

    Hi again, I put the repair command in the background so it keeps running, and it is almost running for 48 hours now. I guess thats too long and there must be something wrong? Would like to now why it's taking so long. (there's no output in the terminal while running the command, and if i'm...
  2. J

    Issue Plesk 12.5.30 suddenly won't show login screen

    Hi, thanks for your suggestions. I stopped NGINX but I keep getting the same message during login. (no login screen) I made a backup and tried the repair utitility, but it's running for about 12 hours now without any output. ("plesk repair all") Does it create a log file?
  3. J

    Issue Plesk 12.5.30 suddenly won't show login screen

    Hello, thanks for your reply. I restarted the server but it didn't solve the problem. I ran the auto installer and it seems to hang. When I look into "/tmp/autoinstaller3.log" I see: [2017-01-12 18:26:36.603036] Use package source...
  4. J

    Issue Plesk 12.5.30 suddenly won't show login screen

    Last week I got this message when I tried to login at Plesk admin panel at https://<domainname>:8443 "502 Bad Gateway" nginx As far as I'm aware of, the server was not recently updated. (I checked the yum update log) I searched for help articles and found this one and followed the...
See more
Back
Top