Hey I’m a relatively new person trying to build and work some stuff on Cardano, but trying to configure and setup blockfrost RYO on a local computer. I’m doing some on-chain analytics and know that I can run that cheaper on a local setup than on a paid tier of Blockfrost. I wrote a bunch of Blockfrost scripts and want to reuse them, hence building out the RYO node.
My computer is a NUC that meets the hardware requirements for db-sync and ryo. I’ve configured a node and db-sync (fully synced and can run postres queries on db-sync), but am lost on the final part of connecting the blockfrost ryo to it. In the logs below when I run the docker container for blockfrost it looks like I’m not connecting it properly.
The node and db-sync were configured using the guild operators basic walkthrough… Any help on where to find errors. If I try to run queries I get 500 errors so definitely something with the server config.
┌────┬───────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├────┼───────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ server │ default │ 2.0.0 │ cluster │ 36 │ 0s │ 0 │ online │ 0% │ 69.8mb │ undefin… │ disabled │
│ 1 │ server │ default │ 2.0.0 │ cluster │ 43 │ 0s │ 0 │ online │ 0% │ 69.9mb │ undefin… │ disabled │
│ 2 │ server │ default │ 2.0.0 │ cluster │ 50 │ 0s │ 0 │ online │ 0% │ 68.3mb │ undefin… │ disabled │
│ 3 │ server │ default │ 2.0.0 │ cluster │ 57 │ 0s │ 0 │ online │ 0% │ 69.3mb │ undefin… │ disabled │
│ 4 │ server │ default │ 2.0.0 │ cluster │ 68 │ 0s │ 0 │ online │ 0% │ 69.9mb │ undefin… │ disabled │
│ 5 │ server │ default │ 2.0.0 │ cluster │ 79 │ 0s │ 0 │ online │ 0% │ 67.7mb │ undefin… │ disabled │
│ 6 │ server │ default │ 2.0.0 │ cluster │ 86 │ 0s │ 0 │ online │ 0% │ 65.3mb │ undefin… │ disabled │
│ 7 │ server │ default │ 2.0.0 │ cluster │ 101 │ 0s │ 0 │ online │ 0% │ 60.6mb │ undefin… │ disabled │
│ 8 │ server │ default │ 2.0.0 │ cluster │ 112 │ 0s │ 0 │ online │ 0% │ 59.5mb │ undefin… │ disabled │
│ 9 │ server │ default │ 2.0.0 │ cluster │ 127 │ 0s │ 0 │ online │ 0% │ 56.7mb │ undefin… │ disabled │
│ 10 │ server │ default │ 2.0.0 │ cluster │ 134 │ 0s │ 0 │ online │ 0% │ 52.5mb │ undefin… │ disabled │
│ 11 │ server │ default │ 2.0.0 │ cluster │ 149 │ 0s │ 0 │ online │ 0% │ 50.2mb │ undefin… │ disabled │
└────┴───────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
[–no-daemon] Continue to stream logs
[–no-daemon] Exit on target PM2 exit pid=18
04:06:35 1|server | 2024-04-20T04:06:35: WARNING: NODE_APP_INSTANCE value of ‘1’ did not match any instance config file names.
04:06:35 1|server | 2024-04-20T04:06:35: WARNING: See Strict Mode · node-config/node-config Wiki · GitHub
04:06:35 6|server | 2024-04-20T04:06:35: WARNING: NODE_APP_INSTANCE value of ‘6’ did not match any instance config file names.
04:06:35 6|server | 2024-04-20T04:06:35: WARNING: See Strict Mode · node-config/node-config Wiki · GitHub
04:06:35 3|server | 2024-04-20T04:06:35: WARNING: NODE_APP_INSTANCE value of ‘3’ did not match any instance config file names.
04:06:35 4|server | 2024-04-20T04:06:35: WARNING: NODE_APP_INSTANCE value of ‘4’ did not match any instance config file names.
04:06:35 5|server | 2024-04-20T04:06:35: WARNING: NODE_APP_INSTANCE value of ‘5’ did not match any instance config file names.
04:06:35 2|server | 2024-04-20T04:06:35: WARNING: NODE_APP_INSTANCE value of ‘2’ did not match any instance config file names.