Generates http only links and not https when our site is https

[coolgal1980]

How can I make sure it generates sitemap for https?

[miroslav-mihaljevic-luminos]

We are experiencing same issue, and the very strange thing is that after we set all sitemaps to https, after deleting cache, refreshing, running sitemap job and re-logging, I see them set to https, but a colleague see some of them reverted to http, we confirmed that by comparing screenshots at the same time (difference is that he connects from USA and I connect from Europe, maybe it has something to do with that)

EDIT: After trying in incognito mode, now I see also that some them reverted to http

[miroslav-mihaljevic-luminos]

Here is an example, after setting absolutely all sitemaps to https, I still got about 10 of them with http only links, so the sitemap listing show they are all https, but they are not:

And after I press "edit" on that same sitemap, then it shows me in dropdown that it actually stayed on http URL

[miroslav-mihaljevic-luminos]

Here is a workaround on how to update them all to https:

1. Open incognito window
2. Go to the sitemap configuration page, and open each sitemap using the "View" button at the side
3. Scroll through opened sitemaps (easy using Ctrl+PageDown/Up) and check which are not HTTPS
4. Add tabs with HTTP sitemaps to separate tab group and use Chrome's feature to save all tabs into bookmarks (will help with retesting later)
5. Close all incognito windows

Now follows the part that will be repeated as needed

1. Delete images/files cache (don't know if helps but I do it)
2. Open incognito mode and go to the sitemap configuration page
3. Find all http:// URLs and update them to HTTPS
4. Run generate sitemap job
5. Open all saved tabs with sitemaps from bookmarks (use the "open all tabs" option, not each individually)
6. Check if they all got HTTPS links and note the ones that don't
7. Close all incognito windows
8. Delete image/files cache
9. Again update the sitemaps, rinse and repeat until you got them all updated

It appears that the root problem is that sitemap configuration doesn't really get updated after pressing the update button and that the browser caches the saved state, and users see it on their screen, but the configuration is not actually saved on the server