You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a local installation running with MAMP Pro.
✅ I can login to the admin, everything is normal
✅ I can test graphql queries in the graphiql of craftql.
✅ Local mysql is running, php as well
What I can't: Run the curl command $ curl -H "Authorization: bearer TOKEN" -H "Content-type: application/json" -d '{"query":"{ helloWorld }"}' http://localdomain.test/api
It stopped working from one to another minute...
I even tried to add another token and run the curl command again.
Same error as described above.
Does somebody have an idea, where that could result from?
Stacktrace seems to show to a craftql thing as well.
I think it is related to these lines here:
From file: in /Users/USERNAME/Documents/github/my-craft/vendor/craftcms/cms/src/web/Controller.php
How could I suddenly not be authorized anymore?...
Thanks for any help, I really have no clue.
The text was updated successfully, but these errors were encountered:
Hi there
I experienced a very weird error. While developing suddenly my graphql endpoint would not work anymore.
I get an html returned saying things like:
I have a local installation running with MAMP Pro.
What I can't: Run the curl command
$ curl -H "Authorization: bearer TOKEN" -H "Content-type: application/json" -d '{"query":"{ helloWorld }"}' http://localdomain.test/api
It stopped working from one to another minute...
I even tried to add another token and run the curl command again.
Same error as described above.
Does somebody have an idea, where that could result from?
Stacktrace seems to show to a craftql thing as well.
I think it is related to these lines here:
From file:
in /Users/USERNAME/Documents/github/my-craft/vendor/craftcms/cms/src/web/Controller.php
How could I suddenly not be authorized anymore?...
Thanks for any help, I really have no clue.
The text was updated successfully, but these errors were encountered: