• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Search results

  1. yabado

    Issue Domain PHP "Performance and security settings" not used?

    Yes Igor, I know all this. It is not working.
  2. yabado

    Issue Domain PHP "Performance and security settings" not used?

    The domain's php.ini has the updated values, but the server is not using them. Perhaps plesk is not restarting things to pick up the new config correctly?
  3. yabado

    Issue Domain PHP "Performance and security settings" not used?

    I load up phpinfo() on a page to verify changes, yet they remain the defaults. I also increase upload_max_filesize to 16MB, yet I am only able to upload files of 2MB or less.
  4. yabado

    Issue Domain PHP "Performance and security settings" not used?

    I have set several custom PHP settings, hit Apply ( then OK ) and the custom settings are never applied to the domain. Anyone know how to fix this? CloudLinux Server 6.10 (Vladimir Lyakhov)‬ProductPlesk Onyx Version 17.8.11 Update #78, last updated on Dec 23, 2019 03:52 AM
  5. yabado

    Resolved Old Email Clients and Obsidian?

    Anyone from Plesk care to reply?
  6. 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...
  7. 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
  8. 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
  9. yabado

    Issue Cannot Edit PHP Setting on ALL domains?

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

    Issue Cannot Edit PHP Setting on ALL domains?

    Did a reboot and did not fix things.
  11. 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...
  12. 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?
  13. 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.
  14. 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
  15. 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 :-/
  16. 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 ?
  17. 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...
  18. 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...
Back
Top