Broken Dashboard

– This typically means WordPress trying to connect to the update server in the background, but couldn’t. This could be due to a simple internet connection issue, or may be the server is offline. This connectivity issue, which usually resolves itself after a while.
– If not, I strongly suggest you to contact your hosting provider.

Would I not be getting this error on all sites if it were an internet connection issue?

I flushed my dns in cmd and reset it, I am able to access other wordpress dashboards with ease?

Agreed it happens mostly because of slow internet connection, or php times out while connecting to the www.remarpro.com

I seem to only be getting this error on this site though. That could be why I dont think it is related to my internet. Also my internet speed download 34.10mbps and upload 15mbps and havent been dealing with any internet issues.

Identical errors on a fresh install.

Speed test for me shows near 100Mbps down 12Mbps up. Check your ping times instead of speeds. My issue was due to excessive ping times, not slow speeds.

EDIT:
Some more info to help. traceroute (tracert on some systems) shows why the error is happening for me (first few sensitive IPs removed):

root@server-hostname:~# traceroute -m 100 www.remarpro.com
traceroute to www.remarpro.com (198.143.164.252), 100 hops max, 60 byte packets
 1  X.X.X.X (X.X.X.X)  0.366 ms  0.449 ms  0.751 ms
 2  X-X-X-X.res.spectrum.com (X.X.X.X)  9.367 ms  9.459 ms  14.750 ms
 3  X-X-X-X.res.spectrum.com (X.X.X.X)  14.888 ms  14.992 ms  15.097 ms
 4  bundle-ether34.orld71-car1.bhn.net (71.44.61.11)  15.232 ms  15.349 ms  15.428 ms
 5  bu-14-tamp20-car1.bhn.net (71.44.1.210)  18.956 ms 072-031-067-217.res.spectrum.com (72.31.67.217)  20.109 ms  19.968 ms
 6  071-044-003-032.res.spectrum.com (71.44.3.32)  19.296 ms 071-044-003-024.res.spectrum.com (71.44.3.24)  13.135 ms 071-044-003-026.res.spectrum.com (71.44.3.26)  14.110 ms
 7  10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96)  22.072 ms bu-ether19.chctilwc00w-bcr00.tbone.rr.com (66.109.6.42)  22.177 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96)  24.257 ms
 8  66.109.9.140 (66.109.9.140)  42.846 ms  41.121 ms bu-ether17.hstqtx0209w-bcr00.tbone.rr.com (66.109.1.70)  42.809 ms
 9  107.14.19.49 (107.14.19.49)  42.950 ms ge-3-1-0.cr1.sea20.tbone.rr.com (66.109.6.90)  45.014 ms bu-ether12.dllstx976iw-bcr00.tbone.rr.com (66.109.6.39)  43.630 ms
10  209-18-43-77.dfw10.tbone.rr.com (209.18.43.77)  45.620 ms  46.458 ms  43.522 ms
11  equinix-dallas.dal2.us.voxel.net (206.223.118.164)  44.974 ms  45.145 ms  37.990 ms
12  bbr2.ae7.dal006.pnap.net (64.95.158.202)  38.609 ms  37.352 ms  43.454 ms
13  bbr1-xe-1-2-1.inapbb-chg-dal-1.chg.pnap.net (64.95.158.157)  67.849 ms  66.742 ms  67.610 ms
14  * * *
15  border2.ae2-bbnet2.chg.pnap.net (64.94.32.69)  52.179 ms border1.ae0-bbnet1.chg.pnap.net (64.94.32.4)  53.402 ms border2.ae2-bbnet2.chg.pnap.net (64.94.32.69)  52.196 ms
16  inapvoxcust-lag.border2.chg.pnap.net (64.94.34.70)  54.126 ms  54.013 ms inapvoxcust-lag.border1.chg.pnap.net (64.74.106.114)  54.595 ms
17  agg2.c13.r03.s101.chi03.singlehop.net (108.178.47.245)  53.306 ms agg1.c13.r03.s101.chi03.singlehop.net (108.178.47.247)  46.785 ms agg2.c13.r03.s101.chi03.singlehop.net (108.178.47.245)  47.645 ms
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *
65  * * *
66  * * *
67  * * *
68  * * *
69  * * *
70  * * *
71  * * *
72  * * *
73  * * *
74  * * *
75  * * *
76  * * *
77  * * *
78  * * *
79  * * *
80  * * *
81  * * *
82  * * *
83  * * *
84  * * *
85  * * *
86  * * *
87  * * *
88  * * *
89  * * *
90  * * *
91  * * *
92  * * *
93  * * *
94  * * *
95  * * *
96  * * *
97  * * *
98  * * *
99  * * *
100  * * *

I’m in central FL. My packets go to Orlando, then Tampa, then Texas, then a whole bunch in Chicago that either drop the packets or just take so long that my local WP install times out. The www.remarpro.com resolved IP also shows that the WP destination server is also in Chicago and also using the SingleHop network that seems to be the source of the problem.

Nothing we can personally do about it, and perhaps SingleHop should be notified to look into it.

• This reply was modified 3 years, 2 months ago by JP3. Reason: more details to help others diagnose

I’ve notified SingleHop and referenced this topic. Hopefully they are able to resolve it soon.

Working fine for me now. Check yours again tmw2591.

If it’s still not working yet, a few other things you can check that could be issues on your end are:

1.) Check WP settings and make sure the site address in wp-admin>settings>general is correct

2.) make sure php-curl is installed and enabled on the site that’s broken (php.ini will tell you)

3.) make sure that you can ping api.www.remarpro.com and the ping times are acceptable (100ms or less)

4.) make sure you can make actually make a secure connection to api.www.remarpro.com
openssl s_client -connect api.www.remarpro.com:443

5.) make sure your DNS resolving is happening properly. (/etc/resolv.conf for linux systems). My setup checks local DNS first, then a caching DNS server I have on my local network, then openDNS servers, and if all those fail I check google DNS servers last. Your setup will be different, but make sure IPs and order are correct.

6.) Confirm # 5 above with:
nslookup api.www.remarpro.com
and/or
dig api.www.remarpro.com

7.) Worst-case scenario (not recommended), you can manually add the IP for api.www.remarpro.com to your local hosts file (/etc/hosts for linux systems).

It could still be some other kind of uncommon server config errors, but if all of that checks out and you’re still getting the error, it very well could be an issue outside of your control like an issue with SingleHop’s network, WP servers, or anything in-between.

• This reply was modified 3 years, 2 months ago by JP3. Reason: fixed small typos