Latest News: (loading..)

Roaddoctor

Members
  • Content count

    1,177
  • Joined

  • Last visited

  • Days Won

    1

Roaddoctor last won the day on September 13 2015

Roaddoctor had the most liked content!

3 Followers

About Roaddoctor

Profile Information

Recent Profile Visitors

75,847 profile views
  1. I get a nice A- at ssl labs. SSLv3 not enabled of course. Today my host swapped my php handlers from DSO to SuPHP as the problem only exists for DSO. All seems stable for the moment. I'll dig into that FedEx sample code - thanks John.
  2. For this type of error.... Is there some safety net coding that could be implemented that would catch the SoapFault exception and prevent the http 500? Way over my head, but getting http 500 really throws customers for a loop and they are gone... Thanks for any ideas!
  3. Per cPanel- It appeared that only ea-libcurl package has been broken during latest EA upgrade. Here's reply from cpanel: ----- Further investigating this the issue is occurring due to internal case EA-6671. The latest update of libcurl which soap uses is what's causing the issue. Unfortunately I do not have an ETA as to when this will be corrected but once it has it'll be reflected in our change log here: https://documentation.cpanel.net/display/EA4/EasyApache+4+Change+Log Our developers have made this case a high priority and I expect this to be implemented soon in our product. --- My host reversed the update and the sites worked normal again. They added ea-libcurl to the yum exclude until resolved. Lost a days business over this too... #$% :) Thanks all for the help!
  4. Looks like SOAP updated on the server last night and broke the interwebs - no connectivity causing http 500. Host has contacted cPanel and is "working on it"... lovely BAD SOAP: Name : ea-php56-php-soap Version : 5.6.31 Release : 2.2.2.cpanel Architecture: x86_64 Install Date: Wed Aug 9 05:51:44 2017 PHP Fatal error: Uncaught SoapFault exception: [HTTP] Could not connect to host in /includes/modules/shipping/fedexwebservices.php:291 stack trace: #0 [internal function]: SoapClient->__doRequest(' version="...', 'https://gateway...', 'getRates', 1, 0) #1 /includes/modules/shipping/fedexwebservices.php(291): SoapClient->__call('getRates', Array) #2 /includes/modules/shipping/fedexwebservices.php(291): SoapClient->getRates(Array) #3 /includes/classes/shipping.php(105): fedexwebservices->quote('') #4 /shipping_quotes.php(167): shipping->quote() #5 {main} thrown in /includes/modules/shipping/fedexwebservices.php on line 291 John, thanks for the replies!
  5. FedEx says all normal on their end - but they are not receiving my quotes request... talking to host now - maybe SOAP is busted.... scratching my head
  6. John, is this what's in your wsdl9? <service name="RateService"> <port name="RateServicePort" binding="ns:RateServiceSoapBinding"> <s1:address location="https://gateway.fedex.com/web-services/"/> </port> </service> Thanks! The problems affecting 2 sites, identically, so doubt its corrupted files... Hopefully a temporary issue at FedEx end... calling them now. If I disable the FedEx module, everything is perfect - so its something odd
  7. testing RateService change now - I think that's the only one in wsdl9
  8. August 2017 – Action Required to Update FedEx Web Services WSDL URLs FedEx is implementing the best practices in the new platform for FedEx Web Services WSDLs. The new platform follows a servlet-based approach which requires customers to use standard URLs to route the requests correctly. If you are currently using undefined/non-standard URLs (SOAP) for the services, please check your URLs prior to January 2018 to ensure your services with FedEx continue and will not be interrupted. See below the corresponding URLs for the impacted FedEx Web Services WSDLs. Note: The following URLs are not intended to be opened in a browser. These are endpoints to be used in a Web Services based transaction. Name of Service Corresponding URL AddressValidationService https://ws.fedex.com:443/web-services/addressvalidation AsyncService https://ws.fedex.com:443/web-services/async CloseService https://ws.fedex.com:443/web-services/close CountryService https://ws.fedex.com:443/web-services/cnty DGDataService https://ws.fedex.com:443/web-services/dgds DGLDService https://ws.fedex.com:443/web-services/dgld InFlightShipmentService https://ws.fedex.com:443/web-services/ifss LocationsService https://ws.fedex.com:443/web-services/locs OpenShip https://ws.fedex.com:443/web-services/openship PickupService https://ws.fedex.com:443/web-services/pickup RateService https://ws.fedex.com:443/web-services/rate ShipService https://ws.fedex.com:443/web-services/ship TrackService https://ws.fedex.com:443/web-services/track UploadDocumentService https://ws.fedex.com:443/web-services/uploaddocument ValidationAvailabilityAndCommitmentService https://ws.fedex.com:443/web-services/vacs What you should do: Please ensure the appropriate team members are aware of this important update. If you have questions or need technical assistance: The United States and Canada, call 1.877.339.2774 or send an email to websupport@fedex.com. Support hours are 7 a.m. to 9 p.m. CT Monday through Friday and 9 a.m. to 3 p.m. CT Saturday. Europe, send an email to emeawebservices@fedex.com. The Indian Subcontinent, the Middle East and Africa, send an email to meisawebservices@fedex.com. Asia-Pacific, send an email to apacwebservices@fedex.com. Brazil, send an email to ct-brazil@corp.ds.fedex.com. The rest of Latin America and the Caribbean, send an email to tsc@corp.ds.fedex.com. Thank you for your time and attention. We appreciate your business. The FedEx Web Integration Solutions Team
  9. crap - just found this http://www.fedex.com/us/developer/announcements.html The issue? Anyone else having problems?
  10. As of this morning, and out of the blue with no recent changes on my end, As soon as a customer reaches checkout_shipping.php, they get HTTP 500 error. If I disable the FedEx Webservice module, everything is fine. This is happening on 2 different sites, and our host says all is ok on their end. Also, the ship-in-cart tool does not cause http 500, but just spins the spinner without returned quotes. What has FedEx Done? How do I fix it? Help! Can anyone else confirm if they are having the same issue?
  11. I don't know if its related, but yesterday, an overnight cURL update on my server did not go right or something, because I had the complete paypal failure situation just like you described until I did a graceful reboot of the server and all was suddenly resolved... hope that helps
  12. @@Harald Ponce de Leon Harald, I'm sorry - I have no idea why, but I rebooted the server and all is well... hrmmmmmmmmmmmmm how frustrating. Thank you for the quick reply!! David on True/Default cURL Version: 7.29.0 cURL SSL Version: NSS/3.21 Basic ECC Default Setting: Success TLS v1.2: Success
  13. it was working just fine on default since the 5.010 update. Then it seems all logging and orders ceased sometime yesterday afternoon. the server is very modern php5.6 tls 1.2 etc,,, Using the test tool I get "A general error occurred. Please try again." with both settings
  14. @@Harald Ponce de Leon
  15. WTF is going on.... the PayPal AP is not working, not logging, nothing.... not even pulling a balance... is it PayPal or the AP developer?.... I'm losing orders in droves. Express goes to page not found, standard freezes on process... I'm on 5.010... and also noted the update button is gone this morning....