Issues with Blockscout 6.7.2 and Hyperledger Besu 24.5.2: Frontend Data Not Displaying and WebSocket Connection Failure

[gmba0212]

Hello,

I am currently testing an environment using Blockscout 6.7.2 and Hyperledger Besu 24.5.2. I have enabled the following APIs: NET, ETH, MINER, IBFT, WEB3, TXPOOL, DEBUG, ADMIN, TRACE. The block information is being stored correctly in the PostgreSQL database.

However, I am encountering the following issues and need assistance to resolve them:

Frontend Error Message:

"Something went wrong. Try refreshing the page or come back later."
No data is displayed on the screen
Console Log:

phoenix.mjs:867 WebSocket connection to 'ws://localhost/socket/v2/websocket?vsn=2.0.0' failed:
Backend Logs:
2024-07-10T07:37:18.283 application=indexer fetcher=block_catchup first_block_number=156 last_block_number=156 missing_block_count=1 shrunk=false [info] Index had to catch up.
2024-07-10T07:37:18.283 application=indexer fetcher=block_catchup [info] Checking if index needs to catch up in 2500ms.
2024-07-10T07:37:20.697 application=indexer fetcher=empty_blocks_to_refetch [info] Start sanitizing of empty blocks. Batch size is 100
2024-07-10T07:37:20.700 application=indexer fetcher=empty_blocks_to_refetch [info] Batch of empty blocks is sanitized
2024-07-10T07:37:22.819 application=indexer fetcher=block_catchup first_block_number=157 last_block_number=157 missing_block_count=1 shrunk=false [info] Index had to catch up.
2024-07-10T07:37:22.819 application=indexer fetcher=block_catchup [info] Checking if index needs to catch up in 2500ms.
2024-07-10T07:37:28.347 application=indexer fetcher=block_catchup first_block_number=158 last_block_number=158 missing_block_count=1 shrunk=false [info] Index had to catch up.
2024-07-10T07:37:28.347 application=indexer fetcher=block_catchup [info] Checking if index needs to catch up in 2500ms.
2024-07-10T07:37:30.700 application=indexer fetcher=empty_blocks_to_refetch [info] Start sanitizing of empty blocks. Batch size is 100
2024-07-10T07:37:30.703 application=indexer fetcher=empty_blocks_to_refetch [info] Batch of empty blocks is sanitized
2024-07-10T07:37:32.481 application=indexer fetcher=coin_balance_catchup count=20 error_count=20 [error] failed to fetch: :closed
From these logs, it appears that the backend container is having issues with the indexer catching up on blocks. Additionally, the WebSocket connection failure is causing the frontend to not display any data.

Could you please advise on how to resolve these issues? Let me know if you need any additional information.

Thank you.

[ekawibisono]

hello @gmba0212, what you use run blockscout method ? manualy or docker-compose ?

[gmba0212]

The issue was finally solved today! I set the IP settings of common-frontend.env to an external IP and the screen appears normally. thank you! -----Original Message----- From: "Ekacitta ***@***.***> To: ***@***.***>; Cc: ***@***.***>; ***@***.***>; Sent: 2024-08-06 (화) 02:58:40 (GMT+09:00) Subject: Re: [blockscout/blockscout] Issues with Blockscout 6.7.2 and Hyperledger Besu 24.5.2: Frontend Data Not Displaying and WebSocket Connection Failure (Discussion #10404) hello @gmba0212, what you use run blockscout method ? manualy or docker-compose ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[gmba0212]

The issue was finally solved today! I set the IP settings of common-frontend.env to an external IP and the screen appears normally. thank you! I used "docker compose -f (**.yaml) up -d" -----Original Message----- From: "Ekacitta ***@***.***> To: ***@***.***>; Cc: ***@***.***>; ***@***.***>; Sent: 2024-08-06 (화) 02:58:40 (GMT+09:00) Subject: Re: [blockscout/blockscout] Issues with Blockscout 6.7.2 and Hyperledger Besu 24.5.2: Frontend Data Not Displaying and WebSocket Connection Failure (Discussion #10404) hello @gmba0212, what you use run blockscout method ? manualy or docker-compose ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[alsenydiallo]

could you elaborate what IP setting of common-frontend.env did you set ? I am having the same issue

[benfunble]

NEXT_PUBLIC_API_HOST={externalIP}
NEXT_PUBLIC_STATS_API_HOST=http://{externalIP}:8080
NEXT_PUBLIC_APP_HOST={externalIP}
NEXT_PUBLIC_VISUALIZE_API_HOST=http://{externalIP}:8081

I resolved the issue by configuring the environment variables as follows: