Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter leears

    (@leears)

    I seem to have fixed the issue!

    Cloudflare was for some reason serving out outdated js files. I dumped my Cloudflare cache and things started working again.

    Let this be a lesson: it’s always either caching or DNS. One of those things is probably the problem, always.

    Thread Starter leears

    (@leears)

    Thanks, Mika—I’ll sit tight and see what I can dig up on my own. Will also drop any relevant info here that I get from the other plugin author, if the issue there has a similar resolution. No rush, and again, I appreciate the responses.

    Thread Starter leears

    (@leears)

    That sounds reasonable, yep. Varnish 5 should act mostly the same as Varnish 4 (at least from how i’m reading the docs), but there might indeed be basic compatibility issues.

    If there’s anything I can supply—logs, configuration files, anything at all—I’m happy to do so. I’m also fully cognizant that you’re on vacation, and I promise I am not expecting instantaneous support!! Thanks for your attention and responses.

    Thread Starter leears

    (@leears)

    Hi Mika—I believe it is, yes. The server in question is running Varnish locally, and has a single public IP address. I am not using Cloudflare or another CDN, so there ought not be any DNS silliness going on.

    Since posting the original thread I’ve also modified the site’s permalink setup from posttitle to to month/posttitle, with no apparent change in the problem behavior, so I don’t think that’s the issue.

    The stack here is HAProxy (SSL termination) to varnish 5, to nginx 1.13.3, with PHP 7 via php-fpm. I’m also troubleshooting this in parallel with another varnish plugin author whose plugin mostly works, but still won’t flush pages when comments are posted/removed.

    I suspect, based on their feedback, that this might simply be due to using Varnish 5 and php7—there might be some incompatibilities with the latest versions of each.

    • This reply was modified 8 years, 10 months ago by leears.
    Thread Starter leears

    (@leears)

    A bit more info: looks like when I smack the “Empty Cache” button on the dashboard, I get this showing up in varnishncsa:

    
    50.28.11.223 - - [14/Jul/2017:19:50:23 -0400] "GET http://mysite.com/.* HTTP/1.1" 403 162 "https://mysite.com/.*" "WordPress/4.8; https://mysite.com"
    

    That’s the correct public IP address, and I can confirm that that address is part of the correct purge ACL and can purge with curl. When I manually execute curl with a purge command, I can see it match that IP address and respond with a 200 without issue:

    
    *   << Request  >> 655368    
    -   Begin          req 655367 rxreq
    -   Timestamp      Start: 1500076516.448708 0.000000 0.000000
    -   Timestamp      Req: 1500076516.448708 0.000000 0.000000
    -   ReqStart       50.28.11.223 50930
    -   ReqMethod      PURGE
    -   ReqURL         /.*
    -   ReqProtocol    HTTP/1.1
    -   ReqHeader      Host: mysite.com
    -   ReqHeader      User-Agent: curl/7.47.0
    -   ReqHeader      Accept: */*
    -   ReqHeader      X-Forwarded-For: 50.28.11.223
    -   VCL_call       RECV
    -   VCL_acl        MATCH purge "50.28.11.223"
    -   VCL_return     synth
    -   VCL_call       HASH
    -   VCL_return     lookup
    -   Timestamp      Process: 1500076516.448760 0.000052 0.000052
    -   RespHeader     Date: Fri, 14 Jul 2017 23:55:16 GMT
    -   RespHeader     Server: Varnish
    -   RespHeader     X-Varnish: 655368
    -   RespProtocol   HTTP/1.1
    -   RespStatus     200
    -   RespReason     OK
    -   RespReason     Purged.
    -   VCL_call       SYNTH
    -   RespHeader     Content-Type: text/html; charset=utf-8
    -   RespHeader     Retry-After: 5
    -   VCL_return     deliver
    -   RespHeader     Content-Length: 244
    -   Storage        malloc Transient
    -   RespHeader     Accept-Ranges: bytes
    -   RespHeader     Connection: keep-alive
    -   Timestamp      Resp: 1500076516.448795 0.000087 0.000035
    -   ReqAcct        88 0 88 220 244 464
    -   End   
    

    That’s only when I do it manually. Hitting the button yields no activity in varnishlog and only the 403 error in varnishncsa.

    Thread Starter leears

    (@leears)

    Also worth noting that the debug hints on the FAQ don’t work because the varnishlog syntax has changed and “-m” is no longer a valid option.

    Thread Starter leears

    (@leears)

    For reference, here’s a quick image of the WP4.8 permalink screen and the option I have selected.

Viewing 7 replies - 1 through 7 (of 7 total)