1

Network error on setup page

When I open setup page in my account on my.nextdns.io I get this error - Network Error (see screenshot) and I can not change Linked IP to my current ip-address

7 replies

null
    • losnad
    • 3 yrs ago
    • Reported - view

    I think something is blocking api.nextdns.io (browser, add-on, another app like AdGuard)

    Try with another browser.

    Maybe take a look at this

    https://help.nextdns.io/t/m1hf6xk/network-error-get-accountsme-when-accessing-my-nextdns-io

    • Jenessa
    • 3 yrs ago
    • Reported - view

    Try to used browser Google chrome beta. I used it good work no error

    • lokman
    • 3 yrs ago
    • Reported - view

    use bromite

    • Viacheslav_Checherenko
    • 3 yrs ago
    • Reported - view

    I tryed in another browser - chrome on macos it still  getting error

     

    ping api.nextdns.io

    PING api.nextdns.io (104.26.1.148): 56 data bytes

    64 bytes from 104.26.1.148: icmp_seq=0 ttl=55 time=29.485 ms

    64 bytes from 104.26.1.148: icmp_seq=1 ttl=55 time=29.413 ms

    64 bytes from 104.26.1.148: icmp_seq=2 ttl=55 time=29.879 ms

    ^C

    --- api.nextdns.io ping statistics ---

    3 packets transmitted, 3 packets received, 0.0% packet loss

    round-trip min/avg/max/stddev = 29.413/29.592/29.879/0.205 ms

    ➜ ~ ping nextdns.io

    PING nextdns.io (172.67.72.46): 56 data bytes

    64 bytes from 172.67.72.46: icmp_seq=0 ttl=56 time=5.426 ms

    64 bytes from 172.67.72.46: icmp_seq=1 ttl=56 time=5.833 ms

    64 bytes from 172.67.72.46: icmp_seq=2 ttl=56 time=6.133 ms

    64 bytes from 172.67.72.46: icmp_seq=3 ttl=56 time=6.259 ms

      • Jenessa
      • 3 yrs ago
      • Reported - view

      Viacheslav Checherenko This problem may be caused by your router or internet service provider.

      • Jenessa
      • 3 yrs ago
      • Reported - view

      Viacheslav Checherenko you should contact your internet service providers

      • Hey
      • 3 yrs ago
      • Reported - view

      Viacheslav Checherenko You could try this on a VPN or your Carrier if your Carrier and ISP are different, that should give a better idea about how or why it could be blocked. If it works with your carrier you can connect to your WIFI and see if it still works, if it does that would mean your PC / Some Software on your PC is blocking it. That should really narrow down the possibilities. 

Login to reply

Content aside

  • 1 Likes
  • 3 yrs agoLast active
  • 7Replies
  • 437Views
  • 4 Following