• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. yabado

    Resolved Old Email Clients and Obsidian?

    Anyone from Plesk care to reply?
  2. yabado

    Resolved Old Email Clients and Obsidian?

    I have several clients that use older email clients to get/send their email. These old email apps still use older SSL protocols like SSL v.2/3 and TLS v.1 If I upgrade to Obsidian, will my clients have issues accessing their emails? My current setup... OS: ‪CloudLinux Server 6.10 (Vladimir...
  3. yabado

    Issue Cannot Edit PHP Setting on ALL domains?

    Happy to see a reply confirming this was a bug caused by recent update. After working all day to track down the problem, only wish the reply was made sooner
  4. yabado

    Issue Cannot Edit PHP Setting on ALL domains?

    Looks to be a bug from Plesk, not sure why no one has replied to this yet ¯\_(ツ)_/¯ It appears related to this issue, but I never changed any settings, only ran updates. PHP support cannot be enabled for one domain in Plesk when nginx service is stopped
  5. yabado

    Issue Cannot Edit PHP Setting on ALL domains?

    All of my domains now look like this?
  6. yabado

    Issue Cannot Edit PHP Setting on ALL domains?

    Did a reboot and did not fix things.
  7. yabado

    Issue Cannot Edit PHP Setting on ALL domains?

    Here is the message next to PHP version selector... PHP support cannot be enabled because current hosting configuration does not include any PHP versions available for this domain. I believe this bug was introduced within past 7 days. How can I fix this? Furthermore it has this as well...
  8. yabado

    Important Repair Kit Extension

    It is great how the new Repair Kit Extension can show which domain is using CPU and Memory, but what I really need is to see who is using high Bandwidth bursts. Is there any chance this can be added to Repair Kit in a future update?
  9. yabado

    Resolved were not created due to the errors in configuration templates: httpd: bad user name...

    Thanks brother. That fixed it up. Seems that errant user was attached to a bunch of webmail configs, across several domains? weird.
  10. yabado

    Resolved were not created due to the errors in configuration templates: httpd: bad user name...

    I removed the "second" instance from /etc/passwd manually Then why is Plesk showing the "bad name" error on my plesk panel dash? Image 2018-02-27 at 8.18.39 AM.png
  11. yabado

    Resolved were not created due to the errors in configuration templates: httpd: bad user name...

    Here is what I have: # grep sample /etc/passwd sample:x:10047:503::/var/www/vhosts/sample.com:/bin/false MariaDB [psa]> select * from sys_users where login='sample'; Empty set (0.00 sec) Now after running adduser, I have 2 instances of the same user :-/
  12. yabado

    Resolved were not created due to the errors in configuration templates: httpd: bad user name...

    On this.. # grep user1 /etc/passwd I do get a result BUT, when I search for user in sys_users it does not exist ?
  13. yabado

    Resolved were not created due to the errors in configuration templates: httpd: bad user name...

    Keep getting this error box in my panel home dashboard... New configuration files for the Apache web server were not created due to the errors in configuration templates: httpd: bad user name example . Detailed error descriptions were sent to you by email. Please resolve the issues and click...
  14. yabado

    Issue Emergency, cannot reboot cloudlinux / ec-2/onyx instance

    Here is the grub.conf file. This is the reason it will not boot. What should I change to make it work? I am desperate for any help. default 1 timeout=0 title CloudLinux Server (2.6.32-896.16.1.lve1.4.51.el6.x86_64.debug) root (hd0) kernel...
  15. yabado

    Issue Sidekick Pro not working in Onyx

    I went ahead a purchased the annual plan for Sidekickro. I had tested it before in years past and not worked ok then, now it does not work at all. When you "can" actually start a tutorial, the first page you come to results in nothing. It appears to start again, but a JS error is preventing it...
  16. yabado

    Important Skins and Color Schemes

    No. I am replying to the issue with the Wordpress and Security Advisor icons on "light" skins.
  17. yabado

    Important Skins and Color Schemes

    I have 3.6.1-62 installed, yet the problem still exists. I even tried to remove and reinstall. Still no dice.
  18. yabado

    Important Skins and Color Schemes

    The Wordpress and Security Advisor icons are white on Light skins, making them nearly invisible until they are selected. The reason is because they are static images and not part of the web-font used for the rest of the sidebar icons. Is there a fix in the works?
  19. yabado

    Issue Wordpress and Security Advisor icons always white?

    All the other nav icons are a web-font. Only the Wordpress and SA icons use image files that only account for darker themes. Should be an easy fix?
Back
Top