• maxity

    (@maxity)


    We have faced this problem multiple times now, so I decided to seek for help here.

    After copying an existing WordPress installation to a different vhost (same web server), adjusting Domain and other config values for the new website, the plugin is not able to connect to our Matomo server anymore:

    “WP-Matomo 1.0.23 was not able to connect to Matomo using your configuration.”

    The plugin ist set to self-hosted HTTP along with the URL to our Matomo server and the correspondig auth token. The very same configuration works flawlessly in every new WordPress installation. This just happens after copying like described above.

    We are using WordPress 5.5.3 and plugin version 1.0.24 (error message is saying 1.0.23 tho).

    • This topic was modified 4 years ago by maxity.
Viewing 4 replies - 1 through 4 (of 4 total)
  • James Hall

    (@putarguygmailcom)

    I’m also having this same problem.
    My version of the plugin is 1.0.24 but the error shows version 1.0.23 as well

    I went so far as to wipe-out my Matomo server and rebuild it from scratch, but same result.

    Except now version 4.0.5 is running much slower for me (about 10 seconds wait time on every click under settings).

    • This reply was modified 3 years, 11 months ago by James Hall.
    James Hall

    (@putarguygmailcom)

    UPDATE:

    Since I had to rebuild my Matomo server anyway, I set everything back to default and started over using a fresh install of Matomo v.4.1.0.

    These sites were moved to this server using the All-in-One WP Migration plugin about 1 year ago. Only a few were new to this rebuild. It took me more than a week to move 110 sites manually.

    The first 90-95 went in without a problem, changing them all from a ‘proxy script’ to ‘default tracking’ and updating to the new ‘auth token’ then saving the settings worked like clockwork until (something) choked, and now the plugin WP-Matomo cannot connect to Matomo Server (it says).

    All 110 websites are on the same server with the same IP address as the Matomo Server they are connecting to. For some reason they can’t update the list of websites that are pre-configured in Matomo Server.

    I have found the most success in entering a website’s information in Matomo Server before trying to connect the two works best.

    I am currently editing the JavaScript code for WordPress and manually entering the ‘SiteID’ in the footer code, and although it is a pain to do this, it seems to be working even though the list of sites isn’t updating even after rebooting the server. It’s as if the server is blocking all new sites now…

    James

    Plugin Author braekling

    (@braekling)

    @maxity Did you check your server logfiles? This may give a hint on what’s going wrong here. E.g., if you configured some redirects while you were moving/duplication your installation, you should always make sure to use the direct URL to Matomo and avoid redirects.

    @putarguygmailcom Please avoid hijacking other user’s threads as well as cross posting in different forums. I’ll answer your question in the Matomo forum to divide it from maxity’s thread. (https://forum.matomo.org/t/matomo-server-stopped-allowing-new-connections/40086/3)

    Plugin Author braekling

    (@braekling)

    – Sorry, duplicate –

    • This reply was modified 3 years, 10 months ago by braekling.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Unable to connect to Matomo server in duplicated WordPress installations’ is closed to new replies.