![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Broke Perl Script Second pair of eyes NET::FTPSSL | Styles | Shell Programming and Scripting | 4 | 01-12-2009 09:07 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Hello,
I ran into an issue in one of my monitoring scripts. If I use the public ip address in my connection string everything works, but if I switch the connection string ip to 127.0.0.1 or the internal ip I get, " Connection refused at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/Net/SSLeay/Handle.pm line 229." This is most likely because it thinks it's a bad cert. I can't seem to find anything on how to force it to ignore a invalid cert? Is this even an option? Thanks, Styles |
|
||||
|
Update: Running through debug now and now I'm really confused as to why it failing.
Quote:
Ok I think I see the problem in the debug. If I use the internal or localhost the script dies when trying to send a file via passive. We can see in the debug that the Public IP is being passed and not the internal network IP. As soon as I change the connection string to the public IP address instead of using the local internal IP everything works. So this might be a VSFTPD issue with passive transfers, or is my thinking wrong on this? Thanks, Eric Last edited by Styles; 02-10-2009 at 05:45 PM.. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|