• 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

    Issue curl: (51) SSL: no alternative certificate subject name matches target host name 'URL'.

    und lieferst genausowenig Informationen. Außerdem schreibst Du in einem englischsprachigen Forum auf Deutsch. plesk -v pls.
  2. M

    Resolved Question to Plesk Backups

    Which steps did you follow?
  3. M

    Question Moving entire /var

    Mount the new /var somewhere, shutdown database, copy everything over (cp -ai or rsync -avP), reboot to change everything to the new location.
  4. M

    Question Plesk SMTP Server

    BTW, username is not enough, it has to be username@domain because there is no other way for a mailserver serving multiple domains to know which domain's account you want to access.
  5. M

    Issue Monitoring: All graphs empty, error="request handler error: [plugin.notRegistered] plugin not registered" in log

    This has been moved to plesk's new location (as above) during or after the dist upgrade, and then recently got the pinned key mentioned in another thread: deb [signed-by=/etc/apt/keyrings/plesk-ext-grafana.gpg] https://autoinstall.plesk.com/grafana/deb stable main The versions look fine, too...
  6. M

    Issue Nginx caching cause too much redirections

    ISTR there was something about nginx caching pages regardless of protocol, so if a page was first accessed with http, all the links and ressources of the cached page will be wrong when accessed with https, and vice versa ... no idea whether that's still a problem Having varnish between nginx and...
  7. M

    Issue Monitoring: All graphs empty, error="request handler error: [plugin.notRegistered] plugin not registered" in log

    Hi, in Monitoring I only see empty graphs: I first noticed this after upgrading from debian 9 to 10 and then to 11. There are no errors about grafana or monitoring logged in panel.log, only four [2023-04-13 00:00:01.829] 1920545:643729e1ca6ea ERR [panel] Unable to get key: Repository is not...
  8. M

    Resolved IMAP not working with STARTTLS or SSL/TLS Mailserver Dovecot Problem

    Just curious: Do pop3 or SMTP work with SSL?
  9. M

    Resolved Unable to get key: Repository is not opened

    Does this happen when registry.xml grows too big? It was 65768 bytes here (just over 64KB), and after removing and retrieving it has just 950 bytes.
  10. M

    Resolved SECURITY - attack surface : ports 7080 and 7081

    We proxy through nginx for a reason. Apache in general is slower than nginx, so attacking apache directly puts more load on the server. Best practice is that attack surface should be minimized. Services that don't need to listen on a public IP shouldn't. Apache might have different...
  11. M

    Resolved SECURITY - attack surface : ports 7080 and 7081

    Do you have the Plesk firewall active? It is not enabled by default. And apache2 itself binds to any IP as visible with netstat, while in /etc/apache2/plesk.conf.d/ip_default or vhosts the domains are bound to the IPs, which is completely unnecessary for domains cached by nginx. If no domain is...
  12. M

    Issue Brute Force Attack - Postfix - Mail

    I usually use grep "SASL LOGIN authentication failed" /var/log/mail.info |cut -f 5 -d ":"|sort|uniq -dc and null-route the more obnoxious ones with route add -net 194.55.224.0/24 lo if there are several in the same net or route add -host 195.133.40.157 lo for single hosts.
  13. M

    Issue Plesk migrator - authentication failed

    And ssh from a shell on the target server works too?
  14. M

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    Okay, I think I know what happened: Starting with the upgrade to 18.0.49, plesk explicitly pins the pgp key for the plesk repositories: add line 'deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.49_10759/ bullseye all' to temporary source list...
  15. M

    Resolved rel="canonical" response header is lost between Apache and Nginx proxy

    Does the request even reach apache or does the pagespeed module in nginx deliver this?
  16. M

    Question remove legacy authentication protocols, such as POP3 and IMAP

    well, taking that literally, I'd remove support for unencrypted POP3/IMAP and keep POP3S/IMAPS. Sending passwords over unencrypted connections is a huge security risk anyway, so the insurance companies aren't exactly wrong about this, they just could have worded that better ...
  17. M

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    And btw, plesk still doesn't show dist-upgrades. /admin/pum/updates-list says All packages are up-to-date Checked on Mar 30, 2023 10:47 AM but apt-get upgrade says The following packages have been kept back: linux-image-amd64
  18. M

    Resolved NO_PUBKEY BD11A6AA914BDF7E

    Well, it doesn't. It supports x86_64. There seems to be some confusion about arch vs. os_arch. This is not a debian key issue however, but a plesk pgp key issue, as all the repositories involved are plesk's. Maybe a leftover from the botched grafana key update? It seems plesk itself messed...
  19. M

    Question DNS for server hostname

    This is a problem with mxtoolbox. They expect mail to be on a subdomain even though there is nothing in the relevant RFCs that would support such an requirement.
  20. M

    Question SSL error when accessing mail.example.com

    Just curious, what are you expecting to access at https://mail.example.com/?
View older results
Back
Top