Private Ethereum Node is unable to add peers - blockchain

Question

My genesis file (used same for both nodes)
"config": {
"chainId": 42,
"homesteadBlock": 0,
"eip150Block": 0,
"eip150Hash": "0x0000000000000000000000000000000000000000000000000000000000000000",
"eip155Block": 0,
"eip158Block": 0,
"byzantiumBlock": 0,
"constantinopleBlock": 0,
"petersburgBlock": 0,
"istanbulBlock": 0,
"ethash": {}
},
"nonce": "0x0",
"timestamp": "0x62c17562",
"extraData": "0x0000000000000000000000000000000000000000000000000000000000000000",
"gasLimit": "0x47b760",
"difficulty": "0x80000",
"mixHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
"coinbase": "0x0000000000000000000000000000000000000000",
"alloc": {
"0000000000000000000000000000000000000000": {
"balance": "0x1"
},
"0000000000000000000000000000000000000001": {
"balance": "0x1"
},
"0000000000000000000000000000000000000002": {
"balance": "0x1"
},
"0000000000000000000000000000000000000003": {
"balance": "0x1"
},
"0000000000000000000000000000000000000004": {
"balance": "0x1"
},
My .sh file for node 1
geth --identity "miner1" --networkid 42 --mine --datadir "~/RPI/miner1" --nodiscover --http --http.port "8042" --port "30303" --http.corsdomain "*" --nat "any" --http.api db,eth,web,web3,private,miner,admin,txpool,debug,personal,net --allow-insecure-unlock --unlock 0 --password ~/RPI/password.sec --ipcpath "~/.ethereum/geth.ipc"
for node 2:
geth --identity "miner2" --networkid 42 --datadir "~/RPI/miner2" --mine --nodiscover --http --http.port "8043" --port "30304" --http.corsdomain "*" --nat "any" --http.api db,eth,web,web3,private,miner,admin,txpool,debug,personal,net --allow-insecure-unlock --unlock 0 --password ~/RPI/password.sec --ipcpath "~/.ethereum/geth.ipc"
I have tried using admin.addPeer but always returns [] tried another method by adding static-nodes.json file but didn't work either.
content of my static-nodes.json:
[
“enode://f9d48547c373fd61124d110791168572382298979d18ab5d6314cd399538ef77b8ff826b870a3474ad351f175b6d4d6f03c09ab4382b4d075e6a3c7fdeee58aa#35.247.47.68:30303?discport=0”,
“enode://991f8279ae27e665151621a9940b42e208bb7cda0108c3cda219059bed28fbb7ec869b04db84d173fbb1cecdce5fef222d010f02a90238e7d8a53b163f6b0a2a#34.105.65.4:30304?discport=0”
]
One thing that I noticed which was very peculiar was mode info:
id: "1fdd33dee80b18a109b51e083ab05fe70d98a2c80d55da9c8679b412a438e180",
ip: "127.0.0.1",
listenAddr: "[::]:30303",
name: "Geth/miner1/v1.10.20-stable-8f2416a8/linux-amd64/go1.18.1",
ports: {
discovery: 0,
listener: 30303
},
protocols: {
eth: {
config: {
byzantiumBlock: 0,
chainId: 42,
constantinopleBlock: 0,
eip150Block: 0,
eip150Hash: "0x0000000000000000000000000000000000000000000000000000000000000000",
eip155Block: 0,
eip158Block: 0,
ethash: {},
homesteadBlock: 0,
istanbulBlock: 0,
petersburgBlock: 0
},
difficulty: 147322604,
genesis: "0xd3ad0f15c44cf0543e7cccce24ce94024026b14a547428f1df6d9d89ab1d6fe7",
head: "0x82714efde94e31b659b232a62a88beb9be1d1cc9a8846f7bde6781276b35ec89",
network: 42
},
snap: {}
}
For some reason in both nodes my discovery ports is set to 0 I feel like that could be the issue but have not been able to find the way to change it. I was under the impression when you set ports both discovery and listener are set to that value.
If that is not the issue then I have no idea what it could be.