LaneDNS: /sitemap.xml and /robots.txt return 404 under nginx

FeatureOpenView on roadmap· 13 days ago

Imported from GitHub issue El-SaMa/oma#213 by @El-SaMa.

nginx ignores the old .htaccess rewrites, so only sitemap.php / robots.php work; /sitemap.xml (linked in every page head and robots) and /robots.txt 404. Pre-existing.

Do (no vhost hand edits): generate static sitemap.xml, sitemap-tools.xml, robots.txt files on deploy or by a small cron that runs scripts/regenerate-sitemap.php, or ask the operator to add an Enhance-supported rewrite. Also manifest.webmanifest is served as application/octet-stream (works, but should be application/manifest+json). Then submit the sitemap in Search Console (verification token can be set in OMA Settings).

Context (2026-10-14): lanedns.lanetti.fi (Lanetti Tools, standalone PHP site on nilek, repo El-SaMa/lanedns site/) was revamped and OMA became its control plane: usage in /admin/tools/usage, settings in /admin/tools/settings, staff MCP oma.admin_lanetti_tools, config pull GET /api/lanetti-tools/config (link token in LaneDNS storage/oma-link.php). Events: site_events site lanedns.lanetti.fi, tool_run sanitized by services/core-api/src/lanetti-tools/usage-events.ts. Read handbook hosting/netspeed section "OMA is the control plane" and .cursor/rules/lanedns-standalone.mdc (deploy recipe: keep public_html group www-data) before touching LaneDNS.

Comments (0)

No comments yet.

Join the discussion