Announcement

Collapse
No announcement yet.

Anybody else experiencing a problem with PayPal

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • feemish
    replied
    Thanks Kraken,
    I will probably pay memset support to downgrade NET:SSL if you find it works.

    but I dont use SSL? so would this be the cause of the problem for me?

    Cmon SellerDeck ! Help us out.

    Leave a comment:


  • DaveFM
    replied
    Am also eagerly awaiting a fix after spending all day trying to find out what was wrong. Have had to suspend all sales on our website. People were able to use PayPal Website Payments Pro using the credit card details, but getting the internal server error when submitting. Payments were going through and people have been paying 2 or 3 times not realising.

    PayPal express checkout was also throwing up the error.

    Dave

    Leave a comment:


  • kraken17
    replied
    I am going to .....

    Downgrade my NET:SSL to 2.77 to see if that solves the problem.

    Will let you know if it does.

    BTW Feemish, downgrading or upgrade requires SSH access together with downloading the correct perl module and running the PERL Makefile.PL, make, make test, make install

    Only attempt if you understand the implications of manually modifying your server. This is at your risk

    Leave a comment:


  • feemish
    replied
    Thank you for calling PayPal today.

    I have opened a new ticket to follow up on your issue.

    I guess you need to contact your Shop provider to solve the Problem

    It seams to be that there is a Problem with your PayPal Module.

    I checked although your IPN history to see if we are able to send IPN's to your Sever, but I can see that we are getting the HTTP Response code 500 from your Server.

    ..............................................
    500 Internal Server Error
    A generic error message, given when no more specific message is suitable
    .............................................

    This is most likely an issue with a wrong configuration in your server or a problem with your IPN Script.

    Please consult with your Website developer in order to troubleshoot this issue. Your own server logs should have more information about the incoming IPN from PayPal, and we only have the IPN History to track the IPN messages.

    If you have further questions or updates to this issue, please feel free to contact me again.

    Regards,
    Huseyin
    PayPal MTS
    gcamley Please get back to us with another idea ! The other 1%
    I'm 99% sure that if you can point this out to your ISP's that they will update the Crypt::SSLeay version to the latest and resolve the problem.

    Leave a comment:


  • kraken17
    replied
    Originally posted by feemish View Post
    Can you advise on how this is done manually?
    Just to let you, the update to 0.60.01 did not work - so you do not need to update it.

    Leave a comment:


  • kraken17
    replied
    Crypt::SSLeay update does NOT work

    have upgraded CryptSSLeay to 0.60.01 and I can confirm this is NOT the fix.

    Digest::MD5 2.52
    ActEncrypt1024 Not installed
    Exporter 5.58
    File::Temp 0.22
    LWP::UserAgent 6.04
    Crypt::SSLeay 0.60_01
    CGI 3.59
    CGI::Carp 3.51
    Archive::Zip 1.30
    Net::SSL 2.85

    Any more suggestions SellerDeck??

    Leave a comment:


  • KipperM
    replied
    No SSL

    I'm getting the same problem with PayPal however we don't use SSL on our site.

    I also get ping and tracert timeouts with www.paypal.com and also for www.amazon.com.

    Fortunately we have another payment provider but this is still irritating.

    Leave a comment:


  • kraken17
    replied
    Checking out Crypt:SSLeay

    This website http://search.cpan.org/dist/Crypt-SSLeay/ indicates that Crypt::SSLeay 0.60.01 is actually a developers version, which means it is not in the automatic update stream.

    ISP's will have to update manually - or downgrade to a working version. I will confirm soon if the developers version actually fixes the problem.

    Leave a comment:


  • feemish
    replied
    Originally posted by kraken17 View Post
    And I cannot update Crypt:SSLeay to version 0.60.01 automatically as it is not available from the cpan system. I will have to do this manually.
    Can you advise on how this is done manually?

    Leave a comment:


  • feemish
    replied
    Originally posted by Golf Tee Warehouse View Post
    Seems a little strange that the problem has started at different times for different people and not all at the same time, unless Paypal has rooled out a change over 2 or more nights.
    it must be that our servers have updated these scripts at different times.

    Leave a comment:


  • kraken17
    replied
    I run my own server

    And I cannot update Crypt:SSLeay to version 0.60.01 automatically as it is not available from the cpan system. I will have to do this manually.

    Digest::MD5 2.52
    ActEncrypt1024 Not installed
    Exporter 5.58
    File::Temp 0.22
    LWP::UserAgent 6.04
    Crypt::SSLeay 0.60
    CGI 3.59
    CGI::Carp 3.51
    Archive::Zip 1.30
    Net::SSL 2.85

    Leave a comment:


  • feemish
    replied
    my site is failing.

    As you said;I am on
    Pearl modules
    Net::SSL 2.85
    Crypt::SSLeay 0.6

    I run my own server using WHM. Can anyone tell me how to update these scripts?

    Leave a comment:


  • gcamley
    replied
    The problem appears to be the perl module Crypt::SSLeay.

    I have identified that one of the failing sites is using Net::SSL 2.85 released 29 July 2012 with Crypt::SSLeay 0.60 but a new release was made on 30th July 2012 with Crypt::SSLeay 0.60_01 http://search.cpan.org/~nanis/, another site that works is using Net::SSL 2.77.

    My analysis and the logs shown earlier in this thread all point to Net::SSL.

    I'm 99% sure that if you can point this out to your ISP's that they will update the Crypt::SSLeay version to the latest and resolve the problem.

    I'm surprised that so many ISPs seem to have taken the first update so quick but not the second.

    You may want to check your perl module versions before contacting your ISP by running the 'Web Site Analysis' from SellerDeck at 'Help | troubleshooting'

    Leave a comment:


  • RichardM
    replied
    I can confirm that we are experiencing the same issue as of yesterday.

    Paypal are indeed blaming the hosts but I host our site.

    The error message received is identical to kraken17

    Leave a comment:


  • Golf Tee Warehouse
    replied
    Seems a little strange that the problem has started at different times for different people and not all at the same time, unless Paypal has rooled out a change over 2 or more nights.

    Leave a comment:

Working...
X