Backendless Support
 
Cannot Reproduce

Cant login to Backendless Dashboard

The website homepage loads fine but once I click the login button I get a "can't find server error".

Leave a Comment

Comments (5)

photo
1

Hi Chris,

What browser are you using? Have you tried googling the text of the error message? I just checked and the login works fine for me and the system is currently stable, too: http://status.backendless.com/

photo
1

I'm using the Safari, same as I always do. Its working for me now but the response time is really slow. If I try to manually update a value through the data tab I click and type and have to wait a few seconds for my typing to register on screen. I just clocked my internet speed at 8 Mbps, not blazing fast but should be plenty for what I'm doing. Definitely something going on today...

photo
1

Hi Chris,

Could you please try running ping and traceroute against develop.backendless.com and api.backendless.com to see what the response time/routing looks like? Please post the commands output here.

Regards,

Mark

photo
1

Traceroute has started…

traceroute to api.backendless.com (149.56.79.124), 64 hops max, 72 byte packets

1 royals.3strikesnetwork.com (74.203.78.129) 14.485 ms 20.905 ms 1.344 ms

2 66-162-72-213.static.twtelecom.net (66.162.72.213) 8.657 ms 2.461 ms 5.868 ms

3 ae2-100g.ar7.chi2.gblx.net (204.246.244.134) 959.422 ms * *

4 * * *

5 * ae-2-3601.ear3.newyork1.level3.net (4.69.150.206) 27.851 ms 40.531 ms

6 be100-104.nwk-1-a9.nj.us (192.99.146.253) 27.831 ms 44.410 ms 42.673 ms

7 be10-1037.bhs-g1-a9.qc.ca (192.99.146.99) 35.967 ms 48.960 ms 36.582 ms

8 vl21.bhs-g1-a75.qc.ca (198.27.73.63) 35.416 ms 35.684 ms 36.497 ms

9 be50-5.bhs-3b-a9.qc.ca (198.27.73.96) 318.034 ms * 365.028 ms

10 149.56.79.124 (149.56.79.124) 35.331 ms 51.175 ms 35.679 ms

Chriss-MacBook-Pro-3:stripeintegration Chris$ ping api.backendless.com

PING api.backendless.com (149.56.79.124): 56 data bytes

64 bytes from 149.56.79.124: icmp_seq=0 ttl=56 time=35.278 ms

64 bytes from 149.56.79.124: icmp_seq=1 ttl=56 time=60.982 ms

64 bytes from 149.56.79.124: icmp_seq=2 ttl=56 time=37.538 ms

64 bytes from 149.56.79.124: icmp_seq=3 ttl=56 time=39.684 ms

64 bytes from 149.56.79.124: icmp_seq=4 ttl=56 time=41.824 ms

^C

--- api.backendless.com ping statistics ---

6 packets transmitted, 5 packets received, 16.7% packet loss

round-trip min/avg/max/stddev = 35.278/43.061/60.982/9.221 ms

Chriss-MacBook-Pro-3:stripeintegration Chris$ ping develop.backendless.com

PING api.backendless.com (149.56.79.124): 56 data bytes

64 bytes from 149.56.79.124: icmp_seq=0 ttl=56 time=37.605 ms

64 bytes from 149.56.79.124: icmp_seq=1 ttl=56 time=38.273 ms

64 bytes from 149.56.79.124: icmp_seq=2 ttl=56 time=37.109 ms

64 bytes from 149.56.79.124: icmp_seq=3 ttl=56 time=141.351 ms

64 bytes from 149.56.79.124: icmp_seq=4 ttl=56 time=37.265 ms

64 bytes from 149.56.79.124: icmp_seq=5 ttl=56 time=35.844 ms

64 bytes from 149.56.79.124: icmp_seq=6 ttl=56 time=35.557 ms

64 bytes from 149.56.79.124: icmp_seq=7 ttl=56 time=37.441 ms

64 bytes from 149.56.79.124: icmp_seq=8 ttl=56 time=37.148 ms

64 bytes from 149.56.79.124: icmp_seq=9 ttl=56 time=46.526 ms

64 bytes from 149.56.79.124: icmp_seq=10 ttl=56 time=38.079 ms

64 bytes from 149.56.79.124: icmp_seq=11 ttl=56 time=47.278 ms

64 bytes from 149.56.79.124: icmp_seq=12 ttl=56 time=50.089 ms

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

64 bytes from 149.56.79.124: icmp_seq=17 ttl=56 time=38.901 ms

64 bytes from 149.56.79.124: icmp_seq=18 ttl=56 time=46.638 ms

64 bytes from 149.56.79.124: icmp_seq=19 ttl=56 time=49.334 ms

64 bytes from 149.56.79.124: icmp_seq=20 ttl=56 time=53.127 ms

64 bytes from 149.56.79.124: icmp_seq=21 ttl=56 time=50.159 ms

64 bytes from 149.56.79.124: icmp_seq=22 ttl=56 time=56.467 ms

64 bytes from 149.56.79.124: icmp_seq=23 ttl=56 time=53.165 ms

64 bytes from 149.56.79.124: icmp_seq=24 ttl=56 time=36.981 ms

64 bytes from 149.56.79.124: icmp_seq=25 ttl=56 time=37.154 ms

64 bytes from 149.56.79.124: icmp_seq=26 ttl=56 time=36.637 ms

64 bytes from 149.56.79.124: icmp_seq=27 ttl=56 time=36.385 ms

64 bytes from 149.56.79.124: icmp_seq=28 ttl=56 time=37.650 ms

64 bytes from 149.56.79.124: icmp_seq=29 ttl=56 time=37.270 ms

64 bytes from 149.56.79.124: icmp_seq=30 ttl=56 time=36.364 ms

64 bytes from 149.56.79.124: icmp_seq=31 ttl=56 time=37.394 ms

^C

--- api.backendless.com ping statistics ---

32 packets transmitted, 28 packets received, 12.5% packet loss

round-trip min/avg/max/stddev = 35.557/45.114/141.351/19.589 ms

photo
1

The reason you're seeing slower response time is due to the packet loss as reported by ping. This is something your network provider should be able to explain. For instance, I just pinged develop.backendless.com and here's the result:

PING api.backendless.com (149.56.79.124): 56 data bytes

64 bytes from 149.56.79.124: icmp_seq=0 ttl=48 time=96.395 ms

64 bytes from 149.56.79.124: icmp_seq=1 ttl=48 time=100.312 ms

64 bytes from 149.56.79.124: icmp_seq=2 ttl=48 time=99.576 ms

64 bytes from 149.56.79.124: icmp_seq=3 ttl=48 time=98.391 ms

64 bytes from 149.56.79.124: icmp_seq=4 ttl=48 time=194.829 ms

64 bytes from 149.56.79.124: icmp_seq=5 ttl=48 time=102.531 ms

64 bytes from 149.56.79.124: icmp_seq=6 ttl=48 time=99.493 ms

64 bytes from 149.56.79.124: icmp_seq=7 ttl=48 time=104.695 ms

64 bytes from 149.56.79.124: icmp_seq=8 ttl=48 time=99.359 ms

64 bytes from 149.56.79.124: icmp_seq=9 ttl=48 time=97.543 ms

64 bytes from 149.56.79.124: icmp_seq=10 ttl=48 time=103.299 ms

^C

--- api.backendless.com ping statistics ---

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

round-trip min/avg/max/stddev = 96.395/108.766/194.829/27.318 ms

mark-pillers-macbook-pro-2:console mark$ traceroute develop.backendless.com

traceroute to api.backendless.com (149.56.79.124), 64 hops max, 52 byte packets

1 gatewaylogin.info (172.20.1.1) 14.775 ms 2.265 ms 12.345 ms

2 12.110.241.57 (12.110.241.57) 4.446 ms 2.484 ms 6.322 ms

3 12.246.137.141 (12.246.137.141) 8.196 ms 31.462 ms 6.702 ms

4 12.122.154.102 (12.122.154.102) 9.974 ms 8.884 ms 15.882 ms

5 cr2.la2ca.ip.att.net (12.122.154.65) 27.589 ms 50.511 ms 7.049 ms

6 ggr2.la2ca.ip.att.net (12.122.129.97) 5.722 ms 5.493 ms 10.981 ms

7 las-bb1-link.telia.net (80.239.193.213) 16.898 ms 15.595 ms 6.659 ms

8 nyk-bb1-link.telia.net (80.91.252.162) 127.985 ms

nyk-bb1-link.telia.net (62.115.120.240) 96.320 ms

nyk-bb4-link.telia.net (80.91.252.166) 101.993 ms

9 nyk-b2-link.telia.net (62.115.134.108) 117.960 ms

nyk-b2-link.telia.net (213.155.130.30) 95.874 ms

nyk-b2-link.telia.net (62.115.134.108) 100.360 ms

10 be100-154.nwk-5-a9.nj.us (192.99.146.38) 90.647 ms 137.621 ms 95.519 ms

11 be10-1018.bhs-g2-a9.qc.ca (192.99.146.101) 106.190 ms 98.706 ms 100.081 ms

12 vl21.bhs-g2-a75-lo2.qc.ca (198.27.73.91) 94.701 ms 100.555 ms 112.651 ms

13 be50-7.bhs-3b-a9.qc.ca (198.27.73.98) 353.349 ms

be50-7.bhs-3a-a9.qc.ca (198.27.73.94) 299.611 ms 379.408 ms

14 149.56.79.124 (149.56.79.124) 99.905 ms 106.154 ms 101.421 ms