bug(web): all /{username} web routes return 404 on dev instance #257

New Issue

2026-05-30T22:59:55Z

jmiller commented

2026-05-30 22:59:55 +00:00

Summary

On the dev instance (git.dev.mokoconsulting.tech), all web routes matching /{username} and /{username}/{reponame} return 404. API routes work correctly.

Reproduction

GET /testadmin -> 404
GET /testadmin/checksum-final -> 404
GET /explore/repos -> 200 (works)
GET /api/v1/repos/testadmin/checksum-final -> 200 (works)
GET /api/v1/version -> 200 (works)

Impact

All user profile pages broken
All repository web pages broken
Update server endpoints (updates.xml, dolibarr.json) unreachable
Admin settings UI may be affected
API layer works correctly

Likely cause

The web router pattern matching for /{username} routes is failing. This could be:

A template asset issue (missing compiled frontend assets in the Docker image)
A route registration conflict from new routes
A middleware issue in RepoAssignment

Environment

Dev instance: git.dev.mokoconsulting.tech
Image: dev-latest (commit 2b82312b4e)
Production (git.mokoconsulting.tech) is on a different image and works fine

Created by @MokoBot - Claude Opus 4.6

## Summary On the dev instance (git.dev.mokoconsulting.tech), all web routes matching `/{username}` and `/{username}/{reponame}` return 404. API routes work correctly. ### Reproduction - `GET /testadmin` -> 404 - `GET /testadmin/checksum-final` -> 404 - `GET /explore/repos` -> 200 (works) - `GET /api/v1/repos/testadmin/checksum-final` -> 200 (works) - `GET /api/v1/version` -> 200 (works) ### Impact - All user profile pages broken - All repository web pages broken - Update server endpoints (updates.xml, dolibarr.json) unreachable - Admin settings UI may be affected - API layer works correctly ### Likely cause The web router pattern matching for `/{username}` routes is failing. This could be: 1. A template asset issue (missing compiled frontend assets in the Docker image) 2. A route registration conflict from new routes 3. A middleware issue in RepoAssignment ### Environment - Dev instance: git.dev.mokoconsulting.tech - Image: dev-latest (commit 2b82312b4e) - Production (git.mokoconsulting.tech) is on a different image and works fine --- *Created by @MokoBot - Claude Opus 4.6*

jmiller commented

2026-05-30 23:06:35 +00:00

Not a code bug. The testadmin user had visibility=1 (limited) which blocks anonymous web access. Set to visibility=0 (public) and all routes work correctly. All features verified on dev.

@MokoBot (Claude Opus 4.6)

Not a code bug. The testadmin user had visibility=1 (limited) which blocks anonymous web access. Set to visibility=0 (public) and all routes work correctly. All features verified on dev. @MokoBot (Claude Opus 4.6)

jmiller closed this issue

2026-05-30 23:06:35 +00:00

Sign in to join this conversation.

Priority -

Type -

Status —

Priority —

Type —

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#257