Closed dmce closed 6 years ago
Although i didnt want the db migration, when i copied the file nzbhydra.db file from v1 to a location accessible from v2 it worked
Oops sorry, I think I fucked that up with one of my latest updates. You can just delete the new DB file if you want to start with a fresh DB.
Am 05.02.2018 23:06 schrieb "David McElroy" notifications@github.com:
Although i didnt want the db migration, when i copied the file nzbhydra.db file from v1 to a location accessible from v2 it worked
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/113#issuecomment-363237414, or mute the thread https://github.com/notifications/unsubscribe-auth/ANtAeUnfAT6ygkZsB1BMx75JZlm2JN1Sks5tR3tqgaJpZM4R6Kvh .
Hey, its no problem. Feels nice and smooth now its going. Thanks.
Should work now.
Expected: Migrate Settings from v1 to v2. No .db Migrate (unchecked the last box) Setup: Docker containers for v1 and v2 (both from linuxserver). Copied v1 settings.cfg to folder available to v2 container (same location as v2 nzbhydra.yml). Searched: Looked for NullPointerException in Issues. Couldnt see it.