-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Received a naive datetime #8
Comments
@medoix the native datetime thingy is only a warning. The API key probably does not have the right for the APIs the plugin needs, especially if you are using them for another app. Webhooks in InvenTree and Shopify API access are not connected. To debug this I need more info - it is working for me on a brand-new install. Please post your inventree version information, deployment method and at what step of the instructions you are stuck. |
@matmair the custom app API key and shared secret has full permission access (everything selected). InvenTree version: 0.12.13 Installed via docker using docker-compose and the files here https://github.com/inventree/InvenTree/tree/master/docker/production I added the plugin to the polugins.txt file
I did raise a separate ticket because after the plugin was installed i was getting table errors so needed to manually run The
I have added full scoped API credentials into the Admin When i click on the button to test the Webhooks it appears a webhook is created but i get the error shared in the ticket above ![]() |
@medoix are you sure you have set api key (API key), Api password (admin-api token) and API shared secret (secret API key) correctly? I have repeated the setup on docker and can not find an error. |
@medoix were you able to solve the problem by switching the keys? |
I spent some time trying to understand why my API key was not working but i believe that error message
[API] Invalid API key or access token (unrecognized login or wrong password)
is not correct and is being sent after the failure to parse the date when attempting to create the webhook.The text was updated successfully, but these errors were encountered: