SafariBooks-Downloader: All books returning 404?

Hi,

Just recently books started returning 404:

$ safaribooks-downloader -u user -p "password" -o ./books/book.epub -b id
[safari-downloader] starting application...
[safari-downloader] the user "bernd@rennebeck.org" was successfully authorized...
[safari-downloader] StatusCodeError: 404 - {}

This is happening for all books I try.

About this issue

Original URL
State: open
Created 6 years ago
Reactions: 8
Comments: 22 (8 by maintainers)

Most upvoted comments

Hi @triangulum. As you can see

https://github.com/nicohaenggi/SafariBooks-Downloader.git:refs/heads/master

Tells us you are on nicohaenggi repository, and on master branch. As my PR is not merged yet, you need to pull my fork here and git checkout dev to make sure you are on the current development branch.

You will then need to reinstall using npm uninstall safaribooks-downloader && npm -g install in the fork directory. A simple way of making sure you have the right version is to add a --debug flag to your safaribooks-downloader previous command.

If it runs and print some debugging info about HTTP request, you made it right, if not, answer here for more assistance.

+10

hypr2771 on Dec 3, 2018

Hi guys, please refer to my pull request https://github.com/nicohaenggi/SafariBooks-Downloader/pull/40 . It is not yet merged, so meanwhile you can use my fork. Feel free to review the commits for your own security.

hypr2771 on Nov 26, 2018

I have finally merged @hypr2771 pull request #40 for fixing the 404 error. Thanks for the input @hypr2771 , I really do appreciate the help.

nicohaenggi on Jan 16, 2019

Hi,

@ElegantPercentage and @Rafaelj, did you install the tool globally before? I think you just need to trigger npm install -g on your checkout to ensure you are using the tool with the latest patches.

I tried fetching the changes of @hypr2771, and also experienced the same 404 issue. Tried using the -d flag where it complained that the option was unknown. So I figured it might be running the old version. Simply reinstalling the tool does the trick for me.

kendlee on Nov 30, 2018