Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: Dumbdrop Not Respecting BASE_URL #39

Open
zabaya opened this issue Mar 8, 2025 · 1 comment
Open

Issue: Dumbdrop Not Respecting BASE_URL #39

zabaya opened this issue Mar 8, 2025 · 1 comment

Comments

@zabaya
Copy link

zabaya commented Mar 8, 2025

I am trying to set up DumbDrop in combination with CalibreWeb's automated ingest folder.

I am running Dumbdrop behind a reverse proxy using Nginx Proxy Manager (NPM), serving it under a subpath /watchfolder/ at:
https://calibre.example.com/watchfolder/

I have set my base url in docker to: BASE_URL: "https://calibre.example.com/watchfolder/"

However, Dumbdrop ignores the BASE_URL setting and continues to send API requests to:
https://calibre.example.com/api/upload/init instead of: https://calibre.example.com/watchfolder/api/upload/init

As a result, the API requests are sent to CalibreWeb instead of Dumbdrop, causing the upload process to fail.

When I host Dumbdrop on a dedicated subdomain (e.g., https://watchfolder.example.com), everything works fine.

This is my advanced setup I set up in the custom location in NPM:

location /watchfolder/ {
    rewrite ^/watchfolder(/.*)$ $1 break;
    proxy_pass http://10.0.0.130:8084/;
    
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}

Is there a way to make this setup work with a subpath /watchfolder/, or is it simply not feasible?

@zabaya zabaya closed this as completed Mar 8, 2025
@zabaya zabaya reopened this Mar 8, 2025
@abiteman
Copy link
Collaborator

abiteman commented Mar 8, 2025

Hmmm we'll take a look at this, we had only tested with

https://www.domain.com/subpath
And
Https://www.subdomain.domain.com

Not both combined, if you're able to set it up as either of those configs it should work, but this is a scenario we can look at implementing potentially

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants