It usually takes a bit of time to load that page. You should get a popup for saving the backup file. The actual page will look a little silly, but that's okay. If you're able to get this file, please send it to firstname.lastname@example.org and reference this thread.
I had those bugs before I changed my router, from a Belkin N300 to a Cisco-Linksys e4200.
At first I was thinking that it was some issue with Bonjour, but there was something else too, because I had the problem even going by ip address. It seems that this redeye thing is a little picky with the routers. Anyway, everything works fine now.
What kind of router you have? Can you borrow another router, just for testing ?
Do you have your browser set to a language other than English? If so, could you let us know what it is so we can test on our end? Please also change it to English, clear cache completely again, and try once more. Let me know how this goes.
I am the guy who writes the browser application. It appears that 2.7.0 has a bug in the French localization file. The app should work just fine in English. We are planning another release soon, and I will get the French working again for it. Apologies for the inconvenience.
I used a PC with Windows 7 (fr) and french browser IE 9 to update to 2.7. The update was OK with iPad 2. I could access to RedEye Pro easily. Went back to the Web on the PC to make a backup copy, then all the problems started. It is almost the same as describe by BOBaGINETTE.
Also, I have a Mac on the same network. I use Airport Extreme as the router. Oh surprise everything works fine. I use Mac OS 10.7.1 (english version) with english browsers (Firefox, Chrome, Safari), It works fine with all these english browsers.
So, I suspect that there a problem with the language. I can't use the PC to make any changes. I have used all recommendations that were suggested in the forum: clear cache, reboot Airport, RedEye Pro. Still, nothing works. With the Mac, everything works fine.
Do you have any idea to solve this problem with the language?
Did you clear the cache after you set the browser to use English? If so, give Firefox English a try and let us know how it goes. As far as we can tell this is only a problem related to language, so changing the language to English and then clearing cache should solve the issue. This has fixed it for everyone we've spoken to (and the only customers experiencing the issue were those using foreign language settings in the browser).