The issue concerns the /tags/none route not existing, causing a 404 error. manuel reported the problem, noting it worked previously but stopped after an update. bartv suggested using tag/none instead, as the route was likely renamed. manuel confirmed the workaround but pointed out that the navigation menu still links to tags/none. rishabh referenced the issue and linked to a GitHub commit, seeking a fix. sam confirmed the issue is resolved in a pull request and that deployment will soon fix it.