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

    Issue Let's Encrypt Certificate Expiration note (Mail cert)

    Hi, I'm getting a daily expiration mail from Let's Encrypt for a while about one Mailserver certificate that is about to expire in couple of days from now. I've been digging a bit but cannot find the cause. As I've read the cert should auto-renew. I've configured logging for the Lets Encrypt...
  2. M

    Issue Not receiving my AWS credits

    Hi Lukas, 1.) I see I requested that too early as migration is not finished. But I do have another question: My in-transit server is a managed VServer. I do have access to the licence code, hence I paid for it within the server fee. But it's not my own licence, I didn't buy it personally. Am I...
  3. M

    Issue Not receiving my AWS credits

    I created a web server on AWS. I installed Plesk with a Trial licence. I bought a licence. All within the advertised time period. I'm in the process of migrating all my webhosting services to AWS. I've contacted Plesk Sales regarding the 500 AWS credits, They said "contact AWS Sales". I've...
  4. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    Ok, just tested it, setting up the hostname in Plesk > Tools & Settings > Server Settings and rebooting afterwards does not solve the issue. The error page still is https://ip-xx-xx-xx/... (that is my hostname, meaning the "computer name", not the hostname set in Plesk)
  5. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    @UFHH01 Following the instruction from Peter results in the error documented here: Can't change hostname or FQDN on Ubuntu 14.04 LEMP droplet | DigitalOcean There in the comments section also the new solution was suggested. Yes, I knew already that the command hostname exists. I just don't...
  6. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    Anyway huge thanks to you, Peter for your help! Really appreciate it. :) At least I now have clarity what's going on. Maybe I'll make a feature request so this can be configured individually within Plesk. I've just checked my other Servers with Plesk at different hosters, this problem exists...
  7. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    I tried to change the hostname like Peter suggested, but sadly this doesn't work. On Ubuntu 16.04 it seems the hostname needs to be changed using hostnamectl set-hostname Also I'm still not sure this is the desired solution. I've read up on the issue a bit more, it seems recently there was a...
  8. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    Thanks to Peter's hint I also checked the hostname via uname -n on the shell. The hostname is indeed this "ip-xx-xx-xx" that shows up in the url. I'm still not sure where to head. Renaming the host and giving it the domain name seems weird, not sure this is the solution.
  9. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    The content of that line is error_page 497 https://$hostname:$server_port$request_uri; No, I never modified any config files on this server, cause it's a pretty fresh install. I've toggled IP settings inside Plesk between dedicated and shared to see if it got anything to do with the issue...
  10. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    Yes, same domain (mydomain.com) is set here, too.
  11. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    Thanks, Peter. Yes, it contains my primary domain name.
  12. M

    Resolved mydomain:8443 redirects to https://ip-xx-xx-xx:8443

    Hi, I've got a webserver set up and running (Ubuntu 16.04 / Plesk 12.5). When I try to connect to Plesk like by typing into the browser mydomain.com:8443 I'm redirected to this: https://ip-xx-xx-xx-xx:8443 (internal IP of my server). That of course doesn't work. When I type in...
  13. M

    Resolved IMAP ./Sent instead of ./INBOX/Sent

    As it turned out, although Thunderbird was completely fine with the prefix setting in place, Outlook 2016 still wasn't able to copy mails to the Sent folder. This was the final solution: /etc/dovecot/conf.d/99-my-settings.conf namespace inbox { prefix = INBOX. mailbox Junk { special_use...
  14. M

    Resolved IMAP ./Sent instead of ./INBOX/Sent

    I solved this now by adding a new file to /etc/dovecot/conf.d with the content: namespace inbox { prefix = INBOX. } Not sure if this is the best solution however. Why isn't that the default setting of Plesk / Dovecot like on most commercial mail servers, gmail etc. What about updates of...
  15. M

    Resolved IMAP ./Sent instead of ./INBOX/Sent

    It's the same also for Drafts as I just found out. This is not very convenient, I'd really like to have it the other way.
  16. M

    Resolved IMAP ./Sent instead of ./INBOX/Sent

    Hi there, is it possible to configure IMAP on Plesk so mail clients don't struggle with copying mail to the sent folder using their default settings? Right now I have to explicitly configure every mail client to use ./INBOX/Sent. By default they try to use ./Sent, which works fine on my iMSCP...
  17. M

    Recover certificates from broken backup file

    Hi! I got a broken backup file, which I can succesfully extract those files from: .discovered -> contains 6 files with size 0kb clients -> the_domain -> all data seems present backup_file_sharing_12345.tgz backup_info_12345.xml backup_keyyxcasdfyv.key_12345.tgz backup_sb_server_12345.tgz...
  18. M

    Backup - corrupted tables (and other problems)

    Realized that Plesk doesn't use the user "root" anymore, but now it's using "admin", for the Panel as well as for MySQL http://kb.odin.com/de/1252 proposes to create the admin user if it's missing. Sadly the document seems dated. When I look into the PHP files, most things aren't written out but...
  19. M

    Backup - corrupted tables (and other problems)

    The journey continues.. Tonight I got an email: /etc/cron.daily/logrotate: error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log /var/log/mysql/error.log ' run-parts: /etc/cron.daily/logrotate exited with return code 1...
  20. M

    Backup - corrupted tables (and other problems)

    The previous problem was that mysql couldn't be stopped or restarted by /etc/init.d/mysql stop [fail] or any other attempts. After trying couple of solutions, it was rather simple as it could be stopped by upstart service mysql stop Getting closer to my first heart-attack I guess... Will try...
Back
Top