auth.json token expired?

[Philip2809]

How long should the device registration live on? I registered the macless-haystack on the 30th of October and today it stopped working. Removing the auth.json and redoing the registration it now works again, any idea why and how long the auth.json is valid? The response from the fetch was empty and the json.loads was not able to parse the empty string the server sent.

[dchristl]

Hello,

that never runs out. I have had the same auth.json for more than 1 year. You may have removed the device from your Apple account or not used it for too long.

[supaeasy]

Every time I update anisette server I have to delete auth and re-enter Credentials/2FA. After that everything works fine but it gives the weirdest errors beforehand.

[dchristl]

Every time I update anisette server I have to delete auth and re-enter Credentials/2FA. After that everything works fine but it gives the weirdest errors beforehand.

Did you see the small edit in the readme of the docker command? (explanation) Recreating the Anisette container should solve your problem

[supaeasy]

I recreated it this way and now, for the first time there are files inside the mapped location. So I guess the problem will be gone from now on. Will see with the next update if this does the trick. Seems promising.

[supaeasy]

well, I just tested it: I have to delete auth.json and re-enter my credentials but 2FA ist not necessary anymore. Weird but at least I know the trick now.

[supaeasy]

I seem to have it working now for good. Tested this including purging and deleting images. Login data persists. I was using a different network than standard configuration before, maybe that was a problem though that would be strange. Maybe it also has something to do with the Synology DSM I am running it on; who knows? I felt like writing this down just in case anyone else has this problem. Was thinking about a pull request to the readme but don't really know where to put this or if this is appreciated. In the end this is just the standard confing from readme translated to a yaml and added "knowledge of the blank shell" for this specific usecase.

So for everyone using Synology DSM and Container Manager here is my docker-compose file that works fine for me. There is just 3 things to do in total:

• create a folder in a location of your choice with subfolders [name1] and [name2]
• create a new project in Container Manager using docker-compose.yaml below, replacing [name1] & [name2] with their filesystem location (format would be something like this example: /volume1/docker/mh/anisette) and start it
• Open macless-haystack project-> click macless-haystack -> in the upper right click open Terminal. A completely blank shell will open. Enter your AppleID and hit enter. Enter password and, when asked to, enter 2FA.

docker-compose.yaml

name: macless-haystack
services:
    anisette-v3-server:
        restart: unless-stopped
        container_name: anisette
        ports:
            - 6969:6969
        volumes:
            - [name1]:/home/Alcoholic/.config/anisette-v3
        image: dadoum/anisette-v3-server
        networks:
            - mh-network
    macless-haystack:
        stdin_open: true
        tty: true
        restart: unless-stopped
        container_name: macless-haystack
        ports:
            - 6176:6176
        volumes:
            - [name2]:/app/endpoint/data
        image: christld/macless-haystack
        networks:
           - mh-network

networks:
  mh-network: