Exception in main error - failed to init p2p server

[aymxdd]

My problem

I installed the app normally from the app store but after many attempts to make the node run, I keep getting this error log in a loop:

monero_monerod_1    | 2024-10-24 09:49:23.770   I Monero 'Fluorine Fermi' (v0.18.3.3-release)
monero_monerod_1    | 2024-10-24 09:49:23.771   I Initializing cryptonote protocol...
monero_monerod_1    | 2024-10-24 09:49:23.771   I Cryptonote protocol initialized OK
monero_monerod_1    | 2024-10-24 09:49:23.774   I Initializing core...
monero_monerod_1    | 2024-10-24 09:49:23.774   I Loading blockchain from folder /home/monero/.bitmonero/lmdb ...
monero_monerod_1    | 2024-10-24 09:49:24.004   I Loading checkpoints
monero_monerod_1    | 2024-10-24 09:49:24.148   I Core initialized OK
monero_monerod_1    | 2024-10-24 09:49:24.148   I Initializing p2p server...
monero_monerod_1    | 2024-10-24 09:49:24.160   I Deinitializing core...
monero_monerod_1    | 2024-10-24 09:49:24.184   I Stopping cryptonote protocol...
monero_monerod_1    | 2024-10-24 09:49:24.184   I Cryptonote protocol stopped successfully
monero_monerod_1    | 2024-10-24 09:49:24.186   E Exception in main! Failed to initialize p2p server.

It seems that monerod is stuck in a restart loop. The UI of the app is also frozen in the "starting up" state with the layout skeleton displayed and no more info.

What I tried:

• Tweak settings (instant crash after restart)
• Fresh install with no settings changed (works for longer but ends up with the same problem once the chain is synced)
• Restarting the app
• Reinstalling the app
• Flush docker cache after app shutdown (docker system prune -a) then re-install the app
• Just wait it out for days

None of this worked.

My setup:

• Raspberry Pi 4b+
• umbrelOS 1.2.2
• port 18080 opened in my router's UPNP config for both UDP and TCP

[deverickapollo]

Thanks for providing a clear description of the problem. I've had two other reports and both were Raspberry Pi's so I suspect there is something specific to that deployment causing an issue. I'll start testing this soon and see what I find.