• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by LarsK

  1. L

    Question Redirect customerdomain.com:8443 to serverhostname:8443

    When a customer has a problem with a website, we normally would go to customerdomain.com:2222 (2222 because of directadmin) and it would redirect us to the serverhostname:2222. This way we could quickly find out on which server the customer website is located. And we would be on the login page...
  2. L

    Issue Website shows plesk login page after migration via Plesk Migrator extension

    Lately all websites that I migrate via the Plesk Migrator extension show the Plesk login page instead of the website content. However, this gets fixed when I do a Re-Sync via the Plesk Migrator. OS: CentOS Kernel (cloudlinux): 4.18.0-147.8.1.el7h.lve Plesk: Version 18.0.28 Update #2 Plesk...
  3. L

    Question www redirect SSL warning, www not included in SSL cert

    Problem: Some of our clients don't include the www subdomain in the SSL cert because of the extra cost. The problem this creates is that if users go to www.domain.com they will get a SSL warning from the browser, after that they will get redirected to domain.com. Question: Is there a way to use...
  4. L

    Resolved Change webmail url from webmail.domain.com to domain.com/webmail

    Hi, I would like to make the webmail accessible via domain.com/webmail. A lot of our customers have a simple SSL certificate (no added subdomains and no wildcard) which means I cannot secure webmail.domain.com. We also used to have the webmail accessible via domain.com/webmail on our...
  5. L

    Issue Cloudlinux "LVE Manager" displayed as "[[LVE Manager]]"

    I just finished installing a new Plesk 18.0.21 server with imunify360 and cloudlinux. After the installation of cloudlinux the "LVE Manager" was displayed as "[[LVE Manager]]". Normally this wouldn't be a problem for me if it was just on one server. But i'm going to use this installation as a...
  6. L

    Resolved Backup was created, altough some minor issues occurred.

    Hello everyone, Since a few days i get the following message on the back-up page: The backup Nov 18, 2019 12:12 AM was created and can be restored, although some minor issues occurred. Download the log file View the log Close this message This happens every time a backup has run so when i...
  7. L

    Question Only IPv4 added to hosting package by default, IPv6 needs to be added manually

    Hello, It seems that all the hosting packages I add will only get the IPv4 of the server assigned. Why is the IPv6 not added by default? Can this be done via the API maybe?
  8. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    Problem was resolved by plesk support, this is what they found:
  9. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    Status update for people in the same boat. I got the folowing response from Plesk Support yesterday Progress!
  10. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    Please create your own thread instead of hijacking mine, i do not have the same problem and i do not have an answer for you. Regarding to my issue, still not fixed.
  11. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    Nope, still the exact same error: What is do notice is that the first time I ran it it said that there is 1 package required for the product to function properly. After the yum update is says: Preparing Your System for Product Installation...
  12. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    Running plesk daily gives me the following errors: [ root@titan ~]# plesk daily [2019-09-27 08:47:32.419] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/f2bmng' '--get-stats'] with exit code [1] [2019-09-27 08:47:32.422] ERR [panel] f2bmng failed: ERROR:__main__:Failed to get...
  13. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    I just got a reply from my service provider (TransIP). They contacted Plesk support for me. Plesk support can't replicate out problem on their test systems so they need SSH access to my server, which is a problem for me. Is one of you able to contact Plesk support and give them SSH access to...
  14. L

    Resolved Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)

    I can't, our license was supplied by TransIP. I contacted them but it's pretty useless that i have to contact them and they just pass on the question to Plesk support. Is there any way that I could contact plesk support directly?
  15. L

    Important Plesk Obsidian Releases

    I had some problems with the upgrade from RC4 to RTM. Made a thread: Issue - Unable to update Plesk Obsidian 18.0.18 to 18.0.19 (RTM)
Back
Top