404 on https://fair.pm/sitemap_index.xml

[tacoverdo]

Problem description

With Yoast SEO installed, https://fair.pm/sitemap_index.xml should show a sitemap. However, it returns a 404.
The non-pretty version (https://fair.pm/?sitemap=1) does work properly.

Possible solution

In Yoast SEO's documentation for NGINX, they suggest adding the following config for NGINX to the NGINX config file:

#Yoast SEO Sitemaps
location ~ ([^/]*)sitemap(.*).x(m|s)l$ {
  ## this rewrites sitemap.xml to /sitemap_index.xml
  rewrite ^/sitemap.xml$ /sitemap_index.xml permanent;
  ## this makes the XML sitemaps work
  rewrite ^/([a-z]+)?-?sitemap.xsl$ /index.php?yoast-sitemap-xsl=$1 last;
  rewrite ^/sitemap_index.xml$ /index.php?sitemap=1 last;
  rewrite ^/([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&sitemap_n=$2 last;
  ## The following lines are optional for the premium extensions
  ## News SEO
  rewrite ^/news-sitemap.xml$ /index.php?sitemap=wpseo_news last;
  ## Local SEO
  rewrite ^/locations.kml$ /index.php?sitemap=wpseo_local_kml last;
  rewrite ^/geo-sitemap.xml$ /index.php?sitemap=wpseo_local last;
  ## Video SEO
  rewrite ^/video-sitemap.xsl$ /index.php?yoast-sitemap-xsl=video last;
}

[rmccue]

This is likely this rule: https://github.com/fairpm/infrastructure-private/blob/2c288fa62f48a8641c548f4c743f1ad4616aa258/helm/projects/site/charts/site/values.yaml#L86

Adding a try_files to this block should solve the problem, but I'd rather we target the sitemap URLs specifically rather than routing all traffic in - which would cause undue server load.

[verlev]

If someone would/can implement this, pls mind the sitemap has other url's too if they would need to be targeted one by one.
At this moment:

• https://fair.pm/post-sitemap.xml
• https://fair.pm/page-sitemap.xml
• https://fair.pm/category-sitemap.xml

[tacoverdo]

@rmccue How can I help you move this issue forward?