Crise

Do you use any plugins?

Most likely there is not a whole lot you can do, free wifi hotspots can have strict limitations or total block on used ports or protocols.

  This is very much the eventual intention for the "webserver" its current implementation is dated, unuseful and not flexible. I wouldn't be surprised if eventually the idea of built in web UI ceased to exist and be replaced by a web based API and the usage left to external utilities or applications (one of which may be an UI of course, but which does not necessarily have to be maintained by us for example).   I can look into directory searching in particular but that is likely just the tip of the iceberg, if you catch my drift. Although, thank you for validating the fact that someone is actually still (trying to) use the webserver as is because that means investing time into developing a replacement whatever it will be is worth it. It has simply been sidelined by other things.

This is caused because of an implementation quirk and is more common on NMDC hubs as far as I know.   The reason for this representation, although not intuitive is actually fairly logical. In NMDC every time a user speaks in chat an identity is created for that user the display you are seeing is caused when hub uses an identity that has no representation in the actual user list. This is less common for ADC because it is less common (and less useful because of protocol design) for hubs to speak as a user that is not on the user list, it can be done though.

  ApexDC doesn't use registry for anything meaningful whatsoever, at least when it comes to connectivity. Really if StrongDC works and ApexDC doesn't all I can think of is that either the connectivity of that specific installed copy of ApexDC is blocked by something external, or that a setting has been accidentally changed somehow without you knowing.   Either way the fix is the same as what you already did with StrongDC, ie. redo the installation process either by hand or by using the installer and specifically telling it to install into a different location. If you have the option I would also install ApexDC to a drive other than your OS installation or make sure you use the option to store settings under AppData in the installer. If you do not use the installer search for dcppboot.xml for more info.

Update check failing would have no impact on overall connectivity of ApexDC. So the first thing I would check is the correctness of any connection settings particularly stuff like bind address if it is anything but its default value. After that it would be firewall and router in that order, then ISP.

In case you happen to see this, can you verify the fix for this in 1.5.13 (I am pretty confident it is good, but I can not test it with you specific configuration of course).

Some of that traffic looks extremely interesting... without looking into it, they seem to be either OP clients of some description, as Mek said, looking for particular defects, or malicious clients trying to run an exploit (although I did not check the existing public exploits against these patterns).

  Are they real users or a some type of bot. Either way, can't say I have heard of this kind of behavior exactly. Also what kind of file name they request from you (namely, if it is an actual file in your share a filelist or something else entirely) ?   If you want to look into it more, open the CDM debug window and look at the protocol traffic for those connections.

What version did you update from. There aren't any specific changes that woukd cause this. Are you sure you did not accidentally sort the column different by clicking on it. Also if this is on an NMDC hub number of random things can affect things because of inconsistent encodings when it comes to NMDC.

Thanks for the report, this seems to be issue related to the installer software (Inno setup) itself rather than us, because it has only started to happen very recently. Assuming you do have a default internet browser on your machine. In any case it is completely harmless message.

We have published a maintenance release available for immediate download. 1.5.13 fixes a small set of issues that can in the worst case scenario render your installation of ApexDC effectively unusable. You can check out the full changelog here. We recommend that you update your version of ApexDC as soon as possible. Download: ApexDC++ 1.5.13

  On NMDC hubs, you can not reliably do this... because only small subset of clients support encryption in NMDC at all.   For ADC though, connecting to encrypted hubs is the answer you are looking for. I replied regarding encryption and enforcing it on ADCS >,

Regarding the ciphers AES-256 is in fact slightly less secure than AES-128, because one is designed better than the other the number of bits used is not everything (https://www.schneier.com/blog/archives/2009/07/another_new_aes.html#c386957). There is no one simple way for a hub to enforce encrypted client to client connections. But typically clients in ADCS hubs use encryption if both clients support encrypted client connections. You can read more on the specifics over here: http://adc.sourceforge.net/ADC-EXT.html#_adcs_symmetrical_encryption_in_adc. In short you can check the presence of INF SU field, for support of encrypted connections but there is no way for a hub to force a client to actually make use of that support when connecting to clients. Also see SUDP extension, for active searches, the alternative to this is enforcing passive searches, that go through the hub, for everyone. However, majority of clients do not support SUDP and that there is discussion on a better version of SUDP but that has been talked about for a while now.

I assume you have not changed any of the settings under security and that UPnP is not an option. Unless you have two (or more) active network connections, and thus actually need to set the bind address, it is advisable not to mess with the bind address at all. You can also attempt to leave the IP field blank. Try with more than one user, also try with both active and passive users to see where exactly the problem is. Additionally if the users on your hub connect to it locally (ie. it is a LAN hub) then you should always connect locally to the hub as well obviously and same works in reverse for internet accessible hubs. Easy way to start diagnosing connectivity issues is to find a user X in active mode that you can connect to when you yourself are in passive mode. Because that means that the user is guaranteed to be connectable on his end and then try different methods of port forwarding starting from there in active mode checking against the same user.

There is no real workaround for this at the moment, luckily it should be easy enough to fix. Although I really can't say I can see a reason to leave apexdc running when you are not logged onto the network (unless that session somehow times out, but it would seem rather unusable if it does, to me anyways). To be completely honest I never considered a fail state like this where the internet access is not "real", although I would criticize the implementation of it in your case, to use the 200 (OK) http status code for the login page seems frankly to be a wrong choice. It should either use one of the 4xx codes or even possibly some unusual application of one of the 3xx codes (I assume it already does signal redirect, if it is in any way competent). Because the response is not what an application would ever know to expect. Edit: this should be fixed on our end in the next version... whenever that might be.

Run windows update and install Service Pack 3, further discussion on this topic is in the 1.5.11 release topic as well as in the first post of this topic. People in this topic have mentioned a potential way of running older versions of ApexDC on pre-SP3 versions of XP but this is not in any way officially supported by us (nor will there be any future public discussion on how this can be done, because it is as stated not supported). The gist of it, for anyone reading this, we no longer can support versions of Windows XP that do not have the latest (or last as it may) updates installed. This is not a choice by us but something Microsoft has kindly decided for us.

Update: We have re-released 1.5.12 to address an usability concern with the original release version, we apologize for any inconvenience this may cause. We have published a maintenance release available for immediate download. 1.5.12 fixes the remainder of known issues for 1.5.10 and majority of known issues for 1.5.11. You can check out the full changelog here. On April 8th, 2014 Microsoft officially ceased its consumer support for their Windows XP operating system, originally released in 2001. With the release of 1.5.11 it was brought to our attention that ApexDC can no longer run on all versions of Windows XP, more specifically installations that have not been upgraded with the last available service pack for the operating system (SP3). Unfortunately there is nothing we can do to address this problem and as such Service Pack 3 is the only supported version of XP for ApexDC going forward. We will continue to provide binaries that can run on Windows XP Service Pack 3 as long as it is technically possible and otherwise feasible for us to do so. However, in practice this means that when it comes to ApexDC all support for Windows XP is likely end sometime later this year. This will also mean that support for old CPU's without SSE2 instructions will end at that time. Download: ApexDC++ 1.5.12

Update: The voting period has ended, thank you for everyone who participated. We have been, presumably randomly or based on recent activity, selected for the community choice vote for SourceForge May Project of the Month (fairly new thing they have been doing). If you have a SourceForge account look at the projects listed and vote as you will... or don't, it is really up to you. But it would be a shame for us not to say anything at all, considering this isn't likely to happen again any time soon. We have so far been a featured project (a weekly thing, for handful of projects at a time) twice within the last two or three years. Direct Connect hasn't been prominently featured in any way in recent memory. It would be nice to make that happen, as well as an achievement for the project of course.

Update: The release of 1.5.11 has been officially rolled out. Full changelog available now. If you haven't done so yet please head on over to the download page and update your installation of ApexDC right now. On April 7th, 2014 OpenSSL released a security advisory concerning CVE-2014-0160 also known as Heartbleed. This is a serious security vulnerability in the SSL/TLS library that can result in your private data being compromised without leaving any trace whatsoever. You can check for more specific details from the above links. Most commonly used DC clients are affected by this issue, including ApexDC. Earlier today (April 10th) DC++ released a fixed version but all versions of DC++ from 0.799 to 0.841 and their derivatives are vulnerable. The specific ApexDC versions affected are at least 1.5.3 through 1.5.10. It is important to note that even if the DC++ base version differs from those listed above a client may still be vulnerable as long as it uses one of affected versions of OpenSSL. There is currently, however, no easy way for users to tell what specific version of OpenSSL is used by a particular client. Reading this you may be thinking: But, I am not using SSL/TLS at all right, because I am only on NMDC hubs. This is actually not necessarily true because a select set of clients, such as StrongDC and its derivatives, including ApexDC implement an unnamed NMDC extension that allows TLS to be used for client to client connections between supporting clients. Thus making these clients also affected by this issue outside of ADC and ADCS.. Two hours ago, version 1.5.11 of ApexDC was uploaded to SourceForge and is listed as the latest download there. Likewise the download links on this site now also point to those files. Release announcement including full changelog and all that important information will be made available sometime on the 11th, but for now suffice to say 1.5.11 will fix the issue discussed here as well as a set of other issues found in 1.5.10.

This problem can be entirely avoided by staying away from the Colors & Fonts page. Which also explains why I did not see it, because I never change those settings. This one was fun one to track down because it had literally nothing to do with the manifested problem whatsoever. Also it is worth to note that XP binaries do not have this issue at all. I will reupload 1.5.12 builds with the fix soon, sorry for any inconvenience in advance.

Well technically it is an issue in Wine. Also doesn't seem like it is a quick and easy one to solve on our end either, the changes in hash management done in .10 certainly work just fine on an actual windows .

I have now managed to reproduce this problem, unfortunately it seems completely random.

I will look into this but I am positive those pages were under correct headings when I tested the release version.   Edit: I made a clean install on a computer that has never seen ApexDC before and I can't replicate any of the issues in your post, likewise 64bit Win8. Also I would hope that an issue like this would have been reported by multiple people because it is very visible. Likewise my development installation (which is also my primary ApexDC install) is fine.   Based on above, this seems to be specific to your installation of ApexDC. Can you backup your Settings directory (or ApexDC directory under AppData, depending on your setup) and see if you have the same issues with a blank install. If a blank install solves the issue for you could you then PM me your DCPlusPlus.xml file.

Unfortunately it is not really up to us as much as it is up to Microsoft the 2013 edition of msvc basically disregards compatibility with any version of XP apart from SP3. And if I had to guess the next major version of msvc will not support XP in any meaningful capacity. While we can hold out on upgrading to said version in the future going back a compiler version to retain compatibility with SP2 seems like overkill. Especially when SP3 is a free upgrade. So with SP2 it is unlikely that the situation will change, but we have no plans to stop supoorting XP SP3 as long as it remains feasible. If you wish to keep using older versions with SP2 you can do so but we do not support this and you will have to make any neccessary changes on your own.