Magento – HTTPS – cannot generate sitemap

httpssitemaps

Does any of you have experienced problems with generating the sitemap due to using https instead of http?

I have 2 webshops (each own installation). One of those have a ssl certificate and uses https. I have added this code in the .htaccess to make the whole site use https:

RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Everytime I try to generate sitemap it gives me an error that it's unable to generate the sitemap

while on the other installation (which do not use https) I can generate it no problem

that's why I'm concluding at the moment that there is something wrong with the https settings but I have no clue how to fix it

Best Answer

Are you using "sitemap.xml" as the filename? Magento gives you the option to enter a custom filename, but for some reason it will throw an error when you enter a different name.

If you have multiple stores, you can add them in different folders (like /en_US/ and /fr_FR/) and still set the filename to sitemap.xml.

If that isn't working either, there is something wrong with the write permissions of your file (or the owner).

Related Solutions

Magento – 404 after switching to https

I encountered this same issue while testing out a switch to full https. Home page and admin pages worked fine via https, but all other pages gave a 404.

In my case the root cause was an error in my Apache configuration. Since Apache listens on a separate port for https:// (443 rather than 80) it also has a separate virtual host. On my Ubuntu server the config files were at these paths:

/etc/apache2/sites-available/000-default.conf (port 80)
/etc/apache2/sites-available/default-ssl.conf (port 443)

While the 000-default.conf file had an AllowOverride All declaration as shown below, this was missing from the default-ssl.conf.

<VirtualHost *:80>

  <Directory "/var/www/html">
    AllowOverride All
  </Directory>

</VirtualHost>

After adding the directory node and AllowOverride All to the port 443 virtual host in default-ssl.conf, the 404 errors went away. I believe the issue was that Magento relies on the .htaccess file for url rewrites to work on the front end, and Apache only parses .htaccess files when the AllowOverride All declaration is present. Therefore url rewrites didn't work, thus the 404s. Home page doesn't need a rewrite so it worked, and the admin doesn't use rewrites so it worked fine too.

Magento – How to remove interlacing from the PNG files in magento 2

If you mean you want to run this convert command on several png files, you could try:

find . -iname *.png -execdir convert {} -interlace none {} \;

This would be equivalent to running for every .png file:

convert <mypngfilename> -interlace none <mypngfilename>

where <mypngfilename> is, obviously, the name of the png file.

Make sure you try find . -iname *.png first alone to see the results being produced and making sure they are what you need. Also I am also not familiar with the convert command so test it first on one file to make sure that having the <out> file and <in> file being the same name does not cause issues.

That said, I'm quite suspicious that your sitemap would have anything to do with that warning in the first place but I couldn't tell you with 100% certainity.

Best Answer

Related Solutions

Magento – 404 after switching to https

Magento – How to remove interlacing from the PNG files in magento 2

Related Topic