Search results

"Failed to start plugin" logger=plugins.backend pluginId=grafana-simple-json-backend-datasource error="Incompatible API version with plugin. Plugin version: 1, Client versions: [2]"

Hi, I am facing the same problem after Grafana has been updated to the most recent version. "Failed to start plugin" logger=plugins.backend pluginId=grafana-simple-json-backend-datasource error="Incompatible API version with plugin. Plugin version: 1, Client versions: [2]" This plugin...

This does not solve the problem 100%. Most incoming mails work now but I am still getting "Unable to open database(readonly) /plesk/passwd.db: unable to open database file" - and I am guessing this happens when plain text auth is used, but I am not sure.

Hi, I am experiencing the very same problem. Additionally, incoming mail is also broken. postfix/smtpd connect from unknown[192.168.1.8] postfix/smtpd Unable to open database(readonly) /plesk/passwd.db: unable to open database file

Same here on Debian Jessie with Plesk Onyx 17.8.11 U#67. The following packages have unmet dependencies: aum : Depends: libapache2-mod-security2 but it is not installed

Exactly the same problem here. Could not find any solution so far.

Same error message here.

No, it's a very basic DNS service. I am trying to find any difference between subdomains where renewal is working and those where it doesn't. Working subdomain: No /.well-known/acme-challenge/ gets created at /var/www/vhosts/domain.com/sub.domain.com during renewal, only...

I've tried alot, at the end I even removed a subdomain - expecting to get any exisiting cfg files removed - and then recreating it from scratch without touching any default setting. I have manually created a 777 /.well-known/acme-challenge/ folder, I have removed all files in...

I doublechecked and its set to RSA. Also, during my troubleshooting process I recently tried obtaining a wild card certificate for my main domain and therefore added After this, I got the same connection refused error for my main domain and all previously still working subdomains. Reverting...

"Connection refused" suggests that it is a connection problem, but could this also mean other things, i.e. file permission problems? I really don't understand why six subdomains renew successfully, and four others under the same domain don't. I recently tried a docker proxy rule with one of...

I am using an external DNS service and my subdomains are all configured the same way. There aren't any AAAA records. The server uses IPv4 only. Plesk DNS, even though not being used, does not show any AAAA records. "dig sub.domain.com AAAA" does not return any records.

Thank you kindly for your reply. When I open the connection refused URL (/.well-known/acme-challenge/kpzyzJGoVnVyXaWzW4YDPz2TMxz15MyeGGBXmROYcvo) in my browser, I can see text: I can see my own request in the log: I don't see any request by LE, also when successfully renewing another sub domain.

I am using a domain with ten subdomains. They all use LE certificates. Automatic certificate renewal was working flawlessly in the past year. All of a sudden I am getting notified that four of those subdomains can't be renewed due to: It drives me crazy. My other subdomains still renew fine, so...

I have exactly the same issue. I managed to get updates by changing deb http://ftp.debian.org/debian jessie-backports main in /etc/apt/sources.list to deb http://archive.debian.org/debian jessie-backports main and using apt-get -o Acquire::Check-Valid-Until=false update However, I sincerely...