Matomo broken after moving to another server

  • Resolved amedat

    (@amedat)


    3 years, 8 months ago

    Hello.
    I have a problem after having moved my website to another server.
    I cannot archive the reports and all reports are stopped about 6 days ago.
    However, I can see real time visits, but they are not archived.
    I have tried to empty and deactivate the W3 cache and also Matomo cache.
    I also tried deleting Matomo folder and reinstalling it, but none happens.
    When I run Manual Archive in Diagnostic, I see the report like this:

    Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2021-03-18&format=json&trigger=archivephp. Response was \’PHP Fatal error: Uncaught Error: Call to undefined function mysql_connect() in $ABSPATH/wp-includes/wp-db.php:1688 Stack trace: #0 $ABSPATH/wp-content/plugins/w3-total-cache/DbCache_WpdbNew.php(97): wpdb->db_connect()

    (I sent you an email with the full report).

    Could you help, please?
    Thank you very much and best regards,
    – Amedeo

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Thomas

    (@tsteur)

    Thanks for reporting this @amedat and sorry about this.

    It seems there is an error in the w3-total-cache plugin which is causing issues for our plugin:

    > Call to undefined function mysql_connect() in $ABSPATH/wp-includes/wp-db.php:1688 Stack trace: #0 $ABSPATH/wp-content/plugins/w3-total-cache/DbCache_WpdbNew.php(97): wpdb->db_connect()

    Is there maybe an update available for W3 Total Cache or is there any chance you could reach out to them regarding this error?

    Thread Starter amedat

    (@amedat)

    Hello.
    After some researches, I solved adding:
    define(‘MATOMO_SUPPORT_ASYNC_ARCHIVING’, false);
    in wp-config.php.
    Can you explain me if it is a good solution?
    Best regards, Amedeo.

    Plugin Author Thomas

    (@tsteur)

    That works @amedat It’s often a good solution but in some cases it can cause issues related to server configuration like if you’re tracking a lot of visits and the webserver has configured a low request timeout. It’s quite technical but basically I would keep this setting and if you notice that reports aren’t appearing or that some errors pop up then you might need to change back the setting again. Most people don’t experience any issue with this though and it just works. You would notice it doesn’t work if it’s not showing any data in the reports.

    I would still recommend forwarding the above error to the W3 Total Cache team though.

    Glad it’s working now @amedat let me know if you have any further question.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Matomo broken after moving to another server’ is closed to new replies.