Init commands which start service processes have to be run in the background
Problem
When trying to deploy a dapp, it may sometimes not transition into the started state.
Solution
Each of the commands listed in the init section of the node has to finish its execution in order for the services to be treated as started. That's why commands that stay running, e.g. serving the API, have to be suffixed with an ampersand (&) to instruct the shell to put them into the background, e.g.
init:
- run:
args: ['/bin/bash', '-c', '/bin/run_web.sh 192.168.0.3 &']
Bad Default Listening Address
Problem
Many services in publicly available Docker images are configured to listen exclusively on the localhost address by default. This configuration renders them inaccessible when run on the Golem VPN.
Solution
To resolve this, modify the service's configuration or provide the necessary arguments to ensure they listen on 0.0.0.0.
Accessing Specific Ports through Outbound Network Connections
Problem
In the Creating Golem dApps article, it's outlined that when trying to access an address on a specific port like http://geth.golem.network:55555, you must include the port in the manifest file. If you only specify the address (e.g., http://geth.golem.network), it will default to connecting via port 80.
Solution
Ensure you specify the complete URL, including the port number.