Recent connectivity issues

Since a few days, the Dropbox version used in DropboxPortableAHK can’t connect to the Dropbox servers and shows a red cross on its tray icon saying “Can’t establish a secure connection”.
During new setups, the Dropbox setup starts with an error saying the proxy configuration is not correct. This is the same issue.

This issue might be connected to the recently discovered Heartbleed OpenSSL bug, but without an official word from Dropbox I cannot say for sure what is going on. I have contacted the Dropbox guys and am waiting for their response which hopefully will not take too long.

It looks like all Dropbox versions after 1.1.45 still work fine, so either Dropbox decided to pull the plug on old versions or they use a different way of connecting to their servers in versions after 1.1.45.

Until I got a reply from Dropbox, there is nothing I can do about this issue, sorry. Please be patient, I will publish an update on the site as soon as I got anything from Dropbox.

Update (17.04.14):
I got a reply from Dropbox today. They said they updated their security and that’s why old Dropbox clients can not connect to their server anymore.
This was what was already suspected by many of you.
I sent them a reply for any possible solution for newer clients and hope to hear back from them soon.

Thanks for your support guys :)

Update (23.04.14):
Yesterday, I received a reply from Dropbox again. It basically says that Dropbox version 1.1.45 is dead and will never work again. Also, they will not assist me in changing the Dropbox path on newer versions.
During the next days, I will investigate if it is possible to either decrypt the Dropbox database settings and use them on another computer or repackage the Dropbox client to not use an encrypted database at all.
Anyone willing to help, feel free to do some research :)

Possible permanent fix for Dropbox updates

Hey guys!

I just want to let you know that I might have found a solution to the always coming back Dropbox update issue.

If you want to skip the technical explanation, just skip to the end and see, how you can help :)

Here is a quick reminder why Dropbox updates are bad for DropboxPortableAHK:
Starting with version after 1.1.45, Dropbox started to encrypt their database. This made it impossible for DropboxPortableAHK to change the Dropbox folder path.
That’s why DropboxPortableAHK tries to prevent Dropbox from updating itself no matter what, because if Dropbox succeeds to update itself it will encrypt the database on the next start and DropboxPortableAHK can not modify the Dropbox path anymore.

Then, DropboxPortableAHK will start the setup again and you basically have to start from scratch. This is obviously pretty annoying.

Over the past few weeks, I put many hours into figuring out why Dropbox might succeed to update itself on some of your machines and did never – even with the basic update prevention – on any of mine. I had no luck, I did not come up with anything.

However, I instead found a new way to possibly prevent any new Dropbox update. On startup, Dropbox looks into its database to see what the last time was when it checked for updates.
If this time is too long in the past, then it will check for updates again. So, to prevent it from even checking if there is a new version available, DropboxPortableAHK can set the “last time Dropbox checked for updates” value to a time far in the future.
This way, Dropbox always thinks it already has checked for new updates and will skip this during its execution alltogether.

But there is still the possibility of Dropbox checking for updates. This is, because Dropbox resets the value in its database on startup to 0 and thus will always check for updates the first time it connects to the server.
There is a little timeframe between Dropbox resetting its value and trying to check for updates. This is when DropboxPortableAHK needs to modify the database in order to skip the update check. To be able to do this, it is possibly best to just write to the database every few milliseconds during startup of Dropbox. After a few minutes of running, we can stop this and stop wasting CPU usage and possibly slowing down the computer if the database is on a slow media (like slow USB drives).

How can you help:
It would be great if there were a few users willing to test this version for a few weeks before I release it to the public.
The code should be safe, but as I mentioned earlier, it might slow down the computer (or just Dropbox) during startup of DropboxPortableAHK.

So, if you want to test this beta version, please send me an email through the contact page or reply as a comment providing your email address (which will be hidden from others).

Update to v1.6.6

As last version for the current year, here is DropboxPortableAHK v1.6.6.

This will block the latest Dropbox updates to 2.4.10 and provides an option to not wait infinitely for an Internet connection, if none could be established. This option can not be set in the configuration screen at the moment, you will have to set “skipInternetConnectionError=1″ in your .dbfiles\config.ini manually.

Make sure to run DropboxPortableAHK on a computer where it can connect to the update servers every once in a while, though, to receive updates.

Update to v1.6.5

After a long time without updates, I am proud to announce a new one.

I sligthly changed the SyncAndGo behavior because of a request by an user. If you have enabled SyncAndGo by default in your settings, holding down the Ctrl key or passing the “-syncAndGo” command line parameter when starting DropboxPortableAHK will now disable SyncAndGo for that run.

The Internet connection check now uses the update servers instead of fixed URLs in order to make sure that information about updates can be downloaded.

Also, this release prevents Dropbox updates to v2.4.3.

Update to v1.6.1

This is a bugfix release. In the previous version it was not possible to set the new custom Dropbox icons, this should work now.
Additionally, the Dropbox update prevention was updated for version 2.1.19.