Event JSON
{
"id": "68818c51285b28f18e092115ceff81231df614aa25e6262c94c39cefc664c18e",
"pubkey": "1b5e23f65570d7e4d0a6490b492c34e669a1558ef095b4cd13e54329cb546048",
"created_at": 1746190297,
"kind": 1,
"tags": [
[
"e",
"da21cb860b13ac24323da7d5cb70e76d4358d5c9bc860571330ef241e3935aa6",
"wss://relay.primal.net",
"root"
],
[
"e",
"8e4b89da3d07c707dfbf3683902805b66b81d8486843712052383b91c70c18b0",
"wss://relay.primal.net",
"reply"
],
[
"p",
"d49a9023a21dba1b3c8306ca369bf3243d8b44b8f0b6d1196607f7b0990fa8df",
"",
"mention"
],
[
"p",
"1b5e23f65570d7e4d0a6490b492c34e669a1558ef095b4cd13e54329cb546048",
"",
"mention"
],
[
"r",
"wss://a.nos.lol/"
],
[
"r",
"wss://aegis.relayted.de/"
],
[
"r",
"wss://asia.azzamo.net/"
],
[
"r",
"wss://btc.klendazu.com/"
],
[
"r",
"wss://nostr01.counterclockwise.io/"
],
[
"r",
"wss://purplepag.es/"
],
[
"r",
"wss://relayable.org/"
],
[
"r",
"wss://nostr-pr02.redscrypt.org/"
]
],
"content": "Ok, so connection isn't the issue. Next step is to check if it's related with the DNS (resolv the pool domain) or some port blocking in the router.\n\nWith a computer behind the route (use the same that bitaxe), could you try to resolv the pool domain? search for curl in case you want to test.\n\nI am not focusing in bitaxe configuration because you said that using another network, without any change, the bitaxe works.",
"sig": "9f4fdb230570a54ba8c38364c698e7fce2e0ac2e96161c57309c8268983fda5ae50af3aaf6f029015c78b77d0364bef2a8e01f736831facfdc663fa072833338"
}