Recent content by bernes_stainz

  1. B

    Issue Move Domain not working anymore -> Merge Subscription - The mail service is not installed in Plesk

    Hi, marked as "PPPM-15228 - will be fixed in the upcoming release - if you need a HOTFIX please contact Plesk Support (MoveDomain.php to be replaced with a fixed Version) cheers Michael
  2. B

    Issue Move Domain not working anymore -> Merge Subscription - The mail service is not installed in Plesk

    Hi, we have upgraded from 18.0.71 to 18.0.73 and now the following Issue: in 18.0.71 (and before -> this was working since years): plesk bin subscription --merge domain.tld -webspace-name webspacedomain.tld The subscription 'domain.tld' was merged with the subscription 'webspacedomain.tld'...
  3. B

    Question Apache/2.4.6 + httpd + php-cgi >1024

    Hi, how to fix: >> xxxx [fcgid:warn] xxxx mod_fcgid: too much processes, please increase FCGID_MAX_APPLICATION >> starting after more than 1024 php-cgi procs reached >> current workaround: kill -9 $(ps -eo comm,pid,etimes | awk '/^php-cgi/ {if ($3 > 300) { print $2}}') If you don`t move to...
  4. B

    Forwarded to devs Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

    thx a lot working!
  5. B

    Forwarded to devs Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

    18.0.38 -)
  6. B

    Forwarded to devs Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

    And because of this case we are not able to upgrade to 18.0.37 (PPPM-13048 - not marked as solved) - on the other side Plesk needs to think about the Support Policy because of this two newer releases now on (since 18.0.37 release 18.0.35 not supported anymore officially) ... cheers Michael
  7. B

    Forwarded to devs Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

    This is very annoying, currently we are not able to upgrade from 18.0.35 to a higher version due to this error because this is breaking all our E2E provisioning calls, please fix this ASAP (support mentioned that this is planned to be included in the next release 18.0.37)! cheers Michael
  8. B

    Forwarded to devs Cannot start event handler: Could not decode JSON, syntax error - malformed JSON.

    We have exactly the same Issue, please fix it ASAP! cheers
  9. B

    Resolved unable to update license key

    plesk daily -f UpdateKeys cheers Michael
  10. B

    Issue Random Connection Timeouts on all Websites

    If you would like to reduce longer HTTP waiting time, my suggestion is to change this to 1800 seconds and activation of graceful restart, apart from your MaxRequestWorkers problem cheers Bernes
  11. B

    Issue Random Connection Timeouts on all Websites

     Websites periodically are not available in Plesk: scoreboard is full, not at MaxRequestWorkers ++ I suppose you have already configured "graceful apache restart interval + interval e.g. 15 minutes" ( How to enable/disable Apache graceful restart in Plesk - will not solve it but less timeouts)...
  12. B

    Input Plesk DNS panel - "CAA 128 critical - flag" ->please Vote

    Hello, everyone which would like to have this feature implemented asap, please start voting: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/42946377-add-ability-to-set-up-128-value-for-flags-field-of Background: Section: Plesk DNS Settings for Domain Typ: CAA Name: @...
  13. B

    Question Best way to manage multiple Plesk server under same brand

    That is true, for the solution mentioned in the picture you need more dev engineering to achieve it with plesk -) cheers Michael
  14. B

    Question Best way to manage multiple Plesk server under same brand

    look here: Third-Party DNS Services or use an extension for ext ns searching github with keywords "plesk dns extension" cheers Michael
  15. B

    Resolved Plesk not usable since update to 18.0.34

    may different sessions for the same user active (plesk active sessions -> kill those & may service sw-cp-server + sw-engine + nginx restart), had similar troubles today but it was working afterwards, but I don't know if it is solved or not to 100% cheers Michael
See more
Back
Top