Camelot-Hosting down?

This is their reply:
"Clear your browser cache and flush your DNS site is up and running fine" having some issues with customers that cant handle this....

Clearing the DNS cache "only" isn't a magic fix (followed all the examples in the cPanel DNS cache clear instructions, and that didn't help).

But, if you still have the affected sites showing up as down clearing the "browser history for the last 2 days" (or something akin to that) should fix it.
That's what worked for me on several computers.

Until your customers do that, you may have some who get the "down" page unless they specifically change the URL by adding /index.php or something to it. But if they clear their browser history they should be fine.

Strictly speaking, this symptom is no longer a Camelot-specific issue.

I said clear your cache and site running,

This was all you having some issues with customers that cant handle this.... lol

just want to clarify cause that made me sound more of an Ogre than we all know I am LOL

For those that don't know how to flush your DNS. Go to your windows and in either command prompt or run type in ipconfig/flushdns then hit enter. Some will need to run it as administrator.

However the dns maybe working fine on there part but it still may take hours to fully populate down stream. Obviously everyone looking at each others sites can't be wrong. They are up one min and down the next and the same over different browsers. So, for the time being, it's just a waiting game.

Now the ssl issue Tony has posted that they are working on it or at least trying to.

So we wait and hope.

and people wonder why I have the firewalls set so tight

This is just TODAY ( had to shorten it by about 20K characters )

190.48.226.144 # lfd: (sshd) Failed SSH login from 190.48.226.144 (AR/Argentina/190-48-226-144.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 18:40:29 2017
201.254.75.249 # lfd: (sshd) Failed SSH login from 201.254.75.249 (AR/Argentina/201-254-75-249.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 18:41:34 2017
122.241.13.180 # lfd: (sshd) Failed SSH login from 122.241.13.180 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 18:42:39 2017
179.41.198.192 # lfd: (sshd) Failed SSH login from 179.41.198.192 (AR/Argentina/179-41-198-192.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 18:43:19 2017
95.39.170.153 # lfd: (sshd) Failed SSH login from 95.39.170.153 (ES/Spain/95.39.170.153.dyn.user.ono.com): 5 in the last 3600 secs - Sat Jul  8 18:43:30 2017
203.59.41.29 # lfd: (sshd) Failed SSH login from 203.59.41.29 (AU/Australia/203-59-41-29.perm.iinet.net.au): 5 in the last 3600 secs - Sat Jul  8 18:44:24 2017
113.92.215.74 # lfd: (sshd) Failed SSH login from 113.92.215.74 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 18:47:49 2017
42.159.251.248 # lfd: (sshd) Failed SSH login from 42.159.251.248 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 18:50:05 2017
179.190.125.159 # lfd: (sshd) Failed SSH login from 179.190.125.159 (BR/Brazil/-): 5 in the last 3600 secs - Sat Jul  8 18:50:05 2017
190.48.2.80 # lfd: (sshd) Failed SSH login from 190.48.2.80 (AR/Argentina/190-48-2-80.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 18:52:40 2017
219.92.70.231 # lfd: (sshd) Failed SSH login from 219.92.70.231 (MY/Malaysia/-): 5 in the last 3600 secs - Sat Jul  8 18:53:06 2017
27.195.90.56 # lfd: (sshd) Failed SSH login from 27.195.90.56 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 18:56:20 2017
186.72.115.232 # lfd: (sshd) Failed SSH login from 186.72.115.232 (PA/Panama/-): 5 in the last 3600 secs - Sat Jul  8 18:57:26 2017
77.40.35.117 # lfd: (sshd) Failed SSH login from 77.40.35.117 (RU/Russian Federation/117.35.pppoe.mari-el.ru): 5 in the last 3600 secs - Sat Jul  8 18:57:26 2017
119.193.140.166 # lfd: (sshd) Failed SSH login from 119.193.140.166 (KR/Korea, Republic of/-): 5 in the last 3600 secs - Sat Jul  8 19:00:35 2017
171.41.170.183 # lfd: (pop3d) Failed POP3 login from 171.41.170.183 (CN/China/-): 10 in the last 3600 secs - Sat Jul  8 19:01:20 2017
119.193.140.181 # lfd: (sshd) Failed SSH login from 119.193.140.181 (KR/Korea, Republic of/-): 5 in the last 3600 secs - Sat Jul  8 19:01:30 2017
190.6.184.118 # lfd: (sshd) Failed SSH login from 190.6.184.118 (CO/Colombia/adsl-car-118-184.ert.com.co): 5 in the last 3600 secs - Sat Jul  8 19:02:00 2017
119.36.212.26 # lfd: (sshd) Failed SSH login from 119.36.212.26 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:02:34 2017
2.62.165.244 # lfd: (sshd) Failed SSH login from 2.62.165.244 (RU/Russian Federation/2-62-165-244-bbc-dynamic.kuzbass.net): 5 in the last 3600 secs - Sat Jul  8 19:02:50 2017
218.156.85.17 # lfd: (sshd) Failed SSH login from 218.156.85.17 (KR/Korea, Republic of/-): 5 in the last 3600 secs - Sat Jul  8 19:03:20 2017
190.49.82.21 # lfd: (sshd) Failed SSH login from 190.49.82.21 (AR/Argentina/190-49-82-21.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 19:04:52 2017
181.67.143.53 # lfd: (sshd) Failed SSH login from 181.67.143.53 (PE/Peru/-): 5 in the last 3600 secs - Sat Jul  8 19:05:31 2017
103.79.141.175 # lfd: (sshd) Failed SSH login from 103.79.141.175 (VN/Vietnam/-): 5 in the last 3600 secs - Sat Jul  8 19:06:01 2017
49.66.124.212 # lfd: (sshd) Failed SSH login from 49.66.124.212 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:07:16 2017
220.245.251.44 # lfd: (sshd) Failed SSH login from 220.245.251.44 (AU/Australia/220-245-251-44.static.tpgi.com.au): 5 in the last 3600 secs - Sat Jul  8 19:07:21 2017
120.41.46.132 # lfd: (sshd) Failed SSH login from 120.41.46.132 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:09:06 2017
131.255.134.167 # lfd: (sshd) Failed SSH login from 131.255.134.167 (BR/Brazil/static-255-167.otinternet.com.br): 5 in the last 3600 secs - Sat Jul  8 19:09:21 2017
111.40.166.130 # lfd: (sshd) Failed SSH login from 111.40.166.130 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:09:46 2017
155.4.49.57 # lfd: (sshd) Failed SSH login from 155.4.49.57 (SE/Sweden/h-49-57.a185.priv.bahnhof.se): 5 in the last 3600 secs - Sat Jul  8 19:10:06 2017
88.249.106.23 # lfd: (sshd) Failed SSH login from 88.249.106.23 (TR/Turkey/88.249.106.23.static.ttnet.com.tr): 5 in the last 3600 secs - Sat Jul  8 19:10:21 2017
117.3.64.250 # lfd: (sshd) Failed SSH login from 117.3.64.250 (VN/Vietnam/-): 5 in the last 3600 secs - Sat Jul  8 19:11:16 2017
180.117.173.9 # lfd: (sshd) Failed SSH login from 180.117.173.9 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:12:11 2017
181.113.182.58 # lfd: (sshd) Failed SSH login from 181.113.182.58 (EC/Ecuador/58.182.113.181.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 19:13:36 2017
59.45.175.56 # lfd: (sshd) Failed SSH login from 59.45.175.56 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:13:51 2017
60.241.71.142 # lfd: (sshd) Failed SSH login from 60.241.71.142 (AU/Australia/60-241-71-142.static.tpgi.com.au): 5 in the last 3600 secs - Sat Jul  8 19:14:17 2017
181.211.152.51 # lfd: (sshd) Failed SSH login from 181.211.152.51 (EC/Ecuador/51.152.211.181.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 19:14:31 2017
59.45.175.86 # lfd: (sshd) Failed SSH login from 59.45.175.86 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:15:06 2017
59.45.175.67 # lfd: (sshd) Failed SSH login from 59.45.175.67 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:16:12 2017
42.7.26.55 # lfd: (sshd) Failed SSH login from 42.7.26.55 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:16:47 2017
59.45.175.88 # lfd: (sshd) Failed SSH login from 59.45.175.88 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:16:52 2017
121.18.238.125 # lfd: (sshd) Failed SSH login from 121.18.238.125 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:16:55 2017
59.45.175.66 # lfd: (sshd) Failed SSH login from 59.45.175.66 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:16:57 2017
221.194.47.242 # lfd: (sshd) Failed SSH login from 221.194.47.242 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:17:17 2017
110.17.2.157 # lfd: (sshd) Failed SSH login from 110.17.2.157 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:17:27 2017
190.48.140.108 # lfd: (sshd) Failed SSH login from 190.48.140.108 (AR/Argentina/190-48-140-108.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 19:18:52 2017
191.84.213.127 # lfd: (sshd) Failed SSH login from 191.84.213.127 (AR/Argentina/-): 5 in the last 3600 secs - Sat Jul  8 19:19:37 2017
151.16.237.143 # lfd: (sshd) Failed SSH login from 151.16.237.143 (IT/Italy/-): 5 in the last 3600 secs - Sat Jul  8 19:20:07 2017
126.24.181.207 # lfd: (sshd) Failed SSH login from 126.24.181.207 (JP/Japan/softbank126024181207.bbtec.net): 5 in the last 3600 secs - Sat Jul  8 19:20:37 2017
41.139.7.139 # lfd: (sshd) Failed SSH login from 41.139.7.139 (GH/Ghana/-): 5 in the last 3600 secs - Sat Jul  8 19:26:08 2017
222.179.189.206 # lfd: (sshd) Failed SSH login from 222.179.189.206 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:26:21 2017
27.29.69.65 # lfd: (pop3d) Failed POP3 login from 27.29.69.65 (CN/China/-): 10 in the last 3600 secs - Sat Jul  8 19:26:28 2017
72.81.254.63 # lfd: (sshd) Failed SSH login from 72.81.254.63 (US/United States/pool-72-81-254-63.bltmmd.fios.verizon.net): 5 in the last 3600 secs - Sat Jul  8 19:26:53 2017
60.146.122.183 # lfd: (sshd) Failed SSH login from 60.146.122.183 (JP/Japan/softbank060146122183.bbtec.net): 5 in the last 3600 secs - Sat Jul  8 19:27:33 2017
209.193.87.151 # lfd: (sshd) Failed SSH login from 209.193.87.151 (US/United States/209-193-87-151.mammothnetworks.com): 5 in the last 3600 secs - Sat Jul  8 19:28:08 2017
122.156.234.151 # lfd: (sshd) Failed SSH login from 122.156.234.151 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:28:28 2017
113.91.102.139 # lfd: (sshd) Failed SSH login from 113.91.102.139 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:29:18 2017
45.127.86.253 # lfd: (sshd) Failed SSH login from 45.127.86.253 (IN/India/-): 5 in the last 3600 secs - Sat Jul  8 19:29:48 2017
85.89.190.8 # lfd: (sshd) Failed SSH login from 85.89.190.8 (PL/Poland/staticline18577.toya.net.pl): 5 in the last 3600 secs - Sat Jul  8 19:30:43 2017
113.87.160.217 # lfd: (sshd) Failed SSH login from 113.87.160.217 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:31:28 2017
115.92.104.122 # lfd: (sshd) Failed SSH login from 115.92.104.122 (KR/Korea, Republic of/-): 5 in the last 3600 secs - Sat Jul  8 19:31:39 2017
80.25.21.76 # lfd: (sshd) Failed SSH login from 80.25.21.76 (ES/Spain/76.red-80-25-21.staticip.rima-tde.net): 5 in the last 3600 secs - Sat Jul  8 19:32:13 2017
181.196.168.76 # lfd: (sshd) Failed SSH login from 181.196.168.76 (EC/Ecuador/76.168.196.181.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 19:32:33 2017
59.175.144.100 # lfd: (sshd) Failed SSH login from 59.175.144.100 (CN/China/100.144.175.59.broad.wh.hb.dynamic.163data.com.cn): 5 in the last 3600 secs - Sat Jul  8 19:33:18 2017
200.120.182.80 # lfd: (sshd) Failed SSH login from 200.120.182.80 (CL/Chile/pc-80-182-120-200.cm.vtr.net): 5 in the last 3600 secs - Sat Jul  8 19:33:58 2017
178.45.106.38 # lfd: (sshd) Failed SSH login from 178.45.106.38 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 19:35:04 2017
201.178.200.237 # lfd: (sshd) Failed SSH login from 201.178.200.237 (AR/Argentina/201-178-200-237.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 19:36:04 2017
177.93.86.49 # lfd: (sshd) Failed SSH login from 177.93.86.49 (BR/Brazil/177-93-86-49.routeway.com.br): 5 in the last 3600 secs - Sat Jul  8 19:36:14 2017
94.157.93.82 # lfd: (sshd) Failed SSH login from 94.157.93.82 (NL/Netherlands/-): 5 in the last 3600 secs - Sat Jul  8 19:39:34 2017
190.214.66.242 # lfd: (sshd) Failed SSH login from 190.214.66.242 (EC/Ecuador/242.66.214.190.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 19:40:39 2017
181.64.148.56 # lfd: (sshd) Failed SSH login from 181.64.148.56 (PE/Peru/-): 5 in the last 3600 secs - Sat Jul  8 19:41:04 2017
175.166.198.20 # lfd: (sshd) Failed SSH login from 175.166.198.20 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:44:35 2017
221.194.47.236 # lfd: (sshd) Failed SSH login from 221.194.47.236 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:46:05 2017
24.145.70.60 # lfd: (sshd) Failed SSH login from 24.145.70.60 (US/United States/24-145-70-060-dhcp.mia.fl.atlanticbb.net): 5 in the last 3600 secs - Sat Jul  8 19:46:25 2017
46.13.98.182 # lfd: (sshd) Failed SSH login from 46.13.98.182 (CZ/Czech Republic/46-13-98-182.tmcz.cz): 5 in the last 3600 secs - Sat Jul  8 19:46:50 2017
78.186.146.224 # lfd: (sshd) Failed SSH login from 78.186.146.224 (TR/Turkey/78.186.146.224.static.ttnet.com.tr): 5 in the last 3600 secs - Sat Jul  8 19:47:05 2017
50.235.200.138 # lfd: (sshd) Failed SSH login from 50.235.200.138 (US/United States/50-235-200-138-static.hfc.comcastbusiness.net): 5 in the last 3600 secs - Sat Jul  8 19:48:45 2017
181.196.217.126 # lfd: (sshd) Failed SSH login from 181.196.217.126 (EC/Ecuador/126.217.196.181.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 19:48:50 2017
59.45.175.24 # lfd: (sshd) Failed SSH login from 59.45.175.24 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:50:45 2017
181.21.59.15 # lfd: (sshd) Failed SSH login from 181.21.59.15 (AR/Argentina/181-21-59-15.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 19:50:50 2017
190.48.119.39 # lfd: (sshd) Failed SSH login from 190.48.119.39 (AR/Argentina/190-48-119-39.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 19:51:05 2017
186.150.133.24 # lfd: (sshd) Failed SSH login from 186.150.133.24 (DO/Dominican Republic/ip-133-24.tricom.net): 5 in the last 3600 secs - Sat Jul  8 19:51:05 2017
94.78.221.145 # lfd: (sshd) Failed SSH login from 94.78.221.145 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 19:52:18 2017
119.193.140.173 # lfd: (sshd) Failed SSH login from 119.193.140.173 (KR/Korea, Republic of/-): 5 in the last 3600 secs - Sat Jul  8 19:52:40 2017
186.178.191.56 # lfd: (sshd) Failed SSH login from 186.178.191.56 (EC/Ecuador/56.191.178.186.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 19:53:35 2017
190.177.194.57 # lfd: (sshd) Failed SSH login from 190.177.194.57 (AR/Argentina/190-177-194-57.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 19:53:41 2017
94.51.73.216 # lfd: (sshd) Failed SSH login from 94.51.73.216 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 19:55:11 2017
175.152.79.249 # lfd: (sshd) Failed SSH login from 175.152.79.249 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:55:26 2017
97.97.162.10 # lfd: (sshd) Failed SSH login from 97.97.162.10 (US/United States/97-97-162-10.res.bhn.net): 5 in the last 3600 secs - Sat Jul  8 19:56:16 2017
153.34.109.60 # lfd: (sshd) Failed SSH login from 153.34.109.60 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 19:56:16 2017
146.151.108.35 # lfd: (sshd) Failed SSH login from 146.151.108.35 (US/United States/eagleheights-108-35.resnet.wisc.edu): 5 in the last 3600 secs - Sat Jul  8 19:56:21 2017
182.169.79.73 # lfd: (sshd) Failed SSH login from 182.169.79.73 (JP/Japan/pa94f49.fkoknt01.ap.so-net.ne.jp): 5 in the last 3600 secs - Sat Jul  8 19:59:56 2017
218.2.197.240 # lfd: (sshd) Failed SSH login from 218.2.197.240 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:00:12 2017
201.254.72.163 # lfd: (sshd) Failed SSH login from 201.254.72.163 (AR/Argentina/201-254-72-163.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:00:51 2017
73.65.117.87 # lfd: (sshd) Failed SSH login from 73.65.117.87 (US/United States/c-73-65-117-87.hsd1.mn.comcast.net): 5 in the last 3600 secs - Sat Jul  8 20:01:46 2017
202.114.159.186 # lfd: (sshd) Failed SSH login from 202.114.159.186 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:01:56 2017
181.211.136.245 # lfd: (sshd) Failed SSH login from 181.211.136.245 (EC/Ecuador/245.136.211.181.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 20:05:57 2017
60.12.119.222 # lfd: (sshd) Failed SSH login from 60.12.119.222 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:06:08 2017
95.188.180.47 # lfd: (sshd) Failed SSH login from 95.188.180.47 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 20:07:19 2017
31.162.98.200 # lfd: (sshd) Failed SSH login from 31.162.98.200 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 20:08:37 2017
170.84.91.51 # lfd: (sshd) Failed SSH login from 170.84.91.51 (BR/Brazil/-): 5 in the last 3600 secs - Sat Jul  8 20:09:12 2017
201.254.185.216 # lfd: (sshd) Failed SSH login from 201.254.185.216 (AR/Argentina/201-254-185-216.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:09:42 2017
197.46.52.48 # lfd: (sshd) Failed SSH login from 197.46.52.48 (EG/Egypt/host-197.46.52.48.tedata.net): 5 in the last 3600 secs - Sat Jul  8 20:10:47 2017
183.155.182.26 # lfd: (sshd) Failed SSH login from 183.155.182.26 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:10:55 2017
112.118.23.130 # lfd: (sshd) Failed SSH login from 112.118.23.130 (HK/Hong Kong/n11211823130.netvigator.com): 5 in the last 3600 secs - Sat Jul  8 20:10:57 2017
186.178.13.109 # lfd: (sshd) Failed SSH login from 186.178.13.109 (EC/Ecuador/109.13.178.186.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 20:12:12 2017
181.20.177.51 # lfd: (sshd) Failed SSH login from 181.20.177.51 (AR/Argentina/181-20-177-51.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:13:08 2017
94.244.151.72 # lfd: (sshd) Failed SSH login from 94.244.151.72 (UA/Ukraine/94.244.151.72.nash.net.ua): 5 in the last 3600 secs - Sat Jul  8 20:13:43 2017
117.71.18.20 # lfd: (sshd) Failed SSH login from 117.71.18.20 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:13:58 2017
182.243.97.102 # lfd: (sshd) Failed SSH login from 182.243.97.102 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:15:18 2017
190.48.114.20 # lfd: (sshd) Failed SSH login from 190.48.114.20 (AR/Argentina/190-48-114-20.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:15:53 2017
59.45.175.62 # lfd: (sshd) Failed SSH login from 59.45.175.62 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:18:03 2017
91.195.103.44 # lfd: (imapd) Failed IMAP login from 91.195.103.44 (CZ/Czech Republic/-): 10 in the last 3600 secs - Sat Jul  8 20:18:08 2017
5.188.11.11 # lfd: (imapd) Failed IMAP login from 5.188.11.11 (RU/Russian Federation/-): 10 in the last 3600 secs - Sat Jul  8 20:19:03 2017
78.192.107.9 # lfd: (sshd) Failed SSH login from 78.192.107.9 (FR/France/ran75-1-78-192-107-9.fbxo.proxad.net): 5 in the last 3600 secs - Sat Jul  8 20:19:13 2017
220.134.115.11 # lfd: (sshd) Failed SSH login from 220.134.115.11 (TW/Taiwan/220-134-115-11.hinet-ip.hinet.net): 5 in the last 3600 secs - Sat Jul  8 20:20:23 2017
95.83.63.190 # lfd: (sshd) Failed SSH login from 95.83.63.190 (RU/Russian Federation/95-83-63-190.saransk.ru): 5 in the last 3600 secs - Sat Jul  8 20:20:24 2017
103.79.143.175 # lfd: (sshd) Failed SSH login from 103.79.143.175 (VN/Vietnam/-): 5 in the last 3600 secs - Sat Jul  8 20:20:48 2017
91.197.232.103 # lfd: (sshd) Failed SSH login from 91.197.232.103 (CZ/Czech Republic/-): 5 in the last 3600 secs - Sat Jul  8 20:21:03 2017
73.205.5.224 # lfd: (sshd) Failed SSH login from 73.205.5.224 (US/United States/c-73-205-5-224.hsd1.fl.comcast.net): 5 in the last 3600 secs - Sat Jul  8 20:21:38 2017
94.74.127.210 # lfd: (sshd) Failed SSH login from 94.74.127.210 (UA/Ukraine/94.74.127.210.pool.breezein.net): 5 in the last 3600 secs - Sat Jul  8 20:22:59 2017
116.31.82.234 # lfd: (sshd) Failed SSH login from 116.31.82.234 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:24:39 2017
201.176.235.188 # lfd: (sshd) Failed SSH login from 201.176.235.188 (AR/Argentina/201-176-235-188.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:24:44 2017
184.173.145.197 # lfd: (cpanel) Failed cPanel login from 184.173.145.197 (US/United States/server11.camelot-hosting.com): 5 in the last 3600 secs - Sat Jul  8 20:25:04 2017
119.193.140.216 # lfd: (sshd) Failed SSH login from 119.193.140.216 (KR/Korea, Republic of/-): 5 in the last 3600 secs - Sat Jul  8 20:25:59 2017
61.135.4.186 # lfd: (sshd) Failed SSH login from 61.135.4.186 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:26:04 2017
181.22.36.65 # lfd: (sshd) Failed SSH login from 181.22.36.65 (AR/Argentina/181-22-36-65.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:26:14 2017
112.240.223.203 # lfd: (sshd) Failed SSH login from 112.240.223.203 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:27:49 2017
92.127.191.161 # lfd: (sshd) Failed SSH login from 92.127.191.161 (RU/Russian Federation/ws.92.127.191.161.nsk.sibirtelecom.ru): 5 in the last 3600 secs - Sat Jul  8 20:27:55 2017
94.51.59.214 # lfd: (sshd) Failed SSH login from 94.51.59.214 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 20:28:34 2017
186.130.67.36 # lfd: (sshd) Failed SSH login from 186.130.67.36 (AR/Argentina/186-130-67-36.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:28:44 2017
180.250.238.251 # lfd: (sshd) Failed SSH login from 180.250.238.251 (ID/Indonesia/-): 5 in the last 3600 secs - Sat Jul  8 20:29:03 2017
93.85.82.92 # lfd: (sshd) Failed SSH login from 93.85.82.92 (BY/Belarus/mail2.bdo.by): 5 in the last 3600 secs - Sat Jul  8 20:29:49 2017
190.214.66.104 # lfd: (sshd) Failed SSH login from 190.214.66.104 (EC/Ecuador/104.66.214.190.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 20:30:09 2017
190.97.70.90 # lfd: (sshd) Failed SSH login from 190.97.70.90 (CO/Colombia/adsl_dynamic-bug-90-70-97.ert.com.co): 5 in the last 3600 secs - Sat Jul  8 20:30:19 2017
138.99.167.175 # lfd: (sshd) Failed SSH login from 138.99.167.175 (BR/Brazil/138-99-167-175.zecnet.com.br): 5 in the last 3600 secs - Sat Jul  8 20:30:35 2017
78.182.254.117 # lfd: (sshd) Failed SSH login from 78.182.254.117 (TR/Turkey/78.182.254.117.dynamic.ttnet.com.tr): 5 in the last 3600 secs - Sat Jul  8 20:31:25 2017
123.150.200.121 # lfd: (sshd) Failed SSH login from 123.150.200.121 (CN/China/-): 5 in the last 3600 secs - Sat Jul  8 20:31:55 2017
181.113.211.135 # lfd: (sshd) Failed SSH login from 181.113.211.135 (EC/Ecuador/135.211.113.181.static.pichincha.andinanet.net): 5 in the last 3600 secs - Sat Jul  8 20:32:45 2017
43.240.117.230 # lfd: (sshd) Failed SSH login from 43.240.117.230 (HK/Hong Kong/-): 5 in the last 3600 secs - Sat Jul  8 20:34:20 2017
31.162.120.161 # lfd: (sshd) Failed SSH login from 31.162.120.161 (RU/Russian Federation/-): 5 in the last 3600 secs - Sat Jul  8 20:37:05 2017
178.234.176.208 # lfd: (sshd) Failed SSH login from 178.234.176.208 (RU/Russian Federation/X208.bbn07-176.lipetsk.ru): 5 in the last 3600 secs - Sat Jul  8 20:39:01 2017
78.158.210.156 # lfd: (sshd) Failed SSH login from 78.158.210.156 (UA/Ukraine/-): 5 in the last 3600 secs - Sat Jul  8 20:40:41 2017
186.130.64.157 # lfd: (sshd) Failed SSH login from 186.130.64.157 (AR/Argentina/186-130-64-157.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:41:56 2017
186.60.175.126 # lfd: (sshd) Failed SSH login from 186.60.175.126 (AR/Argentina/186-60-175-126.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:42:01 2017
186.57.142.105 # lfd: (sshd) Failed SSH login from 186.57.142.105 (AR/Argentina/186-57-142-105.speedy.com.ar): 5 in the last 3600 secs - Sat Jul  8 20:42:31 2017

To get back on topic. Any news on the ssl issue?

they are coming up slowly

At least it's forward progress. Morning should provide a brighter outlook.

yd29999:

At least it's forward progress. Morning should provide a brighter outlook.

re: HD Work Gear
Glad this behind me and looking ahead I have decided to stay on with Camelot, I understand the situation there was over-whelming. I am sure we will see positive changes come of this. The people at Camelot have a long standing here at Zen Cart and I owe a lot to all that Zen Cart has done for me.

Merlinpa1969:

there was no data loss, we used the backup from AM July 3, emails were not received, absolutly nothing to be done about that since there was no server in place to receive email

To be accurate, lost emails are indeed lost data. Whether something can be done about it is irrelevant. It would be a huge help if you'd start to see these things from the customer's point of view.

Also, as I told Tony, there were orders that I personally shipped that are now gone, so "No data loss" is definitely not accurate.

dkerfoot:

To be accurate, lost emails are indeed lost data. Whether something can be done about it is irrelevant. It would be a huge help if you'd start to see these things from the customer's point of view.

Also, as I told Tony, there were orders that I personally shipped that are now gone, so "No data loss" is definitely not accurate.

Just because emails weren't able to be received during the server outage doesn't mean the emails have been lost. Most mail servers are configured to retry delivery for 5-7 days before they finally give up, and even then the failed ones get returned to sender as being undeliverable which give the sender another chance to resend.

It is actually very difficult for emails to get 'lost' - and when they do, it is generally because the recipients' spam filters are doing the losing.

Just sayin'

Cheers
RodG

My website was up yesterday evening after I cleared the cache stuff that I read about here. This morning I got one of those things to clear the admin log which I did. And now the site is gone. Tony where is my site? Please contact me. Flamedame.com.

p.s. Also can not log in on Camelot to put in a support ticket.

OK..Im pretty done at this point. my peak season is July-October and this is starting to REALLY screw me up!!!! My site was up for a while but anyone who went on and got an error message still got the message because of their browser history and half of the people I told to clear it cant do it as they are even more computer illiterate than I am (and I don't understand why that has to be done anyway, cant that be fixed on Camelots end??) This morning I woke up to several FB posts that its down again. Not even the error message just a "page cant be displayed" pages like I simply don't exist. Now I don't know anything about what is going on but it would seem to me that if you had something break and the data is backed up you replace the broken part, re-load the data and hit the switch. I can allow for a few days to do this but don't see why we have to have our customers jump thru hoops to get on our sites (as in its easier to shop elsewhere!!) and the best we can get for information is a few vague posts here that don't give time frames or anything. Forgive me for my attitude but this is getting expensive at this point.....

I'm being told my site is up, however, I can't see it. I get a different error if I go on with ssl than I do if I don't. I can tell if I'm blocked as the script isn't working... if I go to https://www.uptrends.com/tools/uptime I get mixed answers...

Yep the sites have been going up n down. Marg that link you had shown is still showing DNS errors under SOA for Serial, refresh and expire. The same with ours.
So we continue to wait n see.....

yd29999:

Yep the sites have been going up n down. Marg that link you had shown is still showing DNS errors under SOA for Serial, refresh and expire. The same with ours.
So we continue to wait n see.....

re: HD Work Gear
Hello Tony, should you see this please know - I cannot login to the admin pages or the website - https://www.hdworkgear.com. The mail and c-panel do work as expected. How do I find the website and admin? TY Thomas

hdwrkgr:

re: HD Work Gear
Hello Tony, should you see this please know - I cannot login to the admin pages or the website - https://www.hdworkgear.com. The mail and c-panel do work as expected. How do I find the website and admin? TY Thomas

Ummm I'm not Tony. Tony is Merlinpa1969.

I just pass on what I'm told, what I know, what I've learned. I would recommend putting a ticket in. We did one last night just to make sure they are aware that we are still having issues.

Wyvern Creations:

OK..Im pretty done at this point. my peak season is July-October and this is starting to REALLY screw me up!!!! My site was up for a while but anyone who went on and got an error message still got the message because of their browser history and half of the people I told to clear it cant do it as they are even more computer illiterate than I am (and I don't understand why that has to be done anyway, cant that be fixed on Camelots end??) This morning I woke up to several FB posts that its down again. Not even the error message just a "page cant be displayed" pages like I simply don't exist. Now I don't know anything about what is going on but it would seem to me that if you had something break and the data is backed up you replace the broken part, re-load the data and hit the switch. I can allow for a few days to do this but don't see why we have to have our customers jump thru hoops to get on our sites (as in its easier to shop elsewhere!!) and the best we can get for information is a few vague posts here that don't give time frames or anything. Forgive me for my attitude but this is getting expensive at this point.....
One of the things you can do for your FB customers is reply back with a link to your store that is different than the home-page that they probably are used to going to.

So, if your customers typically bookmark or type in "example.com", post back to FB and tell them to go to "example.com/index.php" instead. As long as they don't hit the same URL that got the "down" page last week, they should be fine.

That only works for the ones I can reach...
Now I am by NO means computer literate but I don't understand if you have a page bookmarked or even went to look for it on a search engine, and hit it and its down/shows an error message why when the site comes back up you cant see the fixed site without having to do all these skips and jumps to fix an issue that had nothing to do with the computer my customers are using. Its bad enough Ive lost I don't know how many sales over this being down at all not to mention SE position and all sorts of other things but now I have to hope that someone I may not know and may not be able to get in touch with will understand if they try to see my page again if and when its fixed that they cant just type in the URL???? Im sorry but that's pretty hard to swallow. IMO Camelot needs to do a re-direct or something on everyones page that will bring it to the sight or whatever so we don't have to worry about losing all the sales/customers who think we are now closed due to this and will not be able to see our site once its back up..

Im sorry, but I pay for my ".com" to work. Not to have to have my customers jump thru geeky hoops and try to find ".com/index.php" This is NOT "my" problem, its Camelots and they need to fix this so my ".com" works they way its supposed to.