Invalid JWT generated during local cli crawls about a11ywatch HOT 3 CLOSED

Hi @GECORegulatory , thank you for the detailed report. At the moment if we use an API token a11ywatch --set-token $JWT the token used will not work if the instance was built on a different machine. If the token was signed on a build that uses docker a11ywatch start and afterwards a11ywatch start --standalone --local the machines used are different causing the token to be invalid.

Try to run cargo install a11ywatch_cli again to get the latest version 0.10.3 and run the command a11ywatch --clear-token. This will remove the token from the request. In order to get the token again a re-auth is needed from the machine used.

from a11ywatch.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

from a11ywatch.

This issue was closed because it has been stalled for 5 days with no activity.

from a11ywatch.