Login works successfully but all other commands result in "Your API Token is invalid."

[AndrewMast]

Forge CLI Version

1.8.3

PHP Version

8.3.26

Description

Running forge login --token=XXX works and results in ==> Authenticated Successfully As [XXX], but all other commands result in Your API Token is invalid. for me.

I had just downloaded the forge cli yesterday. I logged in, and then I was able to add a SSH key, but for some reason after the SSH was added to the server, the command failed.

And now every command results in Your API Token is invalid., even after creating new API tokens, logging in multiple times, logging out, uninstalling and reinstalling forge-cli.

I was able to sort of figure out what is wrong:

• When running forge login, my token is added to ~/.laravel-forge/config.json
• When running any other command, the config file is updated with a key that is only 985 characters, but does not match my key.

Decoding the token shows a token with zero scopes ([]) and expired yesterday:

I don't think I'll be doxxing myself, but I can provide the "token" that it always replaces my token with if needed.

Trying to edit the config file with my token always results in the token being replaced after every command run.

Steps To Reproduce

1. Install forge-cli with composer global require laravel/forge-cli
2. Log in with forge login --token=XXX
3. Run any other forge command, i.e. forge server:list

[AndrewMast]

Here is a video showing the whole issue.

error.mov

All tokens have been deleted :D

[brunogaspar]

Hello @AndrewMast

I've tried to reproduce the issue but sadly i could not. Followed the steps you've given, so it would match, but the token on my side stays intact, meaning, the scopes never change and the commands i execute works as expected.

Will see with the team if there are other ideas on what can be wrong.

[mathiasgrimm]

@AndrewMast can you run the following and let me know the result?

which forge

forge might be conflicting with Herd

Try running forge with the following and let me know if it works:

~/.composer/vendor/bin/forge

[AndrewMast]

Oh I didn't even think of that. Yes, which forge reveals /Users/andrew/Library/Application Support/Herd/bin//forge

[mathiasgrimm]

Bingo!

[AndrewMast]

Running ~/.composer/vendor/bin/forge login and then ~/.composer/vendor/bin/forge server:list does work. Currently testing to see if ssh configure messes it up agian.

Any idea why the Herd forge allows me to sign in (saved to ~/.laravel-forge/config.json) but then doesn't work in any other command?

[mathiasgrimm]

@AndrewMast Not sure. You might want to reach out to support@beyondco.de for that.
Are you using the latest version of Herd?

[AndrewMast]

Yes, latest Herd (1.22.3, build 55). I ended up "deleting" my Herd Forge integration and then recreating it. It created an api token with "0" scopes and no name on the Forge API page. I was able to ssh into the server with that as well.

Interesting. I'm going to see what I can do to fix the composer version, or maybe simply uninstall it to avoid conflicts. Thanks for the help @mathiasgrimm and @brunogaspar! I feel crazy for not checking which forge all this time haha.

[mathiasgrimm]

You're welcome, that's what we're here for!
Have an excellent day!

[AndrewMast]

Removing the composer forge messed up the herd forge again, but after some finagling with the ssh keys, I got it working again! For some reason it couldn't "reuse" keys so I had to delete and recreate.

One odd thing is even though both forge versions is 1.8.3, only the Herd one was using the newer laravel/prompts.

Maybe there could be a note on the Forge docs that adding the forge-cli via composer isn't needed if using Herd?

Really odd that the Herd forge cli stores the key in the same place as the composer one when using forge login, but it then uses the one stored via Herd in its config/integrations.plist for all the commands instead (and then resets the token in the composer location). Anyways, thanks again for helping me out! I'm closing this as resolved.