How to monitor your testnet node? (GraphQL throws 405 error)

Community
1

I’ve got my testnet node running and I think I figured out how the node’s privatekey gets associated with a wallet (import into a wallet but prefix the secret with “0x”).

But the URL to graphql throws a 405 error (I have to use the public IP of my node in the URL because it’s on a VPS)

Is there a way I can just view sync status, etc from the command line?

2

may I ask how did you start your node ? in your logs you should see these “downloading logs” messages if your node is syncing

2024-03-26T17:50:25.104804Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566091..=5566121
2024-03-26T17:56:50.122987Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566122..=5566151
2024-03-26T18:03:15.149142Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566152..=5566179
2024-03-26T18:09:40.401280Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566180..=5566208
2024-03-26T18:16:05.900557Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566209..=5566237
2024-03-26T18:22:40.449932Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566238..=5566268
2024-03-26T18:28:55.537489Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566269..=5566297
2024-03-26T18:35:15.703916Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566298..=5566324
2024-03-26T18:41:40.741418Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566325..=5566354
2024-03-26T18:48:05.824962Z  INFO new{name=Fuel_Node2}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5566355..=5566385
3

Yes, that’s what I see and continue to see.

I’ve since found out that the documentation on setting up the test node says to point at

http://0.0.0.0:4000/graphql

when it should be

http://0.0.0.0:4000/playground
1 Like
4

Hey @markjr, just a heads up, http://0.0.0.0:4000/playground serves as a convenient UI for experimenting with the main endpoint at http://0.0.0.0:4000/graphql. :slight_smile:

1 Like