Common Issues

Common issues

404 not found

This is usually a misspelling in the Get command.

HTTP Error 500.30 - ASP.NET Core app failed to start

This usually indicates that something is misspelled in the application.json file, or a “,” is missing in either connectionstrings or jsonwebtokens sections.

Unauthorized Missing Json Web Token

This usually comes if you attempt to use the webaddress server/v1/project_previews?connectionstringkey=integrationapi which required a JsonWebToken to process. Either use /v1/version, or change authentication method in the API.

Unauthorized The provided token is not intended for this audience, the AudienceClaim setting does not match with the Token.aud.

The scope used to generate the token is probably wrong, as it decides what AUD to use in the Token (and the Roles).

500 Internal Server Error

Check to see if the action is correct, found this when not providing ?connectionstringkey=

401 Unauthorized, Unauthorized The provided token is not valid, possibly due to expiration.

Request a new token and try again.

401 Unauthorized, Unauthorized The provided token does not contain a role with sufficient access

Make sure you have sufficient roles to perform the action you want to do. For instance DatabaseAlias.all.edit does not allow you to perform “Post” commands but only “Patch” commands.