• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. Talistech

    Resolved Backups failing since a couple days: Unable to run the backup agent

    Posting this for future reference; Solved the issue. After all I still had a corrupt table. I restarted the database with innodb_force_recovery = 4. After that I did a "plesk repair db" and I saw the following in my journalctl: Oct 25 19:05:21 [REDACTED] mariadbd[2401316]: 2024-10-25 19:05:21...
  2. Talistech

    Resolved Backups failing since a couple days: Unable to run the backup agent

    Hi fellow Pleskians, My backups recently started failing a couple days ago. This is the error I am getting: Upon checking the journalctl logs while trying to take a backup, I see that it restarts every couple minutes because it crashes itself. You cna find the log trace on the bottom. As far...
  3. Talistech

    Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

    I was wrong. Appearently this is by design. See Issue - Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.
  4. Talistech

    Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

    You're totally right. I was a little too fast with creating this ticket. Thanks for the help!
  5. Talistech

    Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

    Also posted in Reports because I truly believe this is a bug.
  6. Talistech

    Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

    Username: TITLE Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist. PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Server operating system version Ubuntu 22.04.4 LTS Plesk version and microupdate number Plesk Obsidian 18.0.62 Update #2...
  7. Talistech

    Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

    Hi there, I have found a bug while updating DNS records via the CLI. You are able to update the dns records to the "internal" ip address while using NAT. But you cannot use the external/public address because Plesk thinks that that address does not exist. root@server:~# plesk bin subscription...
  8. Talistech

    Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP

    Great! Thanks for following up on this @Kaspar@Plesk! Have a nice evening :-)
  9. Talistech

    Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP

    Look at the difference clicking Reset to default and after. Notice the ip's startign with 178(public) and 10 (internal).
  10. Talistech

    Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP

    Upon trying to reproduce it I have found that my issue is slightly different than I have said earlier. -> Creating a new subdomain gets created with the correct ip address under the main domains DNS records. But what is really going wrong is: -> What is happening on your test server when you...
  11. Talistech

    Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP

    Hi Kaspar, thanks for your reply. 1 internal IP (which is SNAT and DNAT'ed via my firewall) and this same internal IP has a public IP set via Settings -> IP Addresses. Let me provide you some screenshots and another test so I can reproduce it.
  12. Talistech

    Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP

    Hi fellow Pleskians, One of my Plesk servers is running with a NAT configuration. Everything seems to be working fine for now but there is only 1 small issue and I'm nut sure if it's a bug or not. Lets say for example my internal address is 10.10.10.1 and my public address is 99.99.99.99. All...
  13. Talistech

    Question Logging rewrites

    Are you logged in as root? Or another user? Try: cd /var/www/vhosts/[your-domain]/
  14. Talistech

    Resolved fetch_url command suddenly broken in chrooted environment

    Yes that fixes it but it's not the correct fix. Changing it to /bin/bash was also working but that takes the user out of the chrooted environment. See my reply top of here. Seems fixed for now, thanks
  15. Talistech

    Resolved fetch_url command suddenly broken in chrooted environment

    I just got it fixed, I don't know where I went wrong but some other commands were also missing, such as "ls" and "mktemp". curl -o update-chroot.sh https://raw.githubusercontent.com/plesk/kb-scripts/master/update-chroot/update-chroot.sh chmod 700 update-chroot.sh ./update-chroot.sh --add...
  16. Talistech

    Resolved fetch_url command suddenly broken in chrooted environment

    Sadly no parameters or unusual urls :/ root@[REDACTED]:~# cat /var/spool/cron/crontabs/[REDACTED] # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/opt/psa/tmp/sssxmShj8 installed on Fri Aug 4 09:19:31 2023) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)...
  17. Talistech

    Resolved fetch_url command suddenly broken in chrooted environment

    Hi fellow Pleskians, I broke the fetch_url command in a chrooted environment for only 1 specific user. I'm getting the following mail sent by failed cron jobs: -: line 1: /opt/psa/admin/sbin/fetch_url: No such file or directory Running/fetching the urls via the web interface works well, no...
  18. Talistech

    Question Do not forward spam emails to external mailbox

    cat /var/log/maillog Jun 9 09:31:15 **** psa-pc-remote[3985528]: 462D61C1208: from=<****@****.com> to=<****@****.io> Jun 9 09:31:15 **** postfix/cleanup[1142774]: 462D61C1208: discard: header Subject: SPAM from localhost[127.0.0.1]; from=<****@****.com> to=<****@****.io> proto=ESMTP...
  19. Talistech

    Question Do not forward spam emails to external mailbox

    For anyone else having this issue, I resolved my isssue it with Postfix header checks. Since all spam mails are marked with "****SPAM*****" by Spamassassin when they're incoming, I'm simly dropping all outgoing messagedd with "SPAM" in the content. # Install postfix-pcre sudo apt install...
  20. Talistech

    Question Do not forward spam emails to external mailbox

    Thank you, I'll give that a try.
Back
Top