Explore.aepps.com doesn't seem to be working correctly


#1

How long does it take for the node which https://explore.aepps.com talks to to get updates?

fails to find an account:

Uncaught (in promise) Error: Error: While calling getAccountByPubkey (pubkey), GET to //roma-net.aepps.com/v2/accounts/ak_pyqhPTQEwgvo8866rBF2qhEqpM1ZsdVFe3rwgG7KCCDLEwxhw failed with 404: Account not found

but calling the api manually

iex([email protected])1> AE.fetch_account_info "ak_pyqhPTQEwgvo8866rBF2qhEqpM1ZsdVFe3rwgG7KCCDLEwxhw"
%{
  "balance" => 199959000,
  "id" => "ak_pyqhPTQEwgvo8866rBF2qhEqpM1ZsdVFe3rwgG7KCCDLEwxhw",
  "nonce" => 0
}

works fine.


#2

Ah, it seems like https://explore.aepps.com is using roma-net.aepps.com and my function uses main-net.aepps.com, what’s the difference?


#3

I’m also getting lots of CORS errors on the index page https://explorer.aepps.com/#/. https://explorer.aepps.com/#/status/ never fully loads the data either.


#4

Hey,

Our æpps team will get back to you as soon as possible.

Best,
Albena


#5

Aeternity main net is called roma-net. Maybe you were using https://sdk-mainnet.aepps.com/, this is on same network as https://roma-net.aepps.com, just different node.


#6

We had some issues with the node underlying Aeternity explorer failing. This is fixed now.


#7

Maybe the issue was due to failing of underlying node at that time. I am unable the reproduce the issue at present.


#8

Right, seems to be working fine now.

https://explorer.aepps.com/#/account/ak_pyqhPTQEwgvo8866rBF2qhEqpM1ZsdVFe3rwgG7KCCDLEwxhw loads now, but takes several seconds for me.


#9

when you view a generation, the web page will load by itself. This makes you impossible to view a specific generaion.