• Resolved john210360

    (@john210360)


    After restoring a WordPress backup I get the following error on the WordPress dashboard:

    Something went wrong! Error: “CONNECTION_ERROR : “Unknown Error. Last error: include_once(): Failed opening ‘/var/lib/sec/wp-settings.php’ for inclusion (include_path=’.:/usr/share/php’)”.

    How can I fix this?

    Thanks in advance for your help.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author alexandergull

    (@alexandergull)

    Greetings @john210360

    It seems this error does not refer to the CleanTalk plugin.

    What makes you think it does?

    Be well,

    Thread Starter john210360

    (@john210360)

    CleanTalk doesn’t display the anti-spam statistics. Instead it displays

    Something went wrong! Error: “CONNECTION_ERROR : “Unknown Error. Last error: include_once(): Failed opening ‘/var/lib/sec/wp-settings.php’ for inclusion (include_path=’.:/usr/share/php’)”.

    When I go to the CleanTalk configuration page it displays:

    2021-08-28 12:49:34: Error occurred while updating SpamFireWall local base. Error: CREATE TEMP TABLES: COULD NOT CREATEwp_cleantalk_sfw_temp

    It is probably a WordPress misconfiguration issue because it happened after a restore.

    Plugin Support SergeM

    (@serge00)

    Hello, @john210360.
    Please, re-install the CleanTalk Anti-Spam Plugin with the Complete Deactivation option:
    ? WordPress Admin Page —> Settings —> Anti-Spam by CleanTalk —> Advanced settings —> set the option “Complete Deactivation” to “On” —> Save Changes;
    ? WordPress Admin Page —> Plugins —> Installed plugins —> Anti-Spam by CleanTalk —> Deactivate and Delete.

    Then install it anew:
    https://cleantalk.org/help/install-wordpress

    It will solve the issue. Did it help?

    Thread Starter john210360

    (@john210360)

    I granted create and drop rights on the wordpress database to the wordpress user. Then I reinstalled CleanTalk. That solved the database access error.

    I am now left with only one error on the dashboard: JSON_DECODE_ERROR.

    Do you have a solution for that?

    Thanks again for your help.

    • This reply was modified 3 years, 6 months ago by john210360.
    Plugin Support SergeM

    (@serge00)

    Please, synchronize the plugin:
    ? WordPress Admin Page —> Settings —> Anti-Spam by CleanTalk —> press the button “Synchronize with Cloud”

    If it didn’t help, please tell me the following details:
    1. Your PHP version
    2. Your WordPress version
    3. The CleanTalk plugin version you are using

    Thank you.

    Thread Starter john210360

    (@john210360)

    That didn’t work.

    PHP version = 7.4.16
    Wordpress version: 5.7.2
    CleanTalk version: 5.160.2

    Thanks.

    Plugin Support SergeM

    (@serge00)

    Thank you for your reply.
    I’ve passed your details to the programmer staff.
    We will write back to you within 2-3 business days. Please, wait.

    Hello,

    Could you check it once again? We had a server-side issues.

    Best regards.

    Thread Starter john210360

    (@john210360)

    I have found the problem. After disabling the WP Fastest Caching plugin and synchronizing with the cloud all CleanTalk error messages disappeared.

    Thanks again for your help.

    Plugin Support SergeM

    (@serge00)

    Thank you for your confirmation.
    Kind regards.

    But I am not using WP Fastest Cache?

    Plugin Support SergeM

    (@serge00)

    Please, repeat the following, @cleanadmin:
    ? WordPress Admin Page —> Plugins —> Installed plugins —> Anti-Spam by CleanTalk —> Deactivate and Activate again
    ? WordPress Admin Page —> Settings —> Anti-Spam by CleanTalk —> press the button “Synchronize with Cloud”

    Did it help?

    Plugin Support katereji

    (@katereji)

    Hello, @cleanadmin
    We haven’t heard back from you in a while, so I’m going to mark this thread as “resolved” – if you have any further questions, you can start a new thread.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Error after restoring WordPress.’ is closed to new replies.