jmarantz commented on issue #1686: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-623178725
Sorry, didn't mean to say it was a dead end. For an asset that's 404ing in the browser, can you see what's happening on the Apache server logs? Maybe give more details about that. For example, if you found a resource was failing named foo.css.pagespeed.cf.HASH.css in the browser, can you scan the Apache error logs to see if there's issues fetching foo.css? In a multi-server setup, it could be that one of the servers can fetch foo.css, and the other one can't. A shared redis might hide this problem and make it reproduce inconsistently, but ultimately the root cause is likely a failure to fetch the resource from mod_pagespeed, and that should show up in the logs. However, another scenario is that you are running into this bug: https://github.com/apache/incubator-pagespeed-mod/issues/1145. It took me a while to find that. I haven't fully re-read it, but I think the scenario could be that *neither* of your pagespeed instances is able to fetch anything. And the way it is able to optimize assets is by saving them in the local cache while it serves them from their original URLs via In Place Resource Optimization <https://www.modpagespeed.com/doc/system#ipro>. To test this theory, you could disable In Place Resource Optimization off: ModPagespeedInPlaceResourceOptimization off If you do this, I suspect the 404s will go away, but you also won't be optimizing anything. Then we can work on how to ensure your mod_pagespeed instances are able to fetch the origin assets via HTTP. Can you give that first step a try? Disable the feature as above, then see if that fixes the 404s. -Josh On Sun, May 3, 2020 at 3:28 PM Andrew Borg <notificati...@github.com> wrote: > Then i'm at a loss, dunno what else to look at. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pagespeed-ngx/issues/1686#issuecomment-623167179>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAO2IPIWX6E3FR7TNXPYBRTRPXAWRANCNFSM4MTB4TGA> > . > ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
