Could not connect to fuel core server after reinstall cargo and fuelup

I was trying to fix this problem described in this topic^ but Faced into another issue

What I did is:

>>> which cargo                                                                                                                                                                         
>>> which fuelup                                                                                                                                                                        
>>> rm -rf ~/.cargo                                                                                                                                                                     
>>> rm -rf ~/.fuelup

>>> curl --proto '=https' --tlsv1.2 -sSf | sh
>>> rustup install stable       
>>> rustup update
>>> rustup default stable
>>> curl --proto '=https' --tlsv1.2 -sSf \ | sh

But anyway Error getting version string was still present

>>> fuelup show                                                                                                                                                                         12:45:26 
Default host: aarch64-apple-darwin
fuelup home: /Users/lidia/.fuelup

installed toolchains
latest-aarch64-apple-darwin (default)

active toolchain
latest-aarch64-apple-darwin (default)
  forc : 0.40.1
    - forc-client
      - forc-deploy : 0.40.1
      - forc-run : 0.40.1
    - forc-doc : 0.40.1
    - forc-explore : 0.28.1
    - forc-fmt : 0.40.1
    - forc-index : 0.16.2
    - forc-lsp : 0.40.1
    - forc-tx : 0.40.1
    - forc-wallet : 0.2.2
  fuel-core : Error getting version string
  fuel-indexer : Error getting version string

fuels versions
forc : 0.42

And all my test that previously was working started to fail with this error

thread 'local_tests::cancel_order_test::cancel_order_test' panicked at 'error: Could not connect to fuel core server.', /Users/lidia/.cargo/git/checkouts/fuels-rs-ce5f345b87bf4c50/70e531f/packages/fuels-test-helpers/src/

Hi there! @sway
I think we talked briefly about this in person!
Let me know if its still an issue so I can escalate it!


1 Like

Lets try to understand if you got the fuel-core binary in your PATH or not first.

Can you run fuel-core —help?
If that doesn’t work can you try ~/.fuelup/bin/fuel-core --help?

Also let’s try to list contents of ~/.fuelup/bin with ls ~/.fuelup/bin.
Finally, output of which fuel-core would be perfect to have.

If your problem is not installation/tooling related I will try to find someone from SDK or fuel-core teams so that we can work out your problem together.

Here is my output for all of commands

1 Like

I think I had the same issue!
My solution was to build fuel-core from source.

However its weird since you are on arm (my issue was on intel)

Hi there! @sway

It might be possible that you have a time machine backup from an x86_64 mac on an m1 macine?

I don’t think so, is there any way to check it?

Hi there!
Basically the issue is a mess between build

First check if you have multiple builds for the darwin architecture. For me, when I updated rust via rustup I would have two builds.

You could try that, let me know if it works for you.
This message comes from different problems. Some people solved it by custom building the bin, others just had to nuke the OS.

1 Like