15 replies to this topic

[xs1]

Hey guys, i was reading up on this because i haven't been able to get the public hublist in quite some time now. [[ http://forums.apexdc...?showtopic=3133]] Normally this wasn't an inconvenience because i had fav's list so i didnt need the public listing. i uninstalled apex dc++ , tried an older version, than tried the new version again. Still to no avail.  I lost my favs list in the process!  

Anyway, heres where it gets interesting. I downloaded the standard DC++ and peerweb dc++ & strong DC++ or whatever its called and the hublists come in just fine! Which lead me to find out its something with apexDC++. And no, its not my client, because ive tried multiple versions of apex now, as well as other clients and apex is the only one that doesnt recieve hublists.

Here are some screenshots.

1.The apex error

2. The small list of different hublists i have tried. (not all of them, just the ones now)

3. The public hublist using Standard DC++

4. The public hublist's hublists'



1.] http://veeapps.com/nick/ss1.jpg

2.] http://veeapps.com/nick/ss2.jpg

3.] http://veeapps.com/nick/ss3.jpg

4.] http://veeapps.com/nick/ss4.jpg



Now my question is, is their going to be a fix for this? I have tried different clients and they work fine, but i <3 apex and do not want to switch.

~ .s1/ Nick

Edit

ALSO..  I get connection errors even when trying to check for client updates! So its not only the hublists aparently.

5.] http://veeapps.com/nick/ss5.jpg

[Crise]

Well I just tested few of the hublists with my version, and they seem to work just fine... 1.2.0B still has IPGuard, if that has been configured incorrectly it is possible that you have locked yourself out of the hublists.

[xs1]

Crise, on Apr 3 2009, 06:05 PM, said:

Well I just tested few of the hublists with my version, and they seem to work just fine... 1.2.0B still has IPGuard, if that has been configured incorrectly it is possible that you have locked yourself out of the hublists.

Agreed. But mine is currently, and has been , disabled.  

[Mek]

My hublists work fine as well. Do you use a firewall? Try turning it off...

[en_dator]

you can always try and disable coral (in settings / advanced somewhere)  .  Sometimes that can help (in general having it enabled is probably the better option though).

[Mek]

en_dator, excuse me, what is "coral"? Never heard of it before...

[xs1]

Mek, on Apr 4 2009, 04:35 AM, said:

My hublists work fine as well. Do you use a firewall? Try turning it off...

Nope no firewall. Like i said i havnt had this problem before. and ive used apex for a while. recently this happened.

[en_dator]

http://en.wikipedia....ibution_Network

coral is a way to spread the load, and also provide access to content even if the original site is unreachable

[xs1]

en_dator, on Apr 4 2009, 10:53 AM, said:

you can always try and disable coral (in settings / advanced somewhere)  .  Sometimes that can help (in general having it enabled is probably the better option though).

dont see that anywhere lol. :s

[Mek]

xs1, on Apr 6 2009, 11:26 PM, said:

dont see that anywhere lol. :s

have you read the wikipedia link about coral cdn?  
just remove the ".nyud.net" part of hublist address to disable coral  

[xs1]

Mek, on Apr 7 2009, 03:34 AM, said:

have you read the wikipedia link about coral cdn?  
just remove the ".nyud.net" part of hublist address to disable coral  

regardless. none of my hublist links contain the " nyud.net" so apparently that doesn't apply.  this is a client error, most likely starting with the new beta. Even with switching to the old version it still doesn't work.  So my guess is it has something to do with the registry settings for some odd reason. I mean, for 2 different versions of the client to have the same problem while 3 other clients of the same application do not share this problem.. My guess is it has to be something in the registry corrupted(ing) and my question was simply this, with the non beta version coming out, will this problem be fixed.

Got some folks here say " Gotta be you, mines fine" . Well as i previously stated i've spoken to people in hubs who have said things like " Cant remember the last time i got the public hublist". lol so its not just me .  

[en_dator]

since u guys are to damn lazy to look yourself i'll show you :





guess i'll stop trying to help ppl since noone bothers anyway

[xs1]

welp i figured out what it was. Cant say i know why, in fact it makes the complete opposite of sense....  




In the connection settings on first install, theirs in the ip slot 0.0.0.0 .. If your behind a router like me, youd have to put in your router ip.. 192.168.1.2 is my pc. That has always worked for me. Just for shiggle and gitts , i changed it back to 0.0.0.0 and viola, everything works again...  

so.. oddage... but solved.

I do thank you all for all your help.

[Mek]

xs1, it is not odd in any way. There is written "Bind address", 0.0.0.0 means "bind to all network interfaces". If you had multiple network interfaces, you could use a separate ApexDC client for each of them by setting this Bind address.
I have experience that users mostly put the wrong IPs in there since they don't know what Bind address means, in fact, it is one of the most problematic settings. There should be a help balloon or "?" button explaining to users that they don't need to change the Bind address in most cases.

[redrider]

A hublist I have been running for many years, is blocked for some reason.  I can get it to load fine using the alternative address of ..
http://hublist.hopto.org/hublist.xml  but the main address, http://hublist.org.nz/hublist.xml  just gives the message "hublist is temporarily blacklisted for spamming."  How long is temporary?  And Huh?  Spamming where? and what?  The several other links all get to it okay.
I think maybe someone has blocked a similar address..maybe without the NZ on it?  Be nice to get it sorted at long last.
Any ideas anyone?

[Crise]

Update your client to newer version. Also please don't bring up older (as in over a year old) topics like this one. Create new one instead, next time.

Would go into more detail but writing this from a phone so will pass.