search

dappnode / DNP_ADMIN

DAppNode tool responsible for providing the admin UI of DAppNode
http://admin.dappnode
GNU General Public License v3.0
7 stars 21 forks source link

Can not connect to my.dappnode #384

Closed bingen closed 4 years ago

bingen commented 5 years ago

The VPN seems to work fine, but when I try to connect to http://my.dappnode it doesn't work. I can ssh into it, and there I see that core container is constantly restarting:

dappnode@dappnode:~$ docker ps
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS                        PORTS                                                                                     NAMES
a89be56b69e6        ethchain.dnp.dappnode.eth:0.2.10      "entrypoint.sh"          16 hours ago        Up 15 hours                   0.0.0.0:30303->30303/tcp, 0.0.0.0:30303-30304->30303-30304/udp                            DAppNodeCore-ethchain.dnp.dappnode.eth
4f747d7fbd91        rinkeby.dnp.dappnode.eth:0.3.0        "/bin/sh -c 'geth --…"   16 hours ago        Up 15 hours                   30304/udp, 0.0.0.0:31313->30303/tcp, 0.0.0.0:31313->30303/udp, 0.0.0.0:31314->30304/tcp   DAppNodePackage-rinkeby.dnp.dappnode.eth
d237080b105c        core.dnp.dappnode.eth:0.2.13          "/usr/src/app/entryp…"   6 weeks ago         Restarting (1) 1 second ago                                                                                             DAppNodeCore-core.dnp.dappnode.eth
288ed86ddcd9        ethforward.dnp.dappnode.eth:0.2.3     "/bin/sh -c 'node /u…"   6 weeks ago         Up 15 hours                                                                                                             DAppNodeCore-ethforward.dnp.dappnode.eth
5b9abdfffb01        dappmanager.dnp.dappnode.eth:0.2.12   "/bin/sh -c /usr/src…"   7 weeks ago         Up 15 hours                                                                                                             DAppNodeCore-dappmanager.dnp.dappnode.eth
8f4bc43f4610        ipfs.dnp.dappnode.eth:0.2.4           "/sbin/tini -- /usr/…"   7 weeks ago         Up 15 hours                   5001/tcp, 0.0.0.0:4001->4001/tcp, 0.0.0.0:4002->4002/udp, 8080-8081/tcp                   DAppNodeCore-ipfs.dnp.dappnode.eth
e9f6ff9c040e        wifi.dnp.dappnode.eth:0.2.0           "/bin/wlanstart.sh"      8 weeks ago         Up 15 hours                                                                                                             DAppNodeCore-wifi.dnp.dappnode.eth
36daaf294157        admin.dnp.dappnode.eth:0.2.8          "nginx -c /etc/nginx…"   8 weeks ago         Up 15 hours                   80/tcp, 0.0.0.0:8090->8090/tcp                                                            DAppNodeCore-admin.dnp.dappnode.eth
117f32d3d23a        vipnode.dnp.dappnode.eth:0.1.0        "/bin/sh -c 'vipnode…"   2 months ago        Up 15 hours                                                                                                             DAppNodePackage-vipnode.dnp.dappnode.eth
b60f8679cc34        vpn.dnp.dappnode.eth:0.2.1            "./entrypoint.sh"        2 months ago        Up 15 hours                   0.0.0.0:1194->1194/udp                                                                    DAppNodeCore-vpn.dnp.dappnode.eth
3a7b65065141        bind.dnp.dappnode.eth:0.2.0           "entrypoint.sh"          2 months ago        Up 15 hours                   53/udp                                                                                    DAppNodeCore-bind.dnp.dappnode.eth
2ef80b122dc4        wamp.dnp.dappnode.eth:0.2.0           "crossbar start --cb…"   5 months ago        Up 15 hours                   8000/tcp, 8080/tcp                                                                        DAppNodeCore-wamp.dnp.dappnode.eth

Any idea on how to fix this?

vdo commented 5 years ago

The core container restarting has nothing to do here, but it's another issue we should have a look at.

Can you ping the DNS resolver? 

ping 172.33.1.2

Looks like this issue is happening again: https://github.com/dappnode/DNP_BIND/issues/22

bingen commented 4 years ago

Hi @vdo (and sorry for the delay again). Yes, I can consistently ping the DNS resolver.

(...)
--- 172.33.1.2 ping statistics ---
125 packets transmitted, 125 received, 0% packet loss, time 335ms
rtt min/avg/max/mdev = 0.468/0.935/5.653/0.493 ms

About connecting to http://my.admin.dnp.dappnode.eth or to http://my.dappnode/, it sometimes work (not often), intermittently, but it disconnects soon after, so I'm not able to do anything in the console.

bingen commented 4 years ago

The core container restarting has nothing to do here, but it's another issue we should have a look at.

Do you want me to open another issue? Which repo in? What additional info can I provide? I tried running docker logs and I only get messages like:

DAppNodeCore-bind.dnp.dappnode.eth is up-to-date
DAppNodeCore-ipfs.dnp.dappnode.eth is up-to-date
DAppNodeCore-ethchain.dnp.dappnode.eth is up-to-date
DAppNodeCore-ethforward.dnp.dappnode.eth is up-to-date
DAppNodeCore-vpn.dnp.dappnode.eth is up-to-date
DAppNodeCore-wamp.dnp.dappnode.eth is up-to-date
DAppNodeCore-dappmanager.dnp.dappnode.eth is up-to-date
DAppNodeCore-admin.dnp.dappnode.eth is up-to-date
DAppNodeCore-wifi.dnp.dappnode.eth is up-to-date
vdo commented 4 years ago

This issue seems to be on the client side, closing for now