balena os configure fails with "This service may not be available in the `us-east-1' region."

openBalena
1

We have an Open Balena server running. I have configured balena CLI to use it in ~/.balenarc.yml.

If I want to configure an OS image, I run the following command, which fails:

$ balena os configure --debug --config-network ethernet --fleet admin/pts-cctv-chipsee-7inch-test test-img 
[debug] new argv=[/home/tue/balena-cli/balena,/snapshot/balena-cli/bin/balena,os:configure,--config-network,ethernet,--fleet,admin/pts-cctv-chipsee-7inch-test,test-img] length=8
[debug] Deprecation check: 0.18098 days since last npm registry query for next major version release date.
[debug] Will not query the registry again until at least 7 days have passed.
[debug] Event tracking error: getaddrinfo ENOTFOUND data.balena.r2p.com
BalenaRequestError: Request error: Inaccessible host: `resin-production-img-cloudformation.s3.amazonaws.com' at port `undefined'. This service may not be available in the `us-east-1' region.

BalenaRequestError: Request error: Inaccessible host: `resin-production-img-cloudformation.s3.amazonaws.com' at port `undefined'. This service may not be available in the `us-east-1' region.
    at Object.<anonymous> (/snapshot/balena-cli/node_modules/balena-sdk/node_modules/balena-request/build/request.js:193:27)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/balena-cli/node_modules/balena-sdk/node_modules/tslib/tslib.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

For further help or support, visit:
https://www.balena.io/docs/reference/balena-cli/#support-faq-and-troubleshooting

This has worked previously, and as far as I know, nothing on the Open Balena server has changed.

The device is of the type “raspberrypicm4-ioboard”.

I am using balena CLI version 14.5.12.

Any good suggestions for getting this to work again are more than welcome.

2

Hi,

Welcome back! The above host (resin-production-img-cloudformation.s3.amazonaws.com) seems to work as expected. This might very well be related to your network setup for open-balena server or network/server/service/region/data center outage from AWS end. The latter has been reported with similar errors multiple times. AWS provides a dashboard to get health reports of the services offered and the same is available at this link(https://status.aws.amazon.com/). API to access the services’ health is also available.

I would start with server network. Hope this helps. The SDK error message is misleading in the sense that it points to service not existing; but is more of reachability issue.

3

Thanks for the input. Looks like the nftables on our server got updated at one point, which caused the issue. We are up running again.