# TOKEN\_SECRET\_NOT\_VALID
### Why I'm seeing this.[](http://localhost:3000/cli/errors/TOKEN_SECRET_NOT_VALID#why-im-seeing-this)
The `token` or `secret` configured in `myjsblock.credentials.js` are not valid credentials. When pushing a new version, the token or secret configured in `myjsblock.credentials.js` under `token` or `secret` will be validated. You getting this if the `token` or `secret` are not passing the validation on the server.
### How to fix it.[](http://localhost:3000/cli/errors/TOKEN_SECRET_NOT_VALID#how-to-fix-it)
Make sure the `token` and `secret` are correctly stored in the `myjsblock.credentials.js`.
If so and you still getting this error. You can better create a new `token` and `secret`. This will also affect on all your other custom block projects using the `secret`.
For more information how to create a new token and secret see: [create-new-token-and-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_valid.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.