search

netresearch / dhl-shipping-m2

DHL multi-division shipping extension for Magento 2
Open Software License 3.0
13 stars 4 forks source link

Versandetikett konnte nicht erstellt werden: Web service request failed. #39

Closed Assambra closed 2 years ago

Assambra commented 2 years ago

I get the following error message when I want to create a shipping label.

"Versandetikett konnte nicht erstellt werden: Web service request failed."

I called DHL to see if there was a problem. There I was told that a new polling interface has been active since Thursday and that I should update the module. But that did not bring the desired success.

Any ideas?

codingcoast commented 2 years ago

I have the same problem since today. But can‘t find any errors in my logs.

Assambra commented 2 years ago

I called DHL again. There would be a message in the developer forum that IP addresses or urls have changed. Can you please bring a solution quickly. So that we can ship from the shop again.

codingcoast commented 2 years ago

Can you share IPs / Urls please?

mam08ixo commented 2 years ago

The IPs did change but we use the hostname for web service communication. Possible reasons for communication errors are DNS cache issues, firewall settings, or server certificates. I am afraid you have to check in your environment why the service cannot be accessed.

Here is the information from DHL:

Umstellung erfolgt am 16.10.2021 zwischen 8-12 Uhr

Domain: cig.dhl.de Bisherige IP-Adresse: 149.239.125.123 Neue IP-Adresse: 20.93.184.24 Neue Zertifikate: https://entwickler.dhl.de/webdav/ep/document_library/CIG/CIG%20Zertifikat/12.10.2021/cig.dhl.de.zip

colaholiker commented 2 years ago

[2021-10-17 01:01:04] main.ERROR: Product lists update failed. {"exception":"[object] (RuntimeException(code: 0): SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl' : failed to load external entity \"https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl\" at /srv/www/bad-reichenhaller-shop.de/html/vendor/deutschepost/sdk-api-prodws/src/Service/ServiceFactory.php:34, SoapFault(code: 0): SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl' : failed to load external entity \"https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl\" at /srv/www/bad-reichenhaller-shop.de/html/vendor/deutschepost/sdk-api-prodws/src/Service/ServiceFactory.php:32)"} [] [2021-10-17 01:01:04] main.ERROR: Scheduled product lists update failed. {"exception":"[object] (Magento\Framework\Exception\CouldNotSaveException(code: 0): Produktlisten konnten nicht aktualisiert werden: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl' : failed to load external entity \"https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl\" at /srv/www/bad-reichenhaller-shop.de/html/vendor/deutschepost/module-internetmarke/Model/ProductList/Updater.php:73)"} []

colaholiker commented 2 years ago

C:\Users\colaholiker>nslookup - ns.deutschepost.de Standardserver: ns.deutschepost.de Address: 149.239.160.100

prodws.deutschepost.de Server: ns.deutschepost.de Address: 149.239.160.100

Name: prodws.deutschepost.de Address: 149.239.115.11

C:\Users\colaholiker>ping prodws.deutschepost.de

Ping wird ausgeführt für prodws.deutschepost.de [149.239.115.11] mit 32 Bytes Daten: Zeitüberschreitung der Anforderung.

Ping-Statistik für 149.239.115.11: Pakete: Gesendet = 1, Empfangen = 0, Verloren = 1 (100% Verlust), STRG-C ^C

colaholiker commented 2 years ago

Guten Morgen, sorry das ich das so einfach reinwerfe ohne überarbeitung. Kann jemand bestätigen das er auch diesen Fehler hat. Und ebenfalls die angegebene IP nicht pingen kann.

Mit freundlichen Grüßen Sebastian

mam08ixo commented 2 years ago

@colaholiker I am not sure your Deutsche Post WSDL issue is related to the DHL API issue this ticket deals with. You cannot ping the URL.

However, I can click the link from your log and I can also download the WSDL.

wget --verbose https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl
--2021-10-18 10:36:08--  https://prodws.deutschepost.de:8443/ProdWSProvider_1_1/prodws?wsdl
Auflösen des Hostnamens prodws.deutschepost.de (prodws.deutschepost.de) … 149.239.115.11
Verbindungsaufbau zu prodws.deutschepost.de (prodws.deutschepost.de)|149.239.115.11|:8443... verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: 12469 (12K) [text/xml]
Wird in »prodws?wsdl« gespeichert.

prodws?wsdl                                        100%[===============================================================================================================>]  12,18K  --.-KB/s    in 0s      

2021-10-18 10:36:09 (295 MB/s) - »prodws?wsdl« gespeichert [12469/12469]
Assambra commented 2 years ago

I know from the change of my own server ip address for my url that it can take up to 48 hours for it to spread worldwide. it makes sense to use the IP for a short time until all nameservers have updated themselves. How can you change that the module uses the ip instead of the url?

Update: now the error message changed to Versandetikett konnte nicht erstellt werden: login failed

mam08ixo commented 2 years ago

@Assambra You could probably modify the WSDL URL and service location in the ServiceFactory if it is that urgent.

Customers report that things are getting back to normal with no further action from their side.

colaholiker commented 2 years ago

yes, is back to normal. @Assambra or you can add the ip in your hosts file (/etc/hosts)

Assambra commented 2 years ago

Ok it works now without any changes

ngolatka commented 2 years ago

I (and lots of support customers I dealt with this morning) can confirm the same thing: the problem is magically disappearing. Seems like DNS propagation was a bit slower than usual.

If it doesn't work yet for everybody, I suggest being patient. It will probably work fine within the next few hours. If not: check your firewall if you need to whitelist the new IP address (see above).