• 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

Search results

  1. P

    Question problem with ipv6 address

    Argh, I'm so stupid. I deleted every DNS records on the domains but did not stop BIND. I did that now. After that, I just clicked OK on the webhosting access dialog of one of the two domains stil having an IPv6 address. After that, the 2 disappeared and I could delete the IPv6. Thank you so much...
  2. P

    Question problem with ipv6 address

    No, DNS Tool is not used.
  3. P

    Question problem with ipv6 address

    Ok, thanks so far, but I'm not successful yet. I now deinstalled nginx, now every domain is fine again except the two having the IPv6 address. On these two, I tried a plesk repair web domain.com, but without sucess: root@server:~# plesk repair web domain.net Checking web server configuration...
  4. P

    Question problem with ipv6 address

    Yes, several times.
  5. P

    Question problem with ipv6 address

    Thank you so much for your patience. Please find attached the screenshots.
  6. P

    Question problem with ipv6 address

    Yeah, that is basically my problem, I have no IPv6 option anywhere in Plesk UI. Under IP address, I only see my IPv4 address which is selected.
  7. P

    Question problem with ipv6 address

    Great idea, and how can I do that?
  8. P

    Question problem with ipv6 address

    Does not change anything, I already tried that (and now again).
  9. P

    Question problem with ipv6 address

    Hej guys, I've some troubles with an ipv6 address that no longer exists: root@server:/etc/nginx# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo...
  10. P

    Issue cause to 18.0.30 Obsidian fails with DB failure

    Seems to work now. I deleted some unnecessary DNS settings and after that, the upgrade succeeded, still with yome errors regarding the DB structure. After upgrade, I could not open phpmyadmin out of plesk, the known db structure failure coming up. After a plesk repair db -y everything seems to...
  11. P

    Issue cause to 18.0.30 Obsidian fails with DB failure

    I know, but according to How to perform dist-upgrade procedure on Linux server with Plesk?, upgrading ubuntu is not yet supported. Therefore, I want to upgrade at least Plesk to the current version.
  12. P

    Issue cause to 18.0.30 Obsidian fails with DB failure

    Hej all, thanks a lot, I updated roundcube successfuly now, problem was a wrong php-mysql-package. But nevertheless, the upgrade to plesk 18.0.30 fails with this error in the post installation steps regarding the DatabaseServers table, where the column fork does not exist, indeed. I do find some...
  13. P

    Issue cause to 18.0.30 Obsidian fails with DB failure

    Hej Igor, hej all, thanks for your quick help, I just tried plesk repair installation and got: root@server:/# plesk repair installation Reconfiguring the Plesk installation Started bootstrapper repair procedure. This may take a while. Certain actions may be skipped if not applicable...
  14. P

    Issue cause to 18.0.30 Obsidian fails with DB failure

    Hi all, I tried to upgrade my 17.8.11 to Obsidian, different versions. Latest try was to migrate to 18.0.30 , it fails with ERROR: Upgrade step 2018-09-04-04-45-30_DetectMysqlForkTypes.php failed with code 1 and output: [2020-10-06 22:55:32.552] ERR [panel] DB query failed: SQLSTATE[42S22]...
Back
Top