Some people are having problems with uploading the Mex25 zips.

Originally there was a problem with an ISP site "somewhere", who had started using "something" ( router? switch? ) with outdated software.

This could be bypassed by using the cc_config option:
<http_1_0>1</http_1_0>
which tells BOINC to use a more primitive transfer protocol.

I tried this and it worked.

Then the problem appeared to get fixed, so I've been running without that option. Successfully.

Another problem that was reported about the same time as Mex25 zips were stuck in the Transfers tab, was having lots of zips, with problems getting any to start uploading.

This "should" have been fixable by using the option:
<max_file_xfers>1</max_file_xfers>
which tells BOINC to only attempt to send one file at a time.

Now there are reports of more Mex25 upload problems, but only for some people.

If you're one of these, try the following:

Use a PLAIN TEXT editor, such as Notepad, to copy the code at the bottom of this post, and save it into a file called cc_config.xml
(Unless you already have a cc_config, in which case add, if necessary, the 2 lines up near the start of this post.)

Note:
cc_config.xml needs to be in the BOINC folder that also contains such things as your account file(s). (For this project, that will be account_climateprediction.net), client_state.xml, and lots of others.
There'll also be two folders:
Projects
slots

Then use the option in the Manager's menu to read config files.

This is the code:


<cc_config>
<log_flags>
</log_flags>
<options>
<http_1_0>1</http_1_0>
<max_file_xfers>1</max_file_xfers>
</options>
</cc_config>

I've had a talk with "head office" about stuck uploads for mex25 tasks, and we've decided that they can be Aborted, but ONLY the mex25 models, which are probably batch 410.

Any stuck zips for other models will be a different problem, and should be asked about.