Gandalf/sofarr
Public Access
0
0
Fork 0
Code Issues 1 Pull Requests Actions 1 Packages Projects Releases 59 Wiki Activity

BUG: Ombi webhook enable endpoint returning 404 in production #40

New Issue
Closed
opened 2026-05-23 09:53:04 +01:00 by Gandalf · 1 comment
Gandalf commented 2026-05-23 09:53:04 +01:00
Owner
Copy Link
Copy Source

Bug Description

The Ombi webhook setup is failing in production. When the frontend attempts to enable the webhook by sending a POST request to https://sofarr.i3omb.com/api/ombi/webhook/enable, the server responds with a 404 (Not Found) error in the console:

POST https://sofarr.i3omb.com/api/ombi/webhook/enable 404 (Not Found)
Failed to enable Ombi webhook: Error: Failed to enable
    at Fe (app.js:1:6504)
    at async HTMLButtonElement.lt (app.js:8:21364)

Root Cause

  1. In server/app.js (used for integration testing), the Ombi routes are imported and mounted correctly under /api/ombi: 
    const ombiRoutes = require('./routes/ombi');
...
app.use('/api/ombi', ombiRoutes);
  2. However, the production entry point server/index.js does NOT import createApp from server/app.js or mount the ombiRoutes router. Instead, server/index.js duplicates the Express app configuration and fails to register ombiRoutes, causing all /api/ombi/* endpoints to return a 404 (Not Found) in production.

Proposed Changes

  1. Import ombiRoutes in server/index.js: 
    const ombiRoutes = require('./routes/ombi');
  2. Mount the Ombi router under /api/ombi in server/index.js: 
    app.use('/api/ombi', ombiRoutes);
### Bug Description The Ombi webhook setup is failing in production. When the frontend attempts to enable the webhook by sending a `POST` request to `https://sofarr.i3omb.com/api/ombi/webhook/enable`, the server responds with a `404 (Not Found)` error in the console: ``` POST https://sofarr.i3omb.com/api/ombi/webhook/enable 404 (Not Found) Failed to enable Ombi webhook: Error: Failed to enable at Fe (app.js:1:6504) at async HTMLButtonElement.lt (app.js:8:21364) ``` ### Root Cause 1. In `server/app.js` (used for integration testing), the Ombi routes are imported and mounted correctly under `/api/ombi`: ```javascript const ombiRoutes = require('./routes/ombi'); ... app.use('/api/ombi', ombiRoutes); ``` 2. However, the production entry point `server/index.js` does NOT import `createApp` from `server/app.js` or mount the `ombiRoutes` router. Instead, `server/index.js` duplicates the Express app configuration and fails to register `ombiRoutes`, causing all `/api/ombi/*` endpoints to return a `404 (Not Found)` in production. ### Proposed Changes 1. Import `ombiRoutes` in `server/index.js`: ```javascript const ombiRoutes = require('./routes/ombi'); ``` 2. Mount the Ombi router under `/api/ombi` in `server/index.js`: ```javascript app.use('/api/ombi', ombiRoutes); ```
Gandalf added the Kind/Bug
Priority
High
2
 labels 2026-05-23 09:53:04 +01:00
Gandalf reopened this issue 2026-05-23 09:59:05 +01:00
Gandalf commented 2026-05-23 09:59:08 +01:00
Author
Owner
Copy Link
Copy Source

Reopened and successfully closed via commit db809f2fb343bec48fe6c948fbaf6d66844a77b3 on the develop branch.

All automated tests passed successfully, confirming the Ombi routes /api/ombi/* are now correctly mounted in the production server entry point.

Reopened and successfully closed via commit [db809f2fb343bec48fe6c948fbaf6d66844a77b3](https://git.i3omb.com/Gandalf/sofarr/commit/db809f2fb343bec48fe6c948fbaf6d66844a77b3) on the `develop` branch. All automated tests passed successfully, confirming the Ombi routes `/api/ombi/*` are now correctly mounted in the production server entry point.
Gandalf added the Area/Proxy label 2026-05-28 11:58:28 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Area/Docker
Docker image and container packaging
 Area/Download Clients
Download client integrations
 Area/Frontend
Client-side UI and build tooling
 Area/History
History and completed downloads views
 Area/Logging
Log streaming, file handling, and debug infrastructure
 Area/Matching
Matching and correlation logic
 Area/Proxy
Upstream service proxy routes
 Area/SSE
Server-Sent Events and real-time streaming
 Area/Webhooks
Webhook processing and reliability
 Compat/Breaking
Breaking change that won't be backward compatible
 Compat/Non-Breaking
Non-breaking compatibility change
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Area/Proxy Kind/Bug
Priority
High
2
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Gandalf
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Gandalf/sofarr#40
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?