Please login to reply
|
|||||
[#109016]
Written by: WesleyWex [09/08/2009, 22:58] |
|||||
www.ezrss.it isn't responding here, chrome gave me err_empty_response. tried to connect using my phone's 3g network and got a similar error (server stopped responding). |
|||||
[#109025]
Written by: gwumm [09/08/2009, 23:43] |
|||||
not working for me either? - it hasn't worked since it's been 'up' for me. | |||||
[#109027]
Written by: Byeuji [10/08/2009, 00:16] |
|||||
i'm also not able to connect to it, since this morning. got on this morning and utorrent timed out accessing it (red rss symbol), and just now i tried viewing it in firefox, and it timed out. |
|||||
[#109042]
Written by: NovaKing (Administrator) [10/08/2009, 02:07] |
|||||
it seems i need to buy more servers to handle the load. | |||||
[#109051]
Written by: NovaKing (Administrator) [10/08/2009, 03:23] |
|||||
there have also been reports that some routes are blocking the ip of ezrss, reasons i am unsure about just yet, but i am looking into this. http://www.dslreports.com/forum/r22825039-bc-telus-default-gateway-not-routing-properly http://www.dslreports.com/forum/r22832616-connectivity-verizon-router-blocking-httpezrssit-94752 |
|||||
[#109092]
Written by: aLIBUBA [10/08/2009, 12:18] |
|||||
doesn't seem to be the issue at least over here. # tcptraceroute -p 80 94.75.216.31 (skipping some early hops) 9 netnod-ix-ge-a-sth-1500.leaseweb.com (194.68.123.160) 47.145 ms 45.058 ms 45.833 ms 10 po100.hv3.evo.leaseweb.net (94.75.223.249) 46.771 ms 44.730 ms 44.615 ms 11 94.75.216.31 (94.75.216.31) 45.014 ms 45.019 ms 45.089 ms # tcping ezrss.it 80 ezrss.it port 80 open. # curl -v --max-time 10 --head http://ezrss.it * about to connect() to ezrss.it port 80 * trying 94.75.216.31... connected * connected to ezrss.it (94.75.216.31) port 80 > head / http/1.1 > user-agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 openssl/0.9.8b zlib/1.2.3 libidn/0.6.5 > host: ezrss.it > accept: */* > * operation timed out after 10 seconds with 0 bytes received * closing connection #0 curl: (28) operation timed out after 10 seconds with 0 bytes received so the http server seems to have ground to halt. cache, cache, cache. =) al p.s. the login problem seems to still be haunting the backends. |
|||||
[#109262]
Written by: dr spock [13/08/2009, 06:30] |
|||||
some isp's i think are silently blocking the ip (i cant even ping/tracert it), possibly due to a perceived security risk. see: http://safeweb.norton.com/report/show?name=94.75.216.31 http://www.emergingthreats.org/rules/emerging-botcc-block.rules http://foundnets.blogspot.com/2009/08/947521631.html http://owned-nets.blogspot.com/2009/08/netanddoscoukanddos-from-bottalk-lol.html |
|||||
[#116802]
Written by: Ncl8 [21/08/2009, 03:41] |
|||||
i cant access the site either, looks like my isp(telia sonera) is blocking it too. i need to use tor to get to the site. |
|||||
[#116819]
Written by: Exterus [21/08/2009, 11:25] |
|||||
someone seems to have reported this: http://94.75.216.31:85/~anddos/host.exe as a trojan. | |||||
[#116869]
Written by: manuseer [22/08/2009, 05:49] |
|||||
the ip hosting ezrss.it (94.75.216.31) appears to be a botnet controller. it's running an irc server on port 6667 with which infected machines communicate and is serving up trojans/malware on port 85 (http://94.75.216.31:85/~anddos/) given that, it's entirely appropriate for isps to be blocking it. another page on this: http://foundnets.blogspot.com/2009/08/netanddoscouk-anddos.html |
|||||
[#117066]
Written by: sammywhammy [25/08/2009, 22:18] |
|||||
can't start a new thread for some reason...recently the rss feed has been missing some shows maybe because of some parsing errors. prime examples are weeds and 10 things about you even though the shows were distributed by eztv. can any admin please look into it. also when making torrents can you guys include publicbt and the udp version of obt and publicbt. the http ones can be removed once ut 2.0 becomes prevalent. right now my list suggestion is http://tracker.openbittorrent.com/announce udp://tracker.openbittorrent.com:80/announce http://tracker.publicbt.com:80/announce udp://tracker.publicbt.com:80/announce thanks |
|||||
[#117149]
Written by: Shivv [26/08/2009, 23:40] |
|||||
in a similar vein, i can't seem to connect to the openbittorrent.com tracker. anyone else having that problem, and if so what is the solution? |
|||||
[#117172]
Written by: futrtrubl [27/08/2009, 04:04] |
|||||
me too, can't access the tracker, or the rss host (though i have been able since the move). | |||||
[#117251]
Written by: fggt [28/08/2009, 05:04] |
|||||
i can't access the openbittorrent tracker and neither can a great deal of the posters in the thread for general tech questions. i've been copy/pasting a tracker list for people to use to solve the tracker problems. http://tracker.irc.su:80/announce http://www.h33t.com:3310/announce http://nemesis.1337x.org:80/announce http://bttrack.9you.com:8080/announce http://tracker.bittorrent.am:80/announce http://tracker.ilibr.org:6969/announce http://z6gw6skubmo2pj43.onion:8080/announce http://z6gw6skubmo2pj43.tor2web.com:8080/announce http://tracker.openbittorrent.com/announce udp://tracker.openbittorrent.com:80/announce http://tracker.publicbt.com:80/announce udp://tracker.publicbt.com:80/announce always wondered why, especially in light of recent events, uploaders don't use every tracker they can... |
|||||
[#117294]
Written by: NovaKing (Administrator) [28/08/2009, 17:55] |
|||||
i have just bought another server to help with the server load for ezrss, this transitions will occur over the next day or so, hopefully once complete ezrss should be able to be seen by all and have better load times. |
|||||