help: Sitemap URLs generated using HTTP instead of HTTPS

[g-u-x]

📚 What are you trying to do?

Hi,
I’m trying to implement the URLs using HTTPS.
Even though the canonical url includes the correct one across all pages, for some reason the URLs are generated using HTTP.
Not an SEO expert, however I assume this is not good, even when redirects work fine.
Any help to fix this will be really appreciated :)

🔍 What have you tried?

A couple of ways to force the hostname using HTTPS, none of them worked.

ℹ️ Additional context

Nuxt: ^3.14.159
@nuxtjs/sitemap: ^7.0.1
@nuxtjs/i18n: ^9.0.0
Node: v18.20.5
Production website.

[harlan-zw]

Can you share your config and / or a reproduction? It's likely you've configured your site URL to be http://<site>

[butnothero]

the same problem

[butnothero]

[butnothero]

nginx has configured all redirects to https. The application also contains canonical https urls

[harlan-zw]

If you can provide a reproduction for this issue I can make sure it gets solved https://nuxtseo.com/docs/sitemap/getting-started/troubleshooting#submitting-an-issue

[e0v1a]

I encountered the same issue. My site is configured with Nginx, and the HTTPS certificate is properly set up. The .env environment variables, including the BASE_URL, are also set to use https. The entire site operates on the HTTPS protocol and has been running without any issues for a long time.

The only place HTTP is used is in the Nginx reverse proxy. The homepage (pre-rendered) and static assets are directly served by Nginx, while other SSR-related requests are proxied via HTTP to the Nuxt server at http://localhost:3000.

Could you please confirm if this setup might be causing the issue?

However, using HTTP in reverse proxy configurations for backend communication is a very common practice. Please ensure there's an option to explicitly control the protocol (http or https) for URLs generated in the sitemap through additional configuration.

Thank you!

[harlan-zw]

The only thing I can think of is if you didn't configure a site.url and it's falling back to using server headers to figure out what your site canonical URL is.

The module should ideally warn you when this occurs or even throw an error.