woocommerce update failed but then it’s ok 2!

  • Resolved dannybo

    (@dannybo)


    1 year, 3 months ago

    In reference of the problem and what I have done here:

    https://www.ads-software.com/support/topic/woocommerce-update-failed-but-then-its-ok/

    Updating today the woocommerce plugin the varnish error still the same. After refreshing the page, woocommerce results updated to the new version anyway and everything seems fine. :-/ 

    Update failed: <?xml version=”1.0″ encoding=”utf-8″?> <!DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN” “https://www.w3.org /TR/xhtml1/DTD/xhtml1-strict.dtd”> 503 Service Unavailable Error 503 Service Unavailable Service Unavailable Guru Meditation: XID: 1789423382 Varnish cache server.

    I really don’t know what to do… just previously chatted with hosting people and there’s nothing they can do/suggest days ago. I wrote again to them, but i’m really don’t know what to do… but most importantly…

    It’s woocommerce regularly updated?

    Thank you.

    Daniele

    • This topic was modified 1 year, 3 months ago by dannybo.
    • This topic was modified 1 year, 3 months ago by Kathryn Presner.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter dannybo

    (@dannybo)

    ok just saw these message (errors – always the same) inside woocommerce logs…. maybe can help me resolve the situation? 

    2023-07-10T00:06:40+00:00 CRITICAL Uncaught Error: Class "VarnishWPFC" not found in /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/inc/preload.php:522 Stack trace: #0 /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/wpFastestCache.php(1874): PreloadWPFC::create_preload_cache() #1 /home/sf3bkg2y/public_html/wp-includes/class-wp-hook.php(308): WpFastestCache->create_preload_cache() #2 /home/sf3bkg2y/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #3 /home/sf3bkg2y/public_html/wp-includes/plugin.php(565): WP_Hook->do_action() #4 /home/sf3bkg2y/public_html/wp-cron.php(188): do_action_ref_array() #5 {main} thrown in /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/inc/preload.php alla riga 522

    Thank you

    Daniele

    • This reply was modified 1 year, 3 months ago by Kathryn Presner.
    • This reply was modified 1 year, 3 months ago by Kathryn Presner. Reason: put error in code block
    Thread Starter dannybo

    (@dannybo)

    this is the most recent one:

    2023-08-09T00:14:36+00:00 CRITICAL Uncaught Error: Class "VarnishWPFC" not found in /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/inc/preload.php:563 Stack trace: #0 /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/inc/preload.php(758): PreloadWPFC::create_preload_cache_default() #1 /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/wpFastestCache.php(1877): PreloadWPFC::create_preload_cache() #2 /home/sf3bkg2y/public_html/wp-includes/class-wp-hook.php(308): WpFastestCache->create_preload_cache() #3 /home/sf3bkg2y/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #4 /home/sf3bkg2y/public_html/wp-includes/plugin.php(565): WP_Hook->do_action() #5 /home/sf3bkg2y/public_html/wp-cron.php(188): do_action_ref_array() #6 {main} thrown in /home/sf3bkg2y/public_html/wp-content/plugins/wp-fastest-cache/inc/preload.php alla riga 563

    Daniele

    • This reply was modified 1 year, 3 months ago by Kathryn Presner.
    • This reply was modified 1 year, 3 months ago by Kathryn Presner. Reason: put error in code block
    Thread Starter dannybo

    (@dannybo)

    I think the VarnishWPFC not found has been resolved unchecking the “automatic preload of the entire site” by WP Fastest Cache. Since then, no more woocommerce-errors-logs.

    Now, I’m still need to resolve the very first question… the varnish 503 error during woocommerce update. I personally think that it has something to do with some kind of “time limit” in varnish cache configuration by the hosting.

    Hope to get back with good news soon…

    Daniele

    Saif

    (@babylon1999)

    Hello @dannybo,

    I’m sorry to hear you’re still encountering this problem. Based on the logs you’ve attached, it seems like this plugin: https://www.ads-software.com/plugins/wp-fastest-cache/ is causing the error. Have you tried disabling it?

    Also, did you get a chance to implement the necessary configurations for Varnish caching that I previously shared? :?)

    Look forward to hearing back from you.

    Thread Starter dannybo

    (@dannybo)

    @babylon1999 I know. Already deactivated the plugin. The preload seems to create problems. Once unchecked the “preload of the entire website”, logs for woocommerce become ok. But i changed with W3 TOTAL CACHE (My host suggested this one). But the problem with varnish still persist.

    THIS TIME… the error (with W3 TOTAL CACHE) is a little bit different… <!DOCTYPE html> 503 Backend fetch failed Error 503 Backend fetch failed Backend fetch failed Guru Meditation: XID: 16036571 Varnish cache server

    Asked for support to my hosting they’re still investigating… :-/ Of course woocommerce (when refreshed the plugin page) is correctly updated, status is OK.

    So… trying to investigate … i’m asking myself if the plugin LOGINIZER could have problems with varnish communications. When i activated the varnish cache Loginizer advise me to change REMOTE_ADDR into HTTP_X_FORWARDED_FOR to avoid my IP to coincides with that of the SERVER.

    BUT, not satisfied, in all my browsers I disabled “Use DNS-over-HTTPS instead of system DNS settings” (cloudfare was then selected). Maybe I’ll be stupid, but I suspect that “may” also affect the situation…

    Of course now (with after done the last two passages i wrote) i need to wait for another woocommerce update to check. In the meantime my host routed my help request to a more specific team. (after 10 unuseful messages :-/)

    That’ all.

    Daniele

    Thread Starter dannybo

    (@dannybo)

    Hola.

    As previously said (since the beginning speaking with my host), hosting team advise me today about a probably “time out” of the varnish cache in my case. Being on some shared hosting with different websites, time out can be adjusted (varnish configuration) but they need to check and change things for all the server and all the websites involved. This operation needs some study, inside the host, before being applied to everyone. So they suggest me to disable the varnish before any woocommerce update and then restore it. Until futher notice. They also tell me woocommerce updates regularly in background despite the warning message of the varnish.

    Daniele

    Plugin Support Thu P. a11n

    (@thup90)

    Hi Daniele,

    Thanks for letting us know. Do keep us posted on what your host finds with Varnish cache settings!

    Plugin Support Gabriel – a11n

    (@gabrielfuentes)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘woocommerce update failed but then it’s ok 2!’ is closed to new replies.