vardan-karapetyan edited a comment on issue #1996: URL: https://github.com/apache/incubator-pagespeed-mod/issues/1996#issuecomment-646817154
> Well... for Centos the directory and file must be: > > ``` > pagespeed SslCertDirectory /etc/pki/tls/certs; > pagespeed SslCertFile /etc/pki/tls/cert.pem; > ``` > > These are the default config. > > And some things I don´t understand: > You have an opencart site running on nginx public IP, but what have running in 127.0.0.1:80 and 127.0.0.1:8080? if you only have the server block for the public IP ( these with erver_name example.ru [www.example.ru](http://www.example.ru);) the site runs normaly? or you need to make request to 127.0.0.1:80? > > Whit this directive pagespeed MapOriginDomain "http://localhost"; "https://example.ru";; you are saying "when a request to the https://example.ru site is made, you must change the domain to http://localhost to retrieve the request" so in http://localhost mus be running the "true" site, in your case the opencart site. If I´m not wrong, you not need these directive because the opencart site is running in the public IP. > An example: > Think you are running the opencart behins a firewall that only permit your public ip to enter. Some like > user -> nginx public IP + pagespeed -> firewall -> nginx 127.0.0.1:80 > > But I think you only need the server block where opencart is running. What happens if you comment the server block for 127.0.0.1:80? your site still running? Do you mean this block? ``` #server { # server_name localhost; # disable_symlinks if_not_owner; # listen 80; # listen [::]:80; # include /etc/nginx/vhosts-includes/*.conf; # location @fallback { # error_log /dev/null crit; # proxy_pass http://127.0.0.1:8080; # proxy_redirect http://127.0.0.1:8080 /; # proxy_set_header Host $host; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # proxy_set_header X-Forwarded-Proto $scheme; # access_log off ; # } # } ``` I commented on this block and the sites are still working. But I still get 404 from css and js. But the most important thing is that not all files return 404, some css and js function. After commenting out the server, a real ip:80 appeared in the terminals instead of 0.0.0.0:80 And now the site caches with the disabled LoadFromFile option "https://example.ru"; "/var/www/example/data/www/example.ru"; but 404 errors still remained. ---------------------------------------------------------------- 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
