Geoff Bourne

...OK, I grabbed a new capture and only the body seems to indicate the rate limit. I was previously looking only at the headers, since that's where APIs like Github's...

I'll add a conditional on a phrase in the response body. It's a little cheesy and brittle, but better than being totally vague with a failure reason.

Thanks @TrueOsiris that would be easier than the instructions I currently provide to double up the dollar signs. I hadn't thought about looking [here](https://docs.docker.com/compose/environment-variables/env-file/) instead of [here](https://docs.docker.com/compose/compose-file/12-interpolation/).

@meltymon please check the same.

@meltymon home network/public or not doesn't make a difference. Please read (or re-read) this section and make sure you have doubled up **all three** dollar signs in the API key...

Must be the CueseForge imposed rate limit then.

> I have now generated a new API token, but that did not solve the problem. Are you totally sure you have escaped the dollar signs correctly? Your `CF_API_KEY` should...

> Speaking of the API limit, does it eat up an API call with every container restart? Yes. Even with the modpack already installed it has to make at least...

> Alright thanks, I will make sure to change my compose to not restart automatically. To clarify what I was trying to say: restart policy is fine once the container...

I'd say keep it simple and use specific limits rather than percentage based. Since I assume you're initially using a compose file, replace ``` JAVA_OPTS: "-Xms16G -Xmx64G" ``` with ```...