• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Recent content by theunknownstuntman

  1. T

    Question Small Plesk Errors in the logs - Config Related - Local or Plesk or OS?

    Strange though "The error in Plesk: ERR [panel] SQLSTATE[HY000] [2002] No such file or directory, Can't connect to local MySQL server through socket" in the Log Browser regarding the "Plesk", "Panel", I started with is still visible... :rolleyes:
  2. T

    Question Small Plesk Errors in the logs - Config Related - Local or Plesk or OS?

    Thank you for your answe @Sebahat.hadzhi . At this time mysql.service was still running (mysql-server-8.0 to be precise). I decided after taking a snapshot for the server to upgrade to Ubuntu 22.0x LTS, as explained in your upgrade-guide. I ran in the same error, as mentioned above, and was...
  3. T

    Question Small Plesk Errors in the logs - Config Related - Local or Plesk or OS?

    Thanks for your detailed answer. I decided to upgrade the server and with a few problems I was able to finish this. See below.
  4. T

    Question Small Plesk Errors in the logs - Config Related - Local or Plesk or OS?

    Regarding The error in Plesk: ERR [panel] SQLSTATE[HY000] [2002] No such file or directory, Can't connect to local MySQL server through socket it is strange, that I can not find any reference to "mysql.sock" in any mentioned files, that are mentioned in the "resolution" section. There is a...
  5. T

    Question Small Plesk Errors in the logs - Config Related - Local or Plesk or OS?

    I happen to have the same error, after upgrading from Ubuntu 18.0x LTS to 20.0x LTS. Plesk has not been upgraded as part of the Ubuntu upgrade. I see this error in Plesks Logbrowser, for "Panel". It happens after I login to Plesk, which works fine, or when I restart the mysql.service. Plesk...
  6. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Thank you for your answer. Could you mark the topic as resolved? Might help others, having the same problems.
  7. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Moving mv plesk-ext-site-import.list out of the the /etc/apt/sources.list.d/ directory, fixed the issue. I wonder how this can happen. In my opinion this is a bug in Plesk. :rolleyes:
  8. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    This command does not work, because of the mentioned error. Synchronizing the Debian APT package index files... E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/ focal: /etc/apt/keyrings/plesk-ext-panel-migrator.gpg !=...
  9. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Thank you for your help. I can not identify any duplicates on /etc/apt/sources.list.d focal-icinga.list imunify360.list imunify-rollout-bypass.list.disabled imunify-rollout.list imunify-rollout.list.save kcare.list kcare.list.save plesk-ext-docker.list plesk-ext-docker.list.save...
  10. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    I thought I could fix the issue by updating Plesk to Version 18.0.67 Update #3. Unfortunately I can not open https://plesk.server.domain:8447, when I open Tools & Settings, "Updates" in Plesk :(
  11. T

    Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/

    Hi all, since today I receive the following error message, when I run, for example, the command "apt list exim". As I did not modify anything on the server in the last days and no changes where applied as part of "unattended-upgrades", I am a bit clueless, where this error comes from and how...
  12. T

    Forwarded to devs Bug in 360 monitoring "status" panel

    Thanks for the update and confirming, that it is a bug on your side and that it's being worked on. :)
  13. T

    Forwarded to devs Bug in 360 monitoring "status" panel

    Hi, I am using plesk 360 monitoring. Together with this service I use the subdomain "status" to use a short overview, which can be used to view the uptime per day per domain. In this view I have found a bug in the details page of a monitored domain. I would be happy to report it somewhere...
  14. T

    Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.

    With the help of the support I could fix this now. The solution was: - ssh to the affected server - remove or comment out the grafana repository in /etc/apt/sources.list - run the following commands: -- apt-get purge grafana -- plesk bin extension -u monitoring - login to Plesk admin panel...
Back
Top