# TOKEN\_SECRET\_NOT\_PROVIDED
### Why I'm seeing this[](http://localhost:3000/cli/errors/TOKEN_SECRET_NOT_PROVIDED#why-im-seeing-this)
The `token` or `secret` configured in `myjsblock.credentials.js` are invalid. When pushing a new version, the token or secret configured in `myjsblock.credentials.js` under `token` or `secret` was empty.
### How to fix it[](http://localhost:3000/cli/errors/TOKEN_SECRET_NOT_PROVIDED#how-to-fix-it)
Make sure the `token` and `secret` are stored in the `myjsblock.credentials.js` not to be confused with `myjsblock.config.js` file. This secret and token can be created in the [Appmachine Designer](https://design3.appmachine.com/) after adding a new 'Javascript' block.
More information about creating new tokens and secrets, see [create-new-token-secret](broken://pages/ANqrFI2o4koYa09NePcQ).
Your `myjsblock.credentials.js` for such a project should be:
```json
{
"token": "TJ9plldgQSL87dnK6ZIVpzTszlG3TPKo",
"secret": "ifb1kEBUYBJ17NSQWdBUNoTTU5O2d1jlTJ9plldgQSL87dnK6ZIVpzTszlG3TPKo"
}
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.appmachine.com/developers/javascript/cli/errors/token_secret_not_provided.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.