Peer keeps binding to random port

[KvThweatt]

So I can see the peer in my peerlist, but every time we get him to connect it binds to a new port, even tho it should be hardcoded and automatic?

Coin in question is Under The Table Coin, a Monero fork.

Even when using --add-peer <ip:port> or --add-exclusive-node it still chooses a random port, even if the port is specified.

Anyone know why this behavior is happening on a device outside my network, but my other laptop connects just fine within the network?

[vv181]

I hard to tell if you didn't specify your network configuration and/or give examples of the port your node bind to.

If you run the node over Tor, a node binding to some port on your local addresses is expected, and thus if you are connecting within the same local network, it may addressed to the correct specified port.

[KvThweatt]

The other issue I'm having is, about a month ago, one of my builds before I could get any peers to connect would let me send coins to addresses.

Now the wallet keeps responding with "No outputs found or daemon is not ready"

Any help?

We have miners on the network but it wont create any new transactions.

[vv181]

I don't have much experience regarding running monero-based/fork nodes, but I suspect the daemon is not ready may indicate your node isn't running successfully, either the daemon itself or maybe the RPC daemon. Again it's better if you also show some debug.log of your node, it should give better clarity about what is happening.

[KvThweatt]

2022-03-11 17:04:26.058 W Failed to connect to any of seed peers, continuing without seeds
2022-03-11 17:04:26.763 I HTTP [76.245.194.107] POST /json_rpc
2022-03-11 17:04:26.764 I [76.245.194.107:57917 INC] Calling RPC method get_txpool_backlog
2022-03-11 17:04:26.766 I HTTP [76.245.194.107] POST /json_rpc
2022-03-11 17:04:26.767 I [76.245.194.107:57917 INC] Calling RPC method getblockheadersrange

That's all my logs will show.

[vv181]

Can't help much about that. I think you should seek help from their community Discord server.

    Discord: https://discord.gg/HNfyxvRS3f

[KvThweatt]

That's my server lol. I'm the owner creator* of the coin.

Before I could get any nodes to sync, back when I was still trying to get the coin working I could send no problem.
Sometimes there wouldn't be enough outputs for ring size x but I never got the daemon not ready or no output errors.

[vv181]

That's my server lol. I'm the owner creator* of the coin.

Before I could get any nodes to sync, back when I was still trying to get the coin working I could send no problem.
Sometimes there wouldn't be enough outputs for ring size x but I never got the daemon not ready or no output errors.

XD You should've known better then.

Actually, I doubt that is the only log that shows unless you configure something about the logging code processes. I believe in setting some further configuration on the node/daemon config should make the log more informative, that way you should have more clarity about where was it wrong.

Refer to Monero Configuration File and Logging. Using a higher log level and then restarting the node should give you more info about the log.