You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dsimog01 opened this issue
Sep 14, 2023
· 0 comments
· Fixed by #1640
Assignees
Labels
bugSomething isn't workingdockerTasks related to DockerethereumTasks related to the dappmanager core functionality EthereumP1Has to be done but not urgent
It seems that fullnode.dappnode domain does resolve to an IP, but it seems random as the IP is different for every user and the container to which it is attached resolves to packages that have nothing to do with the full node.
The ideal solution would be to implement a mechanism that creates one domain for each network, like <network>.fullnode.dappnode (mainnet.fullnode.dappnode, gnosis.fullnode.dappnode...). This domain should not be related to any container if the fullnode is not active for a specific network
The text was updated successfully, but these errors were encountered:
bugSomething isn't workingdockerTasks related to DockerethereumTasks related to the dappmanager core functionality EthereumP1Has to be done but not urgent
It seems that
fullnode.dappnode
domain does resolve to an IP, but it seems random as the IP is different for every user and the container to which it is attached resolves to packages that have nothing to do with the full node.The ideal solution would be to implement a mechanism that creates one domain for each network, like
<network>.fullnode.dappnode
(mainnet.fullnode.dappnode
,gnosis.fullnode.dappnode
...). This domain should not be related to any container if the fullnode is not active for a specific networkThe text was updated successfully, but these errors were encountered: