• 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. dj ramc

    Resolved [alert] 32414#0: socket() failed (24: Too many open files) while connecting to upstream

    I edited the nginx.conf file. and We'll see if it helps.
  2. dj ramc

    Issue nodejs ng universal only rootpage doesn't render server side

    It's a little late but I use PM2 with an NGINX proxy server.
  3. dj ramc

    Resolved [alert] 32414#0: socket() failed (24: Too many open files) while connecting to upstream

    same here and @IgorG solution doesnt helped
  4. dj ramc

    Question aliasdomain.com to www.aliasdomain.com

    I've done this with adding nginx code below in Additional nginx directives
  5. dj ramc

    Question aliasdomain.com to www.aliasdomain.com

    I've been trying to get this working for a while now, but without success. I'm trying to forward aliasdomain.com to www.aliasdomain.com. Forwarding of domain.com to www.domain.com is already working. Any suggestions are welcome. Thanks in advance.
  6. dj ramc

    Question nginx reverse proxy directive for "location /" for specific domain only

    any update ?
  7. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    done the latest update for plesk is installed
  8. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    thanks alot for support. i fixed db errors by reinstalling mariadb and imported backup. now mariadb errors are gone this night i'll try upgrade plesk
  9. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    hello people this error is not been fixed yet any sugestions? thanks by advance
  10. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    Hi IgorG checked that file it's already mysql the owner
  11. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

  12. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    my second server won't update either .
  13. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    could i see what is installed from this repo ?
  14. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    thank you now plesk is upgraded to 18.0.41
  15. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

    is that a problem ? do i need this custom repo ? what if i delete this repo file and yum update ? Thank you
  16. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

  17. dj ramc

    Resolved error plesk upgrade from 18.0.39 to 18.0.41

  18. dj ramc

    Question install plesk with existing psa database

  19. dj ramc

    Question install plesk with existing psa database

  20. dj ramc

    Question install plesk with existing psa database

    Hi Peter i have installed new fresh plesk and os like you mentioned . now i want to restore from my backup files . could you explain me wich files need to be uploaded to new server after then i will follow this https://support.plesk.com/hc/en-us/articles/115002362654 is that the correct way...
Back
Top