Skip to content

docs: clarify physical device requirement for new Apple IDs in FAQ #240

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.

Sign up for GitHub

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

Open
Paul-HenryP wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify physical device requirement for new Apple IDs in FAQ #240

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 17 additions & 3 deletions FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@

#### Where and what data is stored on the host?

During the installation, a Docker volume (*mh_data*) is created, which is located in the default folder. This is
During the installation, a Docker volume (_mh_data_) is created, which is located in the default folder. This is
normally under `/var/lib/docker/volumes/mh_data/_data`, but you can check, if your location is different, with:

```bash
docker inspect macless-haystack | grep mh_data
```

Check out the *Source*-key. The folder is typically protected and can only be accessed and modified by the root user.
Check out the _Source_-key. The folder is typically protected and can only be accessed and modified by the root user.

In the folder you'll find the configuration (config.ini), the authentication (auth.json), if it has already been
executed. Additionally, the self-signed certificate used for SSL is also located here.
Expand Down Expand Up @@ -171,6 +171,20 @@ container. If there is a file alongside certificate.pem (public key) called priv
used. The two files will be linked like that (Check out the folder and file-names)

```bash
sudo ln -s <path_to_private_key> /var/lib/docker/volumes/mh_data/_data/privkey.pem
sudo ln -s <path_to_private_key> /var/lib/docker/volumes/mh_data/_data/privkey.pem
sudo ln -s <path_to_public_key> /var/lib/docker/volumes/mh_data/_data/certificate.pem
```

### I get an error "Account limit reached" or "A server problem is blocking Apple ID sign in"

If you created a brand new Apple ID specifically for this project, the setup will fail during the iCloud initialization step. Apple's security policies require a new account to be initialized on a physical Apple device equipped with a Secure Enclave (Mac, iPhone, or iPad) before it can be used.

To resolve this:

1. Log into a physical Apple device with your new Apple ID.
2. Open the "Find My" application.
3. Accept the Terms and Conditions to properly initialize the iCloud storage.
4. Log out of the physical device.
5. Restart the macless-haystack setup.

Note: Activating the account via the Apple ID website or iTunes on Windows is not sufficient to bypass this restriction.