DAppNode: Sometimes nginx can not connect to ws backend after updating #191
Comments
TripleSpeeder
added
bug
DAppNode
|
Currently DAppNode does not support additional networks. We need to wait for dappnode/DNP_DAPPMANAGER#618 to be implemented. |
|
@TripleSpeeder issue done ❤️ . Please watch this release to include it https://github.com/dappnode/DNP_DAPPMANAGER/milestone/6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Observed behaviour:
Sometimes after re-installing or updating the node package there are errors in the
webservice logs that indicate nginx can not connect to the profile service running in thewscontainer.According to the logs, the
webservice tries to connect towsat its previous IP-address.Workaround:
Restart the
webservice. After restart it connects to the correct IP-address.Possible solution:
Currently all brightID-node services connect to the default docker network of dappnode. We should create a dedicated virtual network for the brightid-node services. Within this network DNS resolution should work correctly.
The text was updated successfully, but these errors were encountered: