Using the 1.0.0 Windows installer, the connection times out attempting to download the SSL support files (specifically, IO-Socket-SSL-tar.gz). I'm assuming the problem is temporary, but even still, is there a way to manually download and install the files (e.g. from CPAN or wherever it's trying to go) on the Windows version?
Any help appreciated. Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
------------------------------------------------------------
SSL Support installation finished 10-Jan-2008 @ 16:28:57
------------------------------------------------------------
</snip>
As you can see from the log, IO-Socket-SSL.tar.gz is the first SSL file to be downloaded. Perhaps your firewall is blocking the installer's download utility? I had to give permission for the installer to access the internet in order to get the SSL files downloaded on my system.
You can use POPFile's "Add/Remove Programs" entry to try adding SSL support again.
>> is there a way to manually download and install the files <<
If you are still having trouble you can install some old SSL support files using the standalone SSL Setup wizard by running the command:
It would help if you supplied some more information, such as which version of Windows and the exact error message. The installer creates a log file (install.log) which can be found in the POPFile program folder.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks so much. This actually worked on a subsequent try w/ no changes at my end, so I assume the problem is at the download site. In any case, I greatly appreciate the info.
-Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The download site is the University of Winnipeg's ActivePerl 8xx Repository which appears to be very reliable.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2008-02-08
My original problem is that my windows client stopped connecting to yahoo's pop3 server only when going through popfile; using the same port/ssl settings directly works fine. Yahoo servers have been awful lately but it's hard to argue when things work without going through popfile. Telnetting to popfile etc. works fine too, and neither popfile's nor the client's config has changed (and they still match up), but only the combination fails. If anyone has ideas other than throwing out Windows I'd love to hear them. Meanwhile,
I tried to upgrade to 1.0.0. The install cannot download an SSL patch file because of a 403 error.
Relevant installer text follows:
Downloading 1.0.0.pcf file from http://h1212143.stratoserver.net/installer/ssl-patch/
Error 403 (Access Forbidden)
I went ahead and finished the installation. The text says
Unable to download data from POPFile website, using built-in SSL patches instead.
No POPFIle SSL patches are required.
I'm not sure whether to believe that last statement given it was trying to download a patch file earlier.
Can the access be fixed or other guidance given please?
Thanks
CB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I apologize. We are currently moving POPFile to a new server and it seems that I blocked access to the patches with my latest tweak to the web server configuration. You should now be able to download the path.
Sorry,
Manni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I'm not sure whether to believe that last statement given it was trying to download a patch file earlier. <<
Yes, you can believe that statement. At present there are no SSL patches for the 1.0.0 release so it does not matter that the installer was unable to download the patch data.
The SSL Support files are not maintained by us so sometimes we need to apply some patches to make the files work with a particular release of POPFile. This is why the installer always tries to download a Patch Control File (PCF) from the POPFile website in order to find out if any patches are required.
Until you mentioned it, I had not realised that the log entry for the case where the PCF cannot be downloaded is not very clear.
If the installer had been able to download the PCF data the log file would have included:
<snip>
POPFile 1.0.0 Patch Control File (issue 0)
The current SSL Support files are compatible (21 Oct 2007 @ 10:00 GMT)
No POPFile SSL patches are required
</snip>
If the installer cannot download the PCF data I think the log file should contain something like this:
<snip>
Unable to download data from POPFile website, using built-in SSL patches instead
POPFile 1.0.0 Patch Control File (issue 0)
The current SSL Support files are compatible (21 Oct 2007 @ 10:00 GMT)
No POPFile SSL patches are required
</snip>
The next release of POPFile will use an improved log message if the PCF download fails.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> The next release of POPFile will use an improved log message if the PCF download fails <<
I've updated the code which will be used to build the installer for the next release of POPFile (I'm not sure exactly when it'll be released, we're still working on it). When the PCF data cannot be downloaded the log file will show:
Unable to download data from POPFile website, using built-in SSL patches instead
POPFile 1.0.1 Patch Control File (issue 0) [*** Built-in version ***]
The current SSL Support files are compatible (5 Jan 2008 @ 14:41 GMT)
No POPFile SSL patches are required
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using the 1.0.0 Windows installer, the connection times out attempting to download the SSL support files (specifically, IO-Socket-SSL-tar.gz). I'm assuming the problem is temporary, but even still, is there a way to manually download and install the files (e.g. from CPAN or wherever it's trying to go) on the Windows version?
Any help appreciated. Thanks!
>> I'm assuming the problem is temporary <<
I tried using the 1.0.0 installer to add SSL support to an existing installation a few minutes ago without any problem:
<snip>
----------------------------------------
"SSL Support" Section (entry)
----------------------------------------
Downloading IO-Socket-SSL.tar.gz file from http://theoryx5.uwinnipeg.ca/ppms/x86/
Downloading Net_SSLeay.pm.tar.gz file from http://theoryx5.uwinnipeg.ca/ppms/x86/
Downloading ssleay32.dll file from http://theoryx5.uwinnipeg.ca/ppms/scripts/
Downloading libeay32.dll file from http://theoryx5.uwinnipeg.ca/ppms/scripts/
...
Download the Patch Control File and MD5 sums from the POPFile website...
...
POPFile 1.0.0 Patch Control File (issue 0)
The current SSL Support files are compatible (21 Oct 2007 @ 10:00 GMT)
No POPFile SSL patches are required
----------------------------------------
"SSL Support" Section (exit)
----------------------------------------
------------------------------------------------------------
SSL Support installation finished 10-Jan-2008 @ 16:28:57
------------------------------------------------------------
</snip>
As you can see from the log, IO-Socket-SSL.tar.gz is the first SSL file to be downloaded. Perhaps your firewall is blocking the installer's download utility? I had to give permission for the installer to access the internet in order to get the SSL files downloaded on my system.
You can use POPFile's "Add/Remove Programs" entry to try adding SSL support again.
>> is there a way to manually download and install the files <<
If you are still having trouble you can install some old SSL support files using the standalone SSL Setup wizard by running the command:
addssl.exe /BUILTIN
These files should be good enough to let you use POPFile's SSL Support (but I've not tried this with the 1.0.0 release). Here is a download link for the standalone wizard (629 KB): http://www.sugelan.co.uk/popfile/download/cvsbuild/addssl.zip
It would help if you supplied some more information, such as which version of Windows and the exact error message. The installer creates a log file (install.log) which can be found in the POPFile program folder.
Brian
Brian,
Thanks so much. This actually worked on a subsequent try w/ no changes at my end, so I assume the problem is at the download site. In any case, I greatly appreciate the info.
-Mark
Glad to hear it worked when you tried it again!
The download site is the University of Winnipeg's ActivePerl 8xx Repository which appears to be very reliable.
Brian
My original problem is that my windows client stopped connecting to yahoo's pop3 server only when going through popfile; using the same port/ssl settings directly works fine. Yahoo servers have been awful lately but it's hard to argue when things work without going through popfile. Telnetting to popfile etc. works fine too, and neither popfile's nor the client's config has changed (and they still match up), but only the combination fails. If anyone has ideas other than throwing out Windows I'd love to hear them. Meanwhile,
I tried to upgrade to 1.0.0. The install cannot download an SSL patch file because of a 403 error.
Relevant installer text follows:
Downloading 1.0.0.pcf file from http://h1212143.stratoserver.net/installer/ssl-patch/
Error 403 (Access Forbidden)
I went ahead and finished the installation. The text says
Unable to download data from POPFile website, using built-in SSL patches instead.
No POPFIle SSL patches are required.
I'm not sure whether to believe that last statement given it was trying to download a patch file earlier.
Can the access be fixed or other guidance given please?
Thanks
CB
I apologize. We are currently moving POPFile to a new server and it seems that I blocked access to the patches with my latest tweak to the web server configuration. You should now be able to download the path.
Sorry,
Manni
>> I'm not sure whether to believe that last statement given it was trying to download a patch file earlier. <<
Yes, you can believe that statement. At present there are no SSL patches for the 1.0.0 release so it does not matter that the installer was unable to download the patch data.
The SSL Support files are not maintained by us so sometimes we need to apply some patches to make the files work with a particular release of POPFile. This is why the installer always tries to download a Patch Control File (PCF) from the POPFile website in order to find out if any patches are required.
Until you mentioned it, I had not realised that the log entry for the case where the PCF cannot be downloaded is not very clear.
If the installer had been able to download the PCF data the log file would have included:
<snip>
POPFile 1.0.0 Patch Control File (issue 0)
The current SSL Support files are compatible (21 Oct 2007 @ 10:00 GMT)
No POPFile SSL patches are required
</snip>
If the installer cannot download the PCF data I think the log file should contain something like this:
<snip>
Unable to download data from POPFile website, using built-in SSL patches instead
POPFile 1.0.0 Patch Control File (issue 0)
The current SSL Support files are compatible (21 Oct 2007 @ 10:00 GMT)
No POPFile SSL patches are required
</snip>
The next release of POPFile will use an improved log message if the PCF download fails.
Brian
>> The next release of POPFile will use an improved log message if the PCF download fails <<
I've updated the code which will be used to build the installer for the next release of POPFile (I'm not sure exactly when it'll be released, we're still working on it). When the PCF data cannot be downloaded the log file will show:
Unable to download data from POPFile website, using built-in SSL patches instead
POPFile 1.0.1 Patch Control File (issue 0) [*** Built-in version ***]
The current SSL Support files are compatible (5 Jan 2008 @ 14:41 GMT)
No POPFile SSL patches are required
Brian