it feels like its kinda stuck in a loop. i start the docker, open the logs, authorize the twitch TV thing and then it starts all over again and wants to log in again.

even when i try to use my login settings in the run.py it askes for the twitch tv authorization...

and i really think its missing the 2fa...

Edited October 11, 2025Oct 11 by stFfn

i even tested removing my 2FA and it did not work :-/

twitch-drops-miner works without a flaw. i can log in and its farming drops. but this does not log in :(

Can maybe anyone of you guys give me your config and i try to use it, after i changed my twitch name in it?

should it load the webinterface even if its not loged in?

Edited October 12, 2025Oct 12 by stFfn

i think i know why its not working. the cookie folder is read only.. but i dont know why. i´ve set the folder in unraid to read write for everyone and in windows i did the same.

But that does not makse sense. i´ve created the .pk1 file manually and set the permissions for everyone and it still does not work and write the cookies...

Edited October 12, 2025Oct 12 by stFfn

ok, i got pissed of, uninstalled it all again and redid everything and now it works.. 0o

one more thing. does the Analytics web-server not work? i´ve opend the IP:5000 and it does not show any website.

Edited October 12, 2025Oct 12 by stFfn

Glad that it works, have you activated the analytics server in the run.py? I think in the template it is commented out per default.

twitch_miner.analytics(host="0.0.0.0", port=5000, refresh=5, days_ago=7)   # Start the Analytics web-server

Here are my user rights on the folders. The app created them itself, so i just created the folder as in the Before install and started the app:

/mnt/user/appdata/twitch-miner-v2# ls -la
total 12
drwxrwxrwx 1 root   root     52 Sep 24 21:24 ./
drwxrwxrwx 1 nobody users   376 Sep 25 23:41 ../
drwxr-xr-x 1 nobody users    16 Sep 24 21:25 analytics/
drwxr-xr-x 1 nobody users    24 Sep 24 21:26 cookies/
drwxr-xr-x 1 nobody users   346 Oct 12 03:07 logs/
-rwxrwxrwx 1 root   root  10210 Sep 29 22:35 run.py*

7 hours ago, Skylinar said:

Glad that it works, have you activated the analytics server in the run.py? I think in the template it is commented out per default.

twitch_miner.analytics(host="0.0.0.0", port=5000, refresh=5, days_ago=7)   # Start the Analytics web-server

Ah yes. thx. i forgott that i redid the config and did not delete the # :D

Does the twitch points docker give you a fake view count too? Asking for a friend ;)

Edited October 15, 2025Oct 15 by z0ki

Hi, What is the process to upgrade to the postgresql 18 container from an earlier version? I have version 15, can I just dump all the databases and then import them back into the new one and rename the same appdata folder?

Hi, basically a dump is enough, but I backup the appdata folder on top of it to have a double layer backup.

My steps are:

1. I stop the container, in appdata I copy the pg-data folder to have another backup.

2. make a db dump and save it on your server (keep in mind to start the container before)

   mkdir -p /mnt/user/YOUR_BACKUP_SHARE/db-dumps/YOUR_CONTAINER_NAME
   NOW=$(date +"%Y-%m-%d_%H-%M-%S")
   docker exec CONTAINER_NAME pg_dump -U DB_USERNAME -d DB_NAME > /mnt/user/YOUR_BACKUP_SHARE/db-dumps/CONTAINER_NAME/${NOW}_dump.sql

3. now stop the old pgsql container and install the new one, I pass the db user, db password, db name directly as environment variables, if you do not do this, you will need to create the db user(s) and db's on your own.

4. after startup I apply the dump

   docker exec -i PGSQL18_CONTAINER_NAME psql -U DB_USERNAME -d DB_NAME < /mnt/user/YOUR_BACKUP_SHARE/db-dumps/CONTAINER_NAME/DUMP_FILENAME.sql
   

Thats it, have fun.

7 hours ago, Skylinar said:

Hi, basically a dump is enough, but I backup the appdata folder on top of it to have a double layer backup.

My steps are:

1. I stop the container, in appdata I copy the pg-data folder to have another backup.

2. make a db dump and save it on your server (keep in mind to start the container before)

   mkdir -p /mnt/user/YOUR_BACKUP_SHARE/db-dumps/YOUR_CONTAINER_NAME
   NOW=$(date +"%Y-%m-%d_%H-%M-%S")
   docker exec CONTAINER_NAME pg_dump -U DB_USERNAME -d DB_NAME > /mnt/user/YOUR_BACKUP_SHARE/db-dumps/CONTAINER_NAME/${NOW}_dump.sql

3. now stop the old pgsql container and install the new one, I pass the db user, db password, db name directly as environment variables, if you do not do this, you will need to create the db user(s) and db's on your own.

4. after startup I apply the dump

   docker exec -i PGSQL18_CONTAINER_NAME psql -U DB_USERNAME -d DB_NAME < /mnt/user/YOUR_BACKUP_SHARE/db-dumps/CONTAINER_NAME/DUMP_FILENAME.sql
   

Thats it, have fun.

Thanks, this was really helpful and thorough. Just one other question, if I have multiple databases in the same postgresql container, I'm assuming I can just repeat this process for each one?

And do i need to do anything with the containers that use postgresql as a dependency (in my case authentik)? Like do i need to stop authentik before doing this dump? Or recreate the database in authentik?

I only use one postgres container for one database, because it is easier to do updates and dumps. In general I would suggest to stop every application that is using a DB, to have a static dataset while you are dumping. I think it is fine that you can repeat the steps for each database in your one pgsql container.

6 hours ago, Skylinar said:

I only use one postgres container for one database, because it is easier to do updates and dumps. In general I would suggest to stop every application that is using a DB, to have a static dataset while you are dumping. I think it is fine that you can repeat the steps for each database in your one pgsql container.

Worked perfectly! Thanks for your help and your work on this great container

Great to hear, have fun!