MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 163 Pull Requests Actions Packages Licenses 2 Releases 68 Wiki Activity

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

New Issue
Closed
opened 2026-05-30 22:59:55 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-30 22:59:55 +00:00
Owner
Copy Link
Copy Source

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

## 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
Author
Owner
Copy Link
Copy Source

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)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 pending: testing
Feature implemented but not yet tested with documented proof
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 type: bug
Something isn't working
 type: bug
type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#257
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?