• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Search results

  1. K

    Resolved Upgrade not working 8447 nothing listening

    Solved the problem. I remember I tried to upgrade to Debian 9 but this resultat in some kind of errors, so I restored the snapshot. Unfortunatly I did run the prepare script for plesk and took the snapshot after that. So the apt sources lists and autoinstaller got messed up. Fortunatly the...
  2. K

    Resolved Upgrade not working 8447 nothing listening

    Somehas has a slight Idea what to do next, what logs should I check? Is the error all about? ERROR: Not found source for system packages (release 8.11) in APT software sources configuration: Package files: 100 /var/lib/dpkg/status release a=now 500...
  3. K

    Resolved Upgrade not working 8447 nothing listening

    Hi. I search the board for the Issue and found some but nothing I found solved my Problem. :( It's about the Update & Upgrades Web Interface. OS: ‪Debian 8.11‬ Product: Plesk Onyx 17.8.11 Update #21 , last updated at Sept 23, 2018 03:33 PM -It's not about the Firewall or Fail2Ban I disabled...
  4. K

    Resolved Information on some packages might not be actual: inconsistencies were detected ...

    BIG THANKS! Had the same issue but related to drweb packages. After cleaning up and running your commands the message is gone.
  5. K

    Resolved ipv6 stops working after 10-15min

    Okay. So there were two things. 1) Testing with ping was blocked by PSA-Firewall 2) Testing with the Test-Website failed because of DHCP v4 auto config after 30 minutes. /etc/network/interfaces looks like: # The primary network interface auto eth0 iface eth0 inet dhcp post-up while ip -6...
  6. K

    Resolved ipv6 stops working after 10-15min

    I guessed it's about psa-firewall rules. But now after a while (like 30min) all ping request timed out. - I will investigate further. - Nothing in particular in the syslog
  7. K

    Resolved ipv6 stops working after 10-15min

    thanks for the info. I found some things in syslog but so fare nothing related (in this 15min timeframe) but I fixed some other minor issues. I contacted the hoster. They said I should try it within recovery console and than check if ipv6 is working.
  8. K

    Resolved ipv6 stops working after 10-15min

    Yeah I'm pretty basic - there are so many logs, that I don't know which one I should look into.
  9. K

    Resolved ipv6 stops working after 10-15min

    I want to fine tune some server and from my observation I run in a ipv6 Problem. If reboot the server everything works fine as it should but after 10-15min ipv6 stops working. I'm not sure if it has to do with the hosting/server, configuration or the webserver (apache, nginx) at all but why...
  10. K

    Resolved Postfix: mail for postmaster@domain loops back to myself [every other works]

    Thanks for the info. But there is one thing than I don't understand. I had a server running wit 11.5 and migrated to another server with onyx. In 11.5 postmaster@ worked fine. - any explainations to that situation?
  11. K

    Resolved Postfix: mail for postmaster@domain loops back to myself [every other works]

    I have some weird problem with just the alias "postmaster@domain" any other alias or Mail account (so far I tested) has no issues. The system is a VPS/Root Server with own Subdomain from the Hoster. This one I use to manage the Server with Plesk and so on. Kind of the generel Hostname as I have...
Back
Top