ENS resolution

[nugaon]

⚠️ Support requests in an issue-format will be closed immediately. For support, go to Swarm's Discord.

Context

Bee 2.2.0

Summary

When I try to open my registered personal page on http://vps:1633/bzz/nugaon.eth I get 400 error.

Expected behavior

I can resolve the nugaon.eth address as so far.

Actual behavior

"time"="2024-09-13 15:37:30.887535" "level"="debug" "logger"="node/api" "msg"="resolve name: attempting to resolve string to address" "string"="nugaon.eth"
"time"="2024-09-13 15:37:30.887822" "level"="debug" "logger"="node/api/act_decryption_handler" "msg"="invalid path params" "error"="1 error(s) occurred: `address=nugaon.eth`: invalid name or bzz address: 1 error occurred:\n\t* failed parsing CID nugaon.eth err invalid cid: selected encoding not supported: could not parse\n\n"
"time"="2024-09-13 15:37:30.887974" "level"="error" "logger"="node/api/act_decryption_handler" "msg"="invalid path params" "error"="1 error(s) occurred: `address=nugaon.eth`: invalid name or bzz address: 1 error occurred:\n\t* failed parsing CID nugaon.eth err invalid cid: selected encoding not supported: could not parse\n\n"
"time"="2024-09-13 15:37:30.888239" "level"="debug" "logger"="node/api" "msg"="content length header not found"
"time"="2024-09-13 15:37:30.888468" "level"="info" "logger"="node/api" "msg"="api access" "ip"="X.X.X.X" "method"="GET" "host"="vps:1633" "uri"="/bzz/nugaon.eth/" "proto"="HTTP/1.1" "status"=400 "size"=240 "duration"="1.412272ms" "user-agent"="browser"

Steps to reproduce

open http://{hostName}:1633/bzz/nugaon.eth in the browser.

Possible solution

seemingly the problem caused by the newly introduced ACT feature