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

Unable to use with gPodder 3.11.4 #33

Open
patrickuhlmann opened this issue Jul 11, 2024 · 2 comments
Open

Unable to use with gPodder 3.11.4 #33

patrickuhlmann opened this issue Jul 11, 2024 · 2 comments

Comments

@patrickuhlmann
Copy link

patrickuhlmann commented Jul 11, 2024

I tried to synchronize but got the following errors:

gpodder-1  | 2024/07/11 21:05:18 [fa9419552ab6/5mjlPUOo79-000001] "PUT http://localhost:3005/subscriptions/patrick/pc-101.home.json HTTP/1.1" from 172.19.0.1:32810 - 500 0B in 1.594257ms
gpodder-1  | 2024/07/11 21:05:18 error parsing device id: sql: no rows in result set

I used docker-compose with NO_AUTH=true. In gpodder under Preferences the gpodder.net when I clock "Upload local subscriptions" I get the following error: "Error while upload 500". I used username: patrick, password: unused and device name: xps13 and server: localhost:3005.

@oxtyped
Copy link
Owner

oxtyped commented Jul 15, 2024

Hi @patrickuhlmann

I think the instructions are not very clear for running on docker-compose but I think you're missing the creation of the user step (https://github.com/oxtyped/gpodder2go?tab=readme-ov-file#quickstart)

Even though NO_AUTH is set true, you will still need to create a user. The password you set will not matter in NO_AUTH mode, but you still have to fill something up.

If you have access to the binary, you can do the following

$ gpodder2go -d <path/to/g2g.db> accounts create <username> --email="<email>" --name="<display_name>" --password="<password>"

Or you can run it within your container itself.

Let me know if this helps!

I do recommend using the release binaries (or build from source) to run gpodder2go instead of docker as you don't really need any external depedencies.

I also think that we should perhaps have some kind of init container in the docker-compose example to create the user during first load.

@patrickuhlmann
Copy link
Author

I actually created the user patrick as you advised but it still didn't work.

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