• 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!
  • 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. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    Migration delayed Hello, I'll delay this migration, since it looks like I'll have a lot of trouble. The "Counter" and "Script" modules problems are big enought for me. I can't check and repair every costumer's page with this modules after migration, and I'll not have a replacement for...
  2. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    RHEL4 + Plesk 8.1.0 + SB 2.1.3 then upgrade to 3.0.2, but still having problems Hello, I have managed to upgrade SB. The path that worked for me is: RHEL4 + Plesk 8.1.0 (installed with the autoinstaller script) + SB 2.1.3 (installed from the install package), then upgrade to 3.0.2...
  3. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    RHEL4 + Plesk 8.1.0 + SB 3.0.2 Hello, The last installation (RHEL4 + Plesk 8.1.0 + SB 3.0.2) is working fine. The DNS zone for the test server was not configured properly, so I was getting the default site, not SB's site. Thanks for the tip. I'm wondering if I can still "migrate" all...
  4. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    I just can't upgrade from 2.1.3 to 3.0.2 Hello, I have made more tests, and I just can't upgrade from 2.1.3 to 3.0.2. Now I'm doing tests in a RHEL4 server. I have installed and updated (up2date) the server. To solve some of the Plesk's auto-installer RPM dependency problems, I have...
  5. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    Ticket for this problem Hello, I already have a ticket opened for this problem, but I was informed that my free support period has ended and that I will have to pay $75 per incident to resolve this problem. The ticket ID is #250846. Thank you. Alexandre
  6. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    Same results with the Auto-Installer Hello, I have the same results installing everything with the autoinstaller. I have installed Plesk 7.5.4. Then I have upgraded SB and modules from 2.1.2 to 2.1.3 Everthing was working fine at this point. Then I have installed SB 3.0.2 using the...
  7. Z

    Upgrade from 2.1.3 to 3.0.2 does not work in RHEL3 with Plesk 7.5.4

    Hello, I'm trying to upgrade SB from version 2.1.3 to 3.0.2 but it is not working. I have a RHEL3 test system with all packages updated (with RH's up2date). I have installed Plesk 7.5.4 in this server, and it is also updated. Then I have installed SB 2.1.3 with all modules and templates...
  8. Z

    psarestore error: sh: - : invalid option

    Hello Everybody, Swsoft's support staff gave me a patch (bu-patches.tgz) that solved this problem. :) :) :)
  9. Z

    psarestore error: sh: - : invalid option

    You will not find the error message in the log file. You will only see this message if you watch the restore messages while it is running.
  10. Z

    psarestore error: sh: - : invalid option

    I'm not sure, but I think you can edit the restore.sh script file and correct the wrong command's syntax. It looks like that some shell command have it's syntax changed from RHEL3 to RHEL4, and the restore.sh file does not take that in account.
  11. Z

    psarestore error: sh: - : invalid option

    I think you can edit the restore.sh script and fix this syntax error, good luck. I will stay in RHEL 3 in the new server too.
  12. Z

    psarestore error: sh: - : invalid option

    I'm migrating from RHEL 3 to RHEL 4, and having the same problem. Both servers are updated, with version 7.5.4
View older results
Back
Top