Lofesa commented on issue #1742: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1742#issuecomment-953753195
Hi Try `https://domain.com/?PageSpeedFilters=+debug`. and see in the html code inserted debug messages as comments. At a first glance I see this: ``` pagespeed Domain img.domain.com; pagespeed MapProxyDomain https://domain.com/img/ https://img.domain.com/; ``` Is img.domain.com running pagespeed? If no, then you don´t need the Domain directive. Why? If in your html code there is a `https://img.domain.com/some-image.jpg`, with this directive these url is rewrited to some like `https://img.domain.com/xsome-image.jpg.SOMEHAS.jpg` (or webp), then this request come to img.domain.com and get a 404 because this domain is not running pagespeed. If in your html are not present any url from `https://img.domain.com` then this directive does nothing. For the MapProxyDomain: If the `https://img.domain.com/` is really an https server you need to enable https fecht is pagespeed becaause if not enabled pagespeed by default fecht with http only. https://www.modpagespeed.com/doc/https_support#https_fetch with `pagespeed FetchHttps enable;` you need to enable other directive `pagespeed SslCertDirectory directory;` as you say is Ubuntu directory sould be /etc/ssl/certs And I can´t see a `pagespeed Domain domain.com`; and the docs say "In addition to optimizing HTML resources, PageSpeed restricts itself to optimizing resources (JavaScript, CSS, images) that are served from domains, with optional paths, that must be explicitly listed in the configuration file. " https://www.modpagespeed.com/doc/domains#auth_domains -- 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. To unsubscribe, e-mail: dev-unsubscr...@pagespeed.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
