• 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 Svente04

  1. S

    Resolved named service stop randomly

    Hi, thank you. I just installed the update - fortunately everything still works after the update. Strange ...sometimes it happens - sometimes not... Anyway - good that we found a solution and know how to fix it :) Best regards Sven Stienemann
  2. S

    Resolved named service stop randomly

    @Alakide Did it work?
  3. S

    Resolved named service stop randomly

    Okay, at first backup your interfaces file: cp /etc/network/interfaces /etc/network/interfaces.bak Then edit the interfaces file and replace the content with: auto lo eth0 iface lo inet loopback allow-hotplug eth0 # activate dhcp iface eth0 inet dhcp # if this didn't work try the following...
  4. S

    Resolved named service stop randomly

    Please give me the output of the command 'ip a'
  5. S

    Resolved named service stop randomly

    Let's try :) I hope that your problem is the same I had (dhcp didn't work - means the network interfaces couldn't get the network configuration from IONOS network infrastructure. Synchronisation seems to happen every 12 hours). Ok, I need some information first: 1. What's the output of ~# ip a...
  6. S

    Resolved named service stop randomly

    @Alakide problem solved? I contacted my server provider (IONOS) and we were able to find a solution. In my case /etc/network/interfaces was misconfigured. Maybe I can help you.
  7. S

    Resolved named service stop randomly

    No, I don't use Plesk Email Security or Juggernaut Security and Firewall. Only Plesk Firewall. Just had to restart the server (again 12 hours)... Please tell me if you have news - will do the same of course. Greetings from Germany!
  8. S

    Resolved named service stop randomly

    @Alakide I have exactly the same problem since Saturday. Same Plesk version (I installed the latest Update 18.0.45 on Saturday), Same OS version. Since then the problem occures every 12 hours. Did you find a solution already?
Back
Top