• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Search results

  1. M

    Resolved inet:localhost:12301: Connection refused

    All seems to work normally now. I Thought that unnecessary configurations were removed from onyx during upgrade but i was wrong. Thank you for your help :)
  2. M

    Resolved inet:localhost:12301: Connection refused

    I did not remember very well why i used that port.. i think i did this configuration for pre-onyx DKIM.. Should i have to remove it manually?
  3. M

    Resolved inet:localhost:12301: Connection refused

    Hi to all, can anyone help me?
  4. M

    Resolved inet:localhost:12301: Connection refused

    Goodmorning to all, I recently upgraded my server from Ubuntu 14.04 LTS to 16.04 LTS and from then i got this error in my maillog postfix/smtpd[17143]: warning: connect to Milter service inet:localhost:12301: Connection refused I tought that was OpenDKIM Fault, but it's perfectly working and i...
  5. M

    Resolved HTTP Keep-Alive not working on CSS and X-Powered-By not unsettable

    Hi Dukemaster, I think my problems with keep-alive are only on benchmark 'cause in Google Network Console it seems to work like a charm. I've also enabled HTTP2 protocol wich is helping me a lot on performance thanks to parallels load and lighter headers. Regarding "X-Powered-By", i've been...
  6. M

    Resolved HTTP Keep-Alive not working on CSS and X-Powered-By not unsettable

    I'm still fighting with this problem... can anyone help me?:(
  7. M

    Question Blocking access to mail from external ip

    Thank you for your help but it's not working the way i need it to work... It effectively blocks all connection from clients that are out of the list but i'm still able to login on webmail service... can i block all type of login to the mail server? included those on webmail..
  8. M

    Question Blocking access to mail from external ip

    Goodmorning to all, I've to allow login only on three ip addresses for security reasons, is it possible to block other ip from login to my mail server? I'm using Postfix/Dovecot on my server. Thanks in advance for any help, Domenico
  9. M

    Resolved HTTP Keep-Alive not working on CSS and X-Powered-By not unsettable

    Goodmorning to all, today i've got a problem on my Linux server with Plesk Onyx installed, version 17.5.3 #18: i've tried to check if keep-alive for https connection is working correctly but it seems it doesn't... If i check it with Google Chrome i can't see the connection header, so i tried...
Back
Top