<![CDATA[Failed to install app: 409 message: Conflicting tcp port 7473]]>We are packaging another nostr relay for cloudron, the repo is here: https://git.nostrdev.com/stuff/cloudron-orly

This relay includes an embedded neo4j database. This requires enabling some additional ports.

The first deploy seems to be working smoothly.

However the second aborts as follows:

user@ft:~/git/cloudron-orly$ cloudron install -l mleku.ft.hn --image git.nostrdev.com/stuff/cloudron-orly@sha256:4e1fae78b22ce572d07b1c566b97623d948c98935e3c3de06f4b3ddd2e0adf30 
Port NEO4J_BROWSER_PORT: 7473
Port BOLT_BROWSER_PORT: 7687
Failed to install app: 409 message: Conflicting tcp port 7473

It seems to be possible to deploy in spite of this error if removing the "defaultValue" from the "tcpPorts" config. But then the UI appears borked.

Is there any way to have the tcpPort assigned (to the first available port, perhaps inside of a range) during the initial deploy?

How to deploy multiple instances of an app, that uses additional ports, using the CLI?

]]>https://forum.cloudron.io/topic/14656/failed-to-install-app-409-message-conflicting-tcp-port-7473RSS for NodeWed, 07 Oct 2026 18:16:45 GMTMon, 01 Dec 2025 21:42:41 GMT60<![CDATA[Reply to Failed to install app: 409 message: Conflicting tcp port 7473 on Mon, 01 Dec 2025 22:03:46 GMT]]>@nostrdev you can pass -p or --port-bindings to cloudron install . It will query it.

You can also pass directly using -p NEO4J_BROWSER_PORT=someportnumber,BOLT_BROWSER_PORT=anotherport .

]]>https://forum.cloudron.io/post/116315https://forum.cloudron.io/post/116315Mon, 01 Dec 2025 22:03:46 GMT