Search the Community
Showing results for tags 'TLS'.
-
Hi, I'm trying to setup a prestashop 1.7.8.x using the included docker-compose.yaml but behind traefik. traefik as reverse proxy manages the TLS part and then connects to the apache on your image using plain 80/tcp. unfortunately I get into a redirect loop to https://${PS_DOMAIN}/. how can I disable that behavior? update: it's worth mentioning that injecting a simple script the the following, works as intended and without redirect. <?php phpinfo; ?> and shows X-Forwarded-Proto being set to https
-
OK, już powoli tracę nadzieję Konfiguracja SMTP, niby rzecz oczywista i prosta, podstawowa funkcjonalność sklepu -nie działa. Nie dziwiłbym się gdyby był to jakiś egzotyczny system, wersja web serwera lub inna niestandardowa konfiguracja środowiska, ale nie ... system nowo postawiony, wszystko z paczek, świeża instalacja PS i .. zima Do rzeczy: Problem polega na braku możliwości wysyłania poczty via serwer SMTP (hosting własnej domeny na ZOHO.com). Konfiguracja TLS, test przez moduł konfiguracji SMTP działa bez problemu. Testowo robię zakupy i ponawiam wysłanie mejla do klienta (przez moduł Zamówienia). Wtedy nie działa i widzę w logu PS: Swift Error: Failed to authenticate on SMTP server with username \"[email protected]\" using 2 possible authenticators Nie pomaga zmiana PS na inną wersję (próbowałem 1.7.0.6 i 1.6.1.11 - tę mam obecnie). Nie pomaga zmiana rodzaju połączenia na SSL. Nie pomaga zmiana wersji językowej. PrestaShop version: 1.6.1.11 Current theme in use: default-bootstrap Server information: Linux #88-Ubuntu SMP Wed Mar 8 16:34:45 UTC 2017 x86_64 Server software version: Apache PHP version: 7.0.15-0ubuntu0.16.04.4 MySQL version: 5.7.17-0ubuntu0.16.04.1 MySQL server: localhost Mail method: You are using your own SMTP parameters. SMTP server: smtp.zoho.com SMTP username: Defined SMTP password: Defined Encryption: tls SMTP port: 587 Dziękuję za wsparcie
-
Hi guys, we got an email from our payment provider that we need to upgrade to TLS 1.2, without even specifying for what or where exactly. So after some research I believe I concluded that they meant that the server needed to be checked if TLS 1.2 is supported. Checked all my browsers, sure enough, they are all newest versions, so they all check out: (quick way to check you browser, mobile or desktop) https://www.ssllabs.com/ssltest/viewMyClient.html Since there is no dedicated TLS checker like there is for SSL, I had to use that one, and only couple of those checker even mention what TLS protocols are supported: https://cryptoreport.websecurity.symantec.com/checker/ Protocols enabled: TLS1.2 TLS1.1 TLS1.0 Is there anything else you would like to recommend checking? This relates to all payment modules, since if the payment platform starts to refuse TLS 1.0 and you don't support TLS 1.2, then you won't be able to get any payments...
-
Hallo, seit dem Paypal umgestellt hal, geht Paypal nicht meht richtig. Kunden können Paypal nicht mehr nutzen. Aus der Seite meines Providers "DF" sind alle erforderlichen Ein stelliungen seit langen durchgeführt worden. Es kann doch nicht sein, dass die Umstellung von PayPal jeder Kunde = zb. ich, die im System erforderlich sind einrichtungen muss. Habt ihr da zu Erfahrung? Merchants and partners use HTTPS to securely connect with PayPal’s servers. We use the Transport Layer Security (TLS) protocol to encrypt these communications. To ensure the security of our systems and adhere to industry best practices, PayPal is updating its services to require TLS 1.2 for all HTTPS connections. At this time, PayPal will also require HTTP/1.1 for all connections. https://www.paypal-notice.com/en/TLS-1.2-and-HTTP1.1-Upgrade/ https://github.com/paypal/TLS-update
-
PayPal Merchant Technical Services merchant centre contacted me today. They said there is a Poodle vulnerability issue so are cancelling SSL3.0 and changing to TLS on dec 3rd. They said I need to contact my ecommerce platform providers to ensure there is no problem. Is there anything which needs changing or adapting before this happens?
-
Hi all. Prestashop v. 1.6.0.9 Paypal module v. 3.8.1 I have a problem regarding paypal payments due to presence of warning mixed contents, signalling by console browser (Google Chrome and Mozilla Firefox). These warnings are originated by images and product pictures when I click a possible item of interest for a client, checking express paypal payment button. These warning are related to normal size picture and miniatures and so on some other images, but all these ones are images of product example in the default theme of Prestashop 1.6.0.9 that I am using. I add an example of a possible warning list that I received when I try to perform a paypal payment: http://mysite.domain/shop/img/friendly-url-1416946913.jpg http://mysite.domain/shop/img/c/3-0_thumb.jpg http://mysite.domain/shop/img/c/3-1_thumb.jpg http://mysite.domain/shop/8-small_default/printed-dress.jpg http://mysite.domain/shop/20-small_default/printed-chiffon-dress.jpg http://mysite.domain/shop/modules/blockstore/store.jpg the page contains unsecured mixed contents...need to use a https secure connection instead of http. /shop/ folder is the directory in which I am building my prestashop store. So, my topic is a help request. Please, can anyone help me suggesting how change the loading of these images from http to https, or other possibility to fix this issue? Thank you in advance. Gionata
- 2 replies
-
- mixedcontent
- error
- (and 6 more)
-
Hi all, Since the SSL v3 issue (also known as POODLE) was identified on October 14, PayPal has decided to completely disable SSL 3.0 support at 12:01 a.m. Pacific Standard Time on December 3, 2014. POODLE is an internet security vulnerability that impacts the Secure Sockets Layer (SSL) 3.0 protocol, which was designed to ensure secure connections when surfing on the Internet. As a consequence all PayPal merchant customers using PrestaShop need to update their PayPal integration by upgrading their PayPal module on PrestaShop before December 3rd disable SSL 3.0 for their client interactions. If you do not upgrade your PayPal module on PrestaShop by this date, you may face interruptions to your ability to accept payments with PayPal. To make sure your integration is protected against this vulnerability and to keep accepting PayPal payments beyond this date, you need to upgrade your PayPal module to version 3.8.0 by following these steps: Users of version 1.5 and 1.6 of PrestaShop 1- Go to PrestaShop back office in the list of modules installed 2- Click on the « Update it » button next to PayPal module If this button doesn’t appear, please follow the same steps as the ones described below for “users of version 1.4 de PrestaShop” The upgrade to version 3.8.0 will then complete. If it doesn’t, please follow the steps below. Users of version 1.4 of PrestaShop 1. Go to the PrestaShop Addons website and download the latest version of the PayPal module (version 3.8.0) 2. You need to carry out a manual update of the module. Please go to the “Modules” section in the Back Office of your store 3. Click on “Upload the module from your computer” , you should get the screen below: 4. Insert the downloaded file in zip format 5. Click on « Upload this module » The upgrade to version 3.8.0 will then complete. Caution: If the message "Before using the module, you must install the compatibility Retro Module" appears after your being updated, thank you download and install the "Retro compatibility" module at this address: http://addons.presta...patibility.html We make every effort to help you as quickly as possible and we apologize for any inconvenience due to this problem. Regard, PayPal Iberia
-
Hi all , I'm having problems setting up SMTP mail in prestashop . I'm using Live domains. Domain mail: blank SMTP server: smtp.live.com SMTP user: [email protected] SMTP Pass: mypass Encryption : TLS PORT : 587 Prestashop 1.5.3.1 tells me: The SMTP connection failed to start [tls://smtp.live.com:587]: fsockopen returned Error Number 0 and Error String '' I tried everything and always gives me the same error. If I use Thunderbird everything works fine the only diference is that when I choose the encryption Thunderbird suggest me STARTTLS instead of TLS/SSL. If I use TLS/SSL I cant send mail trough the smtp.live.com server. Temporarily I'm using google apps smtp servers without problems but it is not what I need. Thanks in advance. Greetings from Peru.