This is a quick test to try out a couple methods of fixing the proxy authentication issue with the PortableApps.com Platform 2.0 Pre-Release 2.1 release. Please try this two separate replacement files to see if they work. You'll need to download them and rename them to PortableAppsUpdater.exe and replace your existing file in your PortableApps\PortableApps.com directory to try them out. Keep a copy of your existing one to switch back to.
Updated Method: Download The Test Fix - This should resolve the issue fully and only show the banner during startup when required to show the login. It should also resolve the issue of a blank updater page showing. If this does not work for you, please move on to the others...
Download Current inetc Test - This one will leave any files you download behind in Temporary Internet Files on the local PC but will work with both the standard updater/app directory and the check for apps on startup silently feature (except for prompting for password, of course).
Download Banner Test - This one will show a duplicate banner in updater/app directory mode and show a banner in check for updates on platform startup feature (when it shouldn't).
To check the check for updates on startup feature, first enable check for updates on startup in the Options window on the Advanced tab. Then, you can take an installed app like 7-Zip Portable and edit it's appinfo.ini file in the 7-ZipPortable\App\AppInfo directory. Change the line PackageVersion=9.20.0.1 to PackageVersion=9.20.0.0 which will make the updater think there is a new version. Then exit the platform (no need to eject) and then start it again with Start.exe.
Please give this a try if you use a proxy that requires authentication and report back your findings for both updater replacements and for both the updater/app directory and the automatic update check on startup in this thread.
Thank you!
ADDED: Also, if proxy users could post the exact error message they see when they run the standard 2.0 Pre-Release 2.1 updater from the menu (not the automated startup which should produce no error). It should be an error like "Unable to connect to PortableApps.com to retrieve portable apps. Please try again later." in your language followed by an error code within brackets. It's the exact error code within brackets we're interested in. Does everyone get [Proxy Error (407)]? And does it come up just about instantly after running or is there a delay (if so, could you time it)?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
"Download Current inetc Test" did not work with my proxy but "Download Banner Test" works!
Did it work for both the startup one and the manually launched one? Also, what was the exact error you saw in the official version? And does the error come up just about instantly after running or is there a delay (if so, could you time it)?
Sometimes, the impossible can become possible, if you're awesome!
Sorry, I was so excited with the autoupdater working again...
- Yes works for both (startup and manual).
- The error was 407 (I thought we all were having the same error message... sorry again)
- There isn't delay.
And thank you very much for PA.c!
Download Current inetc Test - don't work
Download Banner Test - works fine
Did it work for both the automatic upgrade check on startup as well as the manual updater/app directory launch from Manage Apps for you? Also, what was the exact error you got in the original updater in the 2.0 PR 2.1 platform release? And does the error come up just about instantly after running or is there a delay (if so, could you time it)?
Sometimes, the impossible can become possible, if you're awesome!
Without any fix
"Unable to connect to PortableApps.com to retrieve portable apps. Please try again later. [Proxy Error (407)]"
With "Current inetc Test" fix
Same message: "Unable to connect to PortableApps.com to retrieve portable apps. Please try again later. [Proxy Error (407)]"
With "Banner Test" fix
It worked fine. Asked for proxy authentication, downloaded Google Chrome Portable and installed it.
I didn't see any "duplicate banner in updater/app directory" or maybe I didn't understand what this expression means. It worked the same way as "Beta 5" did.
PS: "To check the check for updates" reminds me a song called "cheek to cheek".
RaphaelRB - Brazil
How long after you run the updater/app directory directly til you see the Proxy Error (407) message? If not right away, could you please time it?
Sometimes, the impossible can become possible, if you're awesome!
Right away means less than 2 seconds?
The error was as soon as I choose "Manage Apps" and "Check For Updates".
All I wrote above was using this way of updating.
I also tried using Automatic Update and running PortableAppsUpdater directly from PortapleApps folder.
Important observation: when I cancel proxy authentication, it shows a dialog "Unable to connect to PortableApps.com to retrieve portable apps. Please try again later. [Cancelled]" (and its okay), but then shows the update window with blank listing. IMHO when Updater isn't able to connect, it must not show that window.
And perhaps it gives a clue to what's happening, don't it?
RaphaelRB - Brazil
Here are my results of the updater.
Pre-Release 2.1 - Baseline; I hadn't used the "check for updates at startup" feature and wanted to make sure it was also having problems.
Current INECT - Essentially the same results at Pre-Release 2.1; seemed slightly faster as noted below.
Banner - Everything appeared to work as described in the OP.
----------
I thought I'd try out the "Get More Apps" feature as well since it should be requesting a proxy authentication if I go looking for more apps. I'm guessing it uses the same .exe, just processes differently. Still, wanted to check it out.
Pre-Release 2.1 - Baseline
Current INECT - Same results as PR 2.1
Banner - Appears to work normally
Current: No go (error 407 for this as well as in PAM 2.0 PR 2.1)
Double Banner: Yes sir!
I've added a test fix that should properly display the banner and then the proxy authentication if it encounters such a proxy but should remain silent when run on startup when it encounters a standard direct connection or a proxy that requires no password. Please try this out on both authentication proxy connections, direct and no connection computers to ensure proper functionality.
This could be released officially as soon as tomorrow (Thursday) so the more people we get on it the better. Thanks!
Sometimes, the impossible can become possible, if you're awesome!
I have just successfully tested your latest update behind a proxy, using a manual update and an on startup. I'll try and get time to test a direct connection later tonight.
I hadn't updated any apps since PR1 was released due to the error, thanks for all the hard work.
Update: Just got home and tried it without a proxy and both manual and on start up work perfectly.
All works as expected.
Manual update shows proxy request window and finds apps needing update.
Check for updates on startup shows proxy request and finds apps.
Direct connection (w/o proxy) also works properly on both manual update and check at start up.
Yay!
Thanks John for getting this worked out.
I've tried with proxy that requires authentication and proxy that don't require. It works very well.
I won't be able to test in a direct connection until Saturday.
Reading other replies, I can assume that it also works in a direct connection.
Thank you very much!
RaphaelRB - Brazil
Hi John,
the Test fix posted under "Update Method" works fine for me.
I tested both the manualupdate and the add apps feature.
Also, the autoupdate on startup work as it should from my point of view.
Regards and many thanks for the fix!
Chris
I was thinking, maybe instead of having two banners when proxy authentication is needed, why not have the second one that comes up in the window say "proxy authentication needed" or something, so that it don't seem too redundant.
It's ok as the old one is destroyed first and then the new one displayed.
Sometimes, the impossible can become possible, if you're awesome!