Jump to content

Daniel D

Members
  • Posts

    55
  • Joined

  • Last visited

Contact Methods

Profile Information

  • Location
    Melbourne Australia
  • Interests
    Photography
  • Activity
    Project Owner

Daniel D's Achievements

Newbie

Newbie (1/14)

2

Reputation

2

Community Answers

  1. Mon problem avec Paypal a ete resolu il y a plusieurs mois.. C'etait in probleme avec Paypal et mon addresse IP . J'ai du changer de server.
  2. Thanks for the reply. Everything is working very well now! Cheers Daniel
  3. Hi Thanks for the help. I replaced l'}" rel="ajax_id_product_{$accessory.id_product|intval}" title="{l s='Add to cart'}">{l s='Add to cart'}</a> with l'}" rel=data-id-product="{$accessory.id_product|intval}" title="{l s='Add to cart'}">{l s='Add to cart'}</a> I cleared the cache and I still get Product not found This product is no longer available when I click on Add to Cart I hope there is another solution. Thanks Daniel
  4. When I click "Add to Cart" button in the Accessories Tab, I get the following message: "Product not found This product is no longer available." The view button works well. I use Prestashop 1.6.0.9 Please click the following link to see the problem on my website: http://www.studioworks.com.au/century-c-stand/heavy-duty-c-stand-with-boom-arm I hope someone can help Thanks Daniel
  5. Thanks for the prompt reply. I turned on option "friendly urls" and now i get : http://www.studioworks.com.au/radio-triggers/90-radio-flash-trigger.html?live_configurator_token=2c343c8a764ffc1c5b30f158d988ff01&id_shop=1&id_employee=1&theme=theme5&theme_font=font5
  6. At the moment the url I get for all my pages is in this format: "http://www.studioworks.com.au/index.php?id_product=90&controller=product" http://www.studioworks.com.au/index.php?id_product=90&controller=product How can I change it so that it shows the name of the products like I wrote it in the friendly url In the back office It says: "The product link will look like this http://www.studioworks.com.au/lang/90-radio-flash-trigger.html I am not getting anything like it. I hope someone can help!
  7. After 2 weeks of getting nowhere and the inability from the Paypal team to fix my issue, my host migrated my website to a different server with a new IP and now everything is working fine. Case is finally closed.
  8. I updated the paypal module to the latest version 3.10.1 Deleted it and re-installed it 3 times. Unfortunately no result.
  9. I finally got a reply from Paypal. After one week!!! here is their reply: "According to our(PayPal) logs, the merchant has attempted to connect 6 times to 3 different IPs associated with api-3t in the last 7 days. 4 - 173.0.92.21 1 - 173.0.84.101 1 - 173.0.88.101 The 173.0.92.21 was removed from DNS on 7/25 which means that it was probably wired off from api. The fact the merchant attempted to connect to this IP after it was removed from DNS indicates the merchant is using hardcoded IPs in their application configuration instead of using DNS. The other two attempts to the current api servers were both attempts over port 80. api-3t does not accept connections over port 80, they must use 443. Recommend to Merchant: Remove any references to api-3t by IP address in merchant’s application Ensure all connection attempts are using TLS with the default port (443)" ============================================================================================================== I don't understand the 2 recommendations to merchant. Could someone explain? Is there anything I could do on my side? Thanks
  10. I am hitting desperation point. And Paypal still doesn't get back to me despite calling them every day! This is the last reply from my host: """If that is normal behavior for paypal telent SSL connection than it means that the connection is established. I see that the outoging connections filter is disabled so there is no way that the connection is being filtered from the VPS and I also see that ModSecurity has been disabled for the affected host. I really don't see what else we could do regarding this case. Still PayPal should be the one that support their plugins/modules so its their opinion that would matter the most...""""
  11. Hi Thanks for getting back to me so quickly This is the reply from my host: "It looks like the connection gets closed by the foreign host after about half a minute after it gets established."
  12. Hi Thanks for the help. I contacted my host to telnet to paypals gateway on port 443 and they got: telnet api-3t.paypal.com 443 Trying 173.0.92.21... Connected to api-3t.paypal.com. Escape character is '^]'. Connection closed by foreign host. I am still waiting for Paypal to reply :-(
  13. My saga is not over!!!! I contacted again my hosting company and sent them Paypal reply. They answered within minutes and according to them Paypal is at fault. Here is the message they sent me which I forwarded to Paypal: "The trace route that they have requested is available below: traceroute api-3t.paypal.com traceroute to api-3t.paypal.com (173.0.84.101), 30 hops max, 60 byte packets 1 202.87.31.155 (202.87.31.155) 0.049 ms 0.015 ms 0.013 ms 2 bdr.mx1.eqx.sis.net.au (122.252.0.193) 7.818 ms 7.980 ms 7.969 ms 3 ten-0-2-0-922.bdr02.syd03.nsw.VOCUS.net.au (114.31.200.141) 7.934 ms 7.932 ms 7.916 ms 4 ten-0-2-0-5.cor03.syd03.nsw.VOCUS.net.au (114.31.192.60) 163.774 ms 163.908 ms 164.152 ms 5 ten-0-1-0-4.cor01.syd04.nsw.VOCUS.net.au (175.45.72.120) 163.694 ms ten-0-5-0-1.cor01.syd04.nsw.VOCUS.net.au (175.45.72.118) 163.394 ms 163.395 ms 6 ten-0-0-0-1.cor02.sjc01.ca.VOCUS.net (114.31.199.36) 163.791 ms ten-0-1-0-1.cor02.sjc01.ca.VOCUS.net (114.31.199.44) 160.122 ms ten-0-0-0-2.cor01.sjc01.ca.VOCUS.net (114.31.199.29) 159.687 ms 7 bundle-100.bdr03.sjc01.ca.VOCUS.net (114.31.199.123) 160.557 ms 157.008 ms bundle-100.cor02.sjc01.ca.VOCUS.net (114.31.199.59) 156.019 ms 8 bundle-100.bdr03.sjc01.ca.VOCUS.net (114.31.199.123) 157.111 ms 157.761 ms ae8-561.sjc12.ip4.gtt.net (46.33.90.49) 183.791 ms 9 ae8-561.sjc12.ip4.gtt.net (46.33.90.49) 178.607 ms paypal-gw.ip4.gtt.net (173.205.56.6) 184.162 ms 184.189 ms 10 64.4.244.160 (64.4.244.160) 177.689 ms paypal-gw.ip4.gtt.net (173.205.56.6) 178.234 ms 64.4.244.152 (64.4.244.152) 183.798 ms 11 64.4.244.100 (64.4.244.100) 201.186 ms 64.4.244.160 (64.4.244.160) 183.877 ms 183.671 ms 12 64.4.244.94 (64.4.244.94) 197.324 ms 203.198 ms 64.4.244.84 (64.4.244.84) 196.167 ms 13 64.4.244.80 (64.4.244.80) 202.208 ms * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * You can see that we are not able to reach their API from the VPS (203.56.191.195) and the trace stops at their IP address 64.4.244.80: http://whatismyipaddress.com/ip/64.4.244.80 The IP is definitely blocked at their end." Hopefully I will see the end on it soon!! Happy to hear from anyone if you have some ideas!!!
  14. I just got a reply from Paypal Technical Support Team (finally after 3 days!!) with the following message: Daniel, sorry for the delayed response. Our network team confirmed the following : "After observing at this IP, we do not see any blocking or preventing access to 203.56.191.195." If this is the IP from where your API requests are originating from, then it is confirmed that PayPal is not blocking that IP. Based on this, I wanted you try the following from the server that is sending these requests. - Run a traceroute to the endpoint that you are trying to connect to. Command to be ran is : tracert api-3t.paypal.com Please provide me with the outcome."
×
×
  • Create New...