Grant type refresh_token is not supported.

eveseat / seat

🌀✳️ SeAT: A Simple, EVE Online API Tool and Corporation Manager

https://eveseat.github.io/docs/

GNU General Public License v2.0

434 stars 142 forks source link

Grant type refresh_token is not supported. #837

Closed TimeSpeeding closed 2 years ago

TimeSpeeding commented 2 years ago

Hello,

Thanks for your working. This is an excellent system. When I was using the seat, I found there are a lot of failed jobs, most in characters queue. And the exception is Seat\Eseye\Exceptions\RequestFailedException: invalid_grant: Grant type refresh_token is not supported. in /var/www/seat/vendor/eveseat/eseye/src/Fetchers/GuzzleFetcher.php:208

Please help me with fixing this problem.

Best Regards, Zhu Yibin

veteranmina commented 2 years ago

Can you provide SeAT versions please?

TimeSpeeding commented 2 years ago

Can you provide SeAT versions please?

All are the latest version.

veteranmina commented 2 years ago

Is your client ID/secret set or has it been changed recently?

TimeSpeeding commented 2 years ago

Is your client ID/secret set or has it been changed recently?

I just set them yesterday since the developer register of EVE broken down before.

warlof commented 2 years ago

Ensure callback, client ID, client secret and app scopes are properly set. Seems Sso may return this error message for various unrelated issues.

TimeSpeeding commented 2 years ago

Ensure callback, client ID, client secret and app scopes are properly set. Seems Sso may return this error message for various unrelated issues.

Hi, I just checked the ID, callback, secret and the scopes are right. Is this a problem that my seat was using an IP address with http, but not https? The jobs still cannot passed. And this will disappear in the character tab.

warlof commented 2 years ago

Does callback setup in .env roughly match with the one into eve dev app? (including scheme, server and path?)

As of remind

http://example.com is not https://example.com
http://0.0.0.0 is not the same as http://example.com

TimeSpeeding commented 2 years ago

Does callback setup in .env roughly match with the one into eve dev app? (including scheme, server and path?)

As of remind

http://example.com is not https://example.com

http://0.0.0.0 is not the same as http://example.com

The callback in .env is same as the eve dev app, both http://*.*.*.*/auth/eve/callback

And it is not all jobs failed. Only several jobs (like contracts, roles, recent killmails) in character queue failed.

TimeSpeeding commented 2 years ago

I am trying to changing the url to a https domain. And I am sure that I changed settings correct. But the problem above did not fixed. I can get the data like the skill summary and employment history. But when I trying to query the contracts, the job failed. More details from Horizon here:

Is anyone can help me with this problem or help me to identify where the problem is?

warlof commented 2 years ago

Is there anything else than contract?

TimeSpeeding commented 2 years ago

Is there anything else than contract?

Roles, Recent(killmails), Notifications in character queue.

warlof commented 2 years ago

Was it v1 to v2 converted tokens? (SeAT prior to v4 was using v1, if you migrate to v4, they've been upgraded to v2)

TimeSpeeding commented 2 years ago

Was it v1 to v2 converted tokens? (SeAT prior to v4 was using v1, if you migrate to v4, they've been upgraded to v2)

Might be. But I just built the SeAT follow the SeAT Documentation > Manual Installation. Where can I find how to upgrade tokens to v2?

warlof commented 2 years ago

No need with that error, I just try to find the origin of your issue with no idea since it appears you're the only one experimenting this. How is SeAT installed? Are you using any non standard thing (including ESI endpoints)?

Is that for any characters or certains only?

TimeSpeeding commented 2 years ago

No need with that error, I just try to find the origin of your issue with no idea since it appears you're the only one experimenting this. How is SeAT installed? Are you using any non standard thing (including ESI endpoints)?

Is that for any characters or certains only?

Sorry for delay responding. I installed the SeAT by the guide of Manual Installation. All softwares are as the suggestions in that guide. For ESI, I choose all and the callback is my https domain.

I just test the system by myself, but all my 5 characters cannot been refreshed the token.

warlof commented 2 years ago

Can you try those ?

clear overall cache using php artisan seat:cache:clear and php artisan cache:clear
renew cached config with php artisan config:cache
renew cached routes with php artisan route:cache

bpvital commented 2 years ago

Just Fyi I had exactly same problem:

-installed latest SeAT (manual instalation) -Lots of failed jobs due to expired character tokens

the problem in my case was incorrect APP_URL in .env