• Resolved yhsh

    (@yhsh)


    Hi,

    This is the second time update fails because of an issue with the origin server…
    My best guess is that this started when I set up an origin certificate in cloudflare and had to change some dns records…

    Could you pls send me in the right direction to correct this update error? I’m again guessing that I need to change some setting(s) in Matomo too?

    Here is a screenshot of the error: https://i.imgur.com/tfmhmZJ.png

    Thank you kindly.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter yhsh

    (@yhsh)

    Oops. I think I may have overlooked the fact that it did update and the tracking was simply disabled. Don’t know how that happened…

    Hmm…

    If you can confirm the error as caused by this mistake, then you may close the topic. Apologies.

    Plugin Author Thomas

    (@tsteur)

    Hi @yhsh thanks for creating this issue. Do I understand this correctly the plugin was updated correctly but the tracking got disabled?

    Generally, there isn’t really any way AFAIK that disabling the tracking could be triggered by our plugin unless the plugin was uninstalled and then installed again. I’m not sure if this could have happened somehow during the update as it seems you’ve had issues there. Maybe when the update failed WordPress did uninstall the plugin because the files were missing. This would likely not be anything we could influence since it is all WordPress logic. It seems related though to the error you had.

    > Could you pls send me in the right direction to correct this update error? I’m again guessing that I need to change some setting(s) in Matomo too?

    Unfortunately I can’t help regarding any certificates as the origin server would be the WordPress plugin directory server and not a server from us. Looking at the screenshot you may want to get in touch with your hoster maybe or even with Cloudflare. I couldn’t find this error message in WordPress itself so I’m assuming Cloudflare might have triggered that error.

    Thread Starter yhsh

    (@yhsh)

    Seems to be working again now. I’ll wait until next update and see how it goes…thanks.

    Plugin Author Thomas

    (@tsteur)

    Thanks for this @yhsh and be great to comment here if you run into this issue again and we’ll follow up.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Second time update fails- origin server/certificate’ is closed to new replies.