Forum moderator: bigblog |
uCoz Community General Information First Steps with uCoz Can't connect to a uCoz website (server is not available, site is down, site inaccessible) |
Can't connect to a uCoz website |
Please check uCoz Server Status' in the following thread before posting: http://forum.ucoz.com/forum/3-14706-1 When posting messages here, make sure that the website is inaccessible for everyone and not just for you.
|
Xenobia, we have sent a request to Comcast to unblock the server.
WorldOfDesign, it looks like your ISP is Comcast as well, it is currently being blocked server 57. You can use TOR or other anonymizers to access your websites till the problem is fixed. I'm not active on the forum anymore. Please contact other forum staff.
|
Hey. My website's IP is 193.109.247.162 and is currently down. I think it's server 57 and it has the same problem as wordofdesign, can you please unblock it.
|
I had this thing 2 months ago, its happening again, the website isnt loading... HELP http://everember.ucoz.com/
Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. tracert everember.ucoz.com Tracing route to everember.ucoz.com [193.109.247.162] over a maximum of 30 hops: 1 2 ms 4 ms 1 ms home [192.168.1.254] 2 11 ms 11 ms 12 ms adsl-99-155-207-254.dsl.wlfrct.sbcglobal.net [99 .155.207.254] 3 12 ms 13 ms 10 ms 12.83.32.29 4 19 ms 19 ms 19 ms n54ny02jt.ip.att.net [12.122.80.237] 5 19 ms 21 ms 18 ms te0-5-0-5.ccr21.jfk07.atlas.cogentco.com [154.54 .12.213] 6 18 ms 20 ms 20 ms te0-3-0-1.mpd22.jfk02.atlas.cogentco.com [154.54 .1.221] 7 91 ms 89 ms 90 ms te0-2-0-6.ccr21.bos01.atlas.cogentco.com [154.54 .44.22] 8 92 ms 109 ms 94 ms te0-0-0-1.ccr21.lpl01.atlas.cogentco.com [154.54 .31.170] 9 98 ms 100 ms 100 ms te0-3-0-3.mpd21.ams03.atlas.cogentco.com [154.54 .58.61] 10 104 ms 103 ms 104 ms te0-3-0-1.mpd21.fra03.atlas.cogentco.com [130.11 7.2.42] 11 107 ms 107 ms 107 ms te0-1-0-0.ccr21.fra06.atlas.cogentco.com [130.11 7.50.202] 12 102 ms 102 ms 102 ms 149.11.20.70 13 159 ms 151 ms 153 ms 217.65.1.253 14 150 ms 151 ms 152 ms sw17.citytelecom.ru [217.65.1.98] 15 149 ms 149 ms 150 ms te4-4-9-fibius.msk.citytelecom.ru [217.65.1.250] 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Post edited by Kajamaz - Thursday, 2012-06-21, 0:31 AM
|
Today, Wednesday 6 20 2012 several people have contacted me. We cannot access 2 websites and 2 we can access. The 2 we cannot access are: dtvprogressive1.ucoz.com and dtvweekend.ucoz.com. We have all tried clearing cache. I get a timed out message. The 2 sites we have no trouble accessing are : dtvweekendvip1.ucoz.com and dtvpresandwh.ucoz.com. Please help :-)
|
server 52 down????????????? whyyyyyyyyyyy????????
|
so what do I do? who has to unblock server 57? do I have to call Comcast or it is unet problem?
|
I want to know the right topic to put my site faithful until Tqomuh evaluation
|
I can not open www.kampoengdiecast.ucoz.com since today.
Can you help me? What's problem? Many thanks for your help. |
I called Comcast, they basically told me I have to wait for the request and for Ucoz to get their end settled. So I guess Imma sit here and hope my site is back up on my end. I can't view it but everyone else can. I can't even make a new one without getting the Timed Out issue...Hope this gets fixed soon. Im already irritated with the pop up thing..
|
i can't access my website http://www.topbusinessfinance.com/ under server52 (i'm not sure with the server). Please help. I've also experience broken css styles and broken links from time to time. Please help...
Post edited by khen - Thursday, 2012-06-21, 6:47 AM
|
It result's for : www.kampoengdiecast.ucoz.com
Now shown on my screen : 504 Gateway Time-out uServ/1.5.4 Then from http://host-tracker.com : Bloomsburg, PA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.20 sec 193.109.247.162 indonetmedia Nurnberg, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 193.109.247.162 UpgradeHost.ru WanChai, Hong Kong Http error:Http_client.No_reply 40.41 sec 193.109.247.162 Zolar Co Ltd Fort Lee,NJ,US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 193.109.247.162 ProGoldHost.net Kiev, Ukraine Http error:Http_client.No_reply 40.02 sec 193.109.247.162 HOSTED Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.16 sec 193.109.247.162 HostPojok.Com Lansing, MI, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.16 sec 193.109.247.162 Rioserver Dallas, TX, US Http error:Http_client.No_reply 40.05 sec 193.109.247.162 Provisov.Net Gunzenhausen, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 aBajt Montreal, CA Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 193.109.247.162 TUWEBHOST Kiev, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.02 sec 193.109.247.162 ABCname Los Angeles, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.20 sec 193.109.247.162 PremiumReseller Amsterdam, Netherlands Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 PDhost Hampshire, UK Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.06 sec 193.109.247.162 PremiumReseller Los Angeles, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.20 sec 193.109.247.162 West Cost Hosting New York, NY, US Http error:Http_client.No_reply 10.14 sec 193.109.247.162 HostGW.com Webhosting Moscow, RU Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 193.109.247.162 HOSTLEX Minsk, Belarus Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.15 sec 193.109.247.162 BelInfoNet Ltd. Montreal, Quebec, Ca Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 193.109.247.162 XP-Hosting.com SPb, Russia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.01 sec 193.109.247.162 Indahost Kwun Tong, Hong Kong Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.39 sec 193.109.247.162 Entinity Information Technology Solutions Amsterdam, Netherlands Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.06 sec 193.109.247.162 Hostmaster, Ltd. Birmingham, UK Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.16 sec 193.109.247.162 Joomla Hosting Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.16 sec 193.109.247.162 Custom Hosting Solutions Moscow, Russia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.07 sec 193.109.247.162 OpenHosting Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.17 sec 193.109.247.162 Eskhosting Nuremberg, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 193.109.247.162 VPS-server.ru Montreal, Quebec, Ca Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 193.109.247.162 NordGate networks Haarlem, Netherlands Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 193.109.247.162 Steadyhost Riga, Latvia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 Nano IT Gdansk, Poland Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.06 sec 193.109.247.162 HCX Hosting Toronto, ON, CA Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 193.109.247.162 OnyxNetUa Paris, France Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 XHN.ES Hosting Washington, USA Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 193.109.247.162 Nidohosting Moscow, Russia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.01 sec 193.109.247.162 MNW.RU Frankfurt, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 mrhost.biz Kostanay, Kazakhstan Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 Globox Perm, Russia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.03 sec 193.109.247.162 Feel-now Paris, France Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 Cyber Snake Ltd Frankfurt, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 193.109.247.162 AllServ.Net.UA Falkenstein, German Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 193.109.247.162 Hosting Hutor.com Kiev, Urkaine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.02 sec 193.109.247.162 HostService.ua Paris, France Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.05 sec 193.109.247.162 IntoHost Tracing route to ucoz.com [213.174.157.210] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 172.31.23.1 2 4 ms 3 ms 8 ms 202.152.225.253 3 4 ms 6 ms 6 ms 112.215.5.132 4 173 ms 133 ms 93 ms 202.152.245.82 5 191 ms 215 ms 210 ms 112.215.37.42 6 221 ms 124 ms 111 ms xe-11-2-0-xcr1.sng.cw.net [203.169.57.205] 7 218 ms 219 ms 229 ms xe-2-3-0-xcr1.sgs.cw.net [195.2.10.214] 8 201 ms 261 ms 272 ms xe-0-1-0-xcr1.tyo.cw.net [195.2.10.69] 9 438 ms 456 ms 527 ms xe-11-0-0-xcr1.mry.cw.net [195.2.28.94] 10 464 ms 510 ms 536 ms xe-0-2-0-xcr1.pal.cw.net [195.2.10.121] 11 502 ms 493 ms 583 ms xe-0-3-0-xcr1.lax.cw.net [195.2.28.21] 12 295 ms 209 ms 236 ms te7-5.ccr01.lax04.atlas.cogentco.com [154.54.12. 1] 13 211 ms 220 ms 212 ms te0-2-0-7.mpd22.lax01.atlas.cogentco.com [154.54 .2.237] 14 314 ms 235 ms 258 ms te0-1-0-6.mpd22.iah01.atlas.cogentco.com [154.54 .0.246] 15 270 ms 361 ms 256 ms te0-1-0-3.mpd22.atl01.atlas.cogentco.com [154.54 .5.54] 16 269 ms 260 ms 259 ms te0-2-0-0.ccr21.atl01.atlas.cogentco.com [154.54 .28.61] 17 284 ms 256 ms 256 ms te0-3-0-2.ccr21.dca01.atlas.cogentco.com [154.54 .2.46] 18 260 ms 261 ms 260 ms te0-2-0-5.ccr21.iad02.atlas.cogentco.com [154.54 .41.114] 19 * * 260 ms 38.122.62.114 20 261 ms 257 ms 291 ms dev210.ucoz.net [213.174.157.210] Trace complete. Added (2012-06-21, 1:43 AM) Post edited by Panglimakapal - Thursday, 2012-06-21, 7:10 AM
|
Server 52 was temporarily unavailable due to the hardware failure. Now it is working in its normal mode. Please accept our apologies for the inconvenience. You can check your server status in the following thread: http://forum.ucoz.com/forum/3-14706-1 Quote (Expert1510) My website's IP is 193.109.247.162 and is currently down. I think it's server 57 Your website is on server 52, not 57. Quote (WorldOfDesign) so what do I do? who has to unblock server 57? do I have to call Comcast or it is unet problem? We have already sent a request to Comcast. Usually they react within several days. Quote (karika) I want to know the right topic to put my site faithful until Tqomuh evaluation Sorry, I don't understand your question. Please try to explain it in more detail. Quote (Xenobia) I called Comcast, they basically told me I have to wait for the request and for Ucoz to get their end settled. So I guess Imma sit here and hope my site is back up on my end. I can't view it but everyone else can. I can't even make a new one without getting the Timed Out issue...Hope this gets fixed soon. Im already irritated with the pop up thing.. You can use TOR or other anonymity services to access your website till the problem is fixed. Most probably the server was blocked by Comcast due to a phishing website hosted on the server. The website has most probably been deleted already, as our abuse team deletes all phishing websites immediately after they have been reported. So the server must be unblocked soon. I'm not active on the forum anymore. Please contact other forum staff.
|
| |||