• 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. Pascal_Netenvie

    Resolved Cron ASL errors started today

    Oh ok, thanks. **** i have to revert that on 17 servers now :p
  2. Pascal_Netenvie

    Resolved Cron ASL errors started today

    Ok but now each morning i get that : /etc/cron.daily/50plesk-daily: stty: /dev/?: Aucun fichier ou dossier de ce type TERM environment variable not set. Configuring Atomic Secured Linux (ASL) 5.0-5248 for myserver.com.
  3. Pascal_Netenvie

    Resolved Cron ASL errors started today

    Problem solved. Thx.
  4. Pascal_Netenvie

    Resolved Cron ASL errors started today

    Same here on all servers since this morning ...
  5. Pascal_Netenvie

    Resolved Suddenly getting ASL errors today

    Hello, Same here ... Since this morning i have this error on all servers under plask 17.5 ... /etc/cron.hourly/asl: Error: ASL has not been configured run-parts: /etc/cron.hourly/asl exited with return code 1
  6. Pascal_Netenvie

    Resolved Errors AH01067 and AH01075

    OK. I searched on doc but not on support ... Too much places ... There would be an unique place to search all databases ... Solution seems to be here : A website is not accessible with "504 Gateway Time-out": The timeout specified has expired: [client 203.0.113.2:54693] AH01075: Error...
  7. Pascal_Netenvie

    Resolved Errors AH01067 and AH01075

    Hi, On a new server (Debian 9.4 + Plesk 17.8) i have these 2 errors in log when trying to run a script. AH01067: Failed to read FastCGI header ... then (104)Connection reset by peer: AH01075: Error dispatching request to : , referer: ... Is there a way to solve this problem ? Cheers !
  8. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    It works but we have to setup some exceptions and disables groups of rules not for linux or mysql.
  9. Pascal_Netenvie

    Issue Plesk Migration Fail to connect servers together

    And you have to be sure root login is enable on source server ...
  10. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    I tried your fix for Debian 9 but, for Comodo rules credentials are needed, and if i try Atomic basic i have now this error :
  11. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    I can't submit demand to support center cause my licence is from a reseller ... So if you have any news about this problem ... I will try the fix .
  12. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    Ye, sorry, you're right ... I will have a look on this ...
  13. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    For this last error it's on servers under Debian 8 !! Only the first message is about a server running Debian 9 ...
  14. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    Perhaps someone from Plesk Support could alert them ...
  15. Pascal_Netenvie

    Resolved Add/remove component bug on access

    Strange cause i see Installer and he run under port 8447 too. Whatever i added a rule for port 8447 in firewall and now it run ok. Thanks.
  16. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    Yes now we have this on many servers :
  17. Pascal_Netenvie

    Resolved Modsecurity failed to retrieve Atomic basic set on Debian 9

    And i see this error on update sources : Err:16 Atomicorp stretch/main i386 Packages 404 Not Found [IP: 173.203.184.213 80]
  18. Pascal_Netenvie

    Resolved Add/remove component bug on access

    Hi, On new server under Debian 9 and Plesk 17.8.11 i try to access Add/Remove component in Plesk Installer but it run endlessly and never display the screen ... Or i have an error message from browser saying page take too long to display ... Is there some problems with Debian 9 ? Some idea ?
Back
Top