• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Search results

  1. M

    Resolved Clicking on "Use Built-in Monitoring" does not work

    This topic should marked as solved, but I can't find how to do it...
  2. M

    Resolved Clicking on "Use Built-in Monitoring" does not work

    Hi, thank you for your interest but I think the problem is now solved. I did : grep -i 'grafana' /var/log/plesk/panel.log but it returned empty. Interestingly, the 2 last strings of the file were : [2024-10-18 06:30:04.559] 4038138:6711e44c84d8b ERR [panel]...
  3. M

    Resolved Clicking on "Use Built-in Monitoring" does not work

    I removed the Grafana extension in the Extension panel. Then I clicked on the "Use the built-in monitoring" button. This time, there was a response, as the small icon started to turn. after a few seconds, the page reloaded, but stayed the same : the button was still here and Grafana was not...
  4. M

    Resolved Clicking on "Use Built-in Monitoring" does not work

    Hi, the only specific parameters are for the NGinx and are very straightforward : proxy_buffers 8 16k; proxy_buffer_size 32k; fastcgi_buffers 8 16k; fastcgi_buffer_size 32k; There are no big extension, as it is only a simple webservice server. The problem is with the Grafana extension, which has...
  5. M

    Resolved Clicking on "Use Built-in Monitoring" does not work

    Username: TITLE Clicking on "Use Built-in Monitoring" does not work PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian v18.0.63_build1800240902.09 / Debian 11.11 / Xeon E3-1230 v6 PROBLEM DESCRIPTION In the Monitoring page, clicking on the button "Use Built-in...
  6. M

    Resolved Inconsistencies were detected in the system's package manager database

    I removed the offending packet (which only exists for Active Directoy/Kerberos authentication) and all upgrades went smoothly. Conclusion : the MariaDB script should remove the mariadb-gssapi-server.x86_64 packet automatically when upgrading from 10.3 to 10.5.
  7. M

    Resolved Inconsistencies were detected in the system's package manager database

    Hi, I still have the problem presented above. As already said, I upgraded to MariaDB 10.5 without problem, but it seems that one of the previous 10.3 package is still here and stops any update because it has unmet depdendancies. Is the package mariadb-gssapi-server.x86_64, which seems to have no...
  8. M

    Resolved Inconsistencies were detected in the system's package manager database

    FYI, the tool I'm referring to is the one described here : Question - Try our new tool to upgrade your old MariaDB server from Plesk UI
  9. M

    Resolved Inconsistencies were detected in the system's package manager database

    Hi, it says : Problem: problem with installed package mariadb-gssapi-server-3:10.3.39-1.module_el8.8.0+3609+204d4ab0.x86_64 - nothing provides mariadb-server(x86-64) = 3:10.3.39-1.module_el8.8.0+3609+204d4ab0 needed by mariadb-gssapi-server-3:10.3.39-1.module_el8.8.0+3609+204d4ab0.x86_64 from...
  10. M

    Resolved Inconsistencies were detected in the system's package manager database

    Hi, this error message has already been answered many times for Debian, but my system is Almalinux 8.9 . So I can't just type dpkg --audit and find out... And I failed to find such a clean command with dnf. There are 53 system packages to upgrade, but they are the most important : grub...
Back
Top