SOAP-ERROR Parsing WSDL Couldn t load from - but works on WAMP

Question

This works fine on my WAMP server  but doesn t work on the linux master server    try       client   new SoapClient  http   ec europa eu taxation customs vies checkVatService wsdl     trace    gt  true         result    client- gt checkVat            countryCode    gt   DK            vatNumber    gt   47458714              print r  result     catch Exception  e       echo  e- gt getMessage        What am I missing here       SOAP is enabled  Error  SOAP-ERROR  Parsing WSDL  Couldn t load from  http   ec europa eu taxation customs vies checkVatService wsdl    failed to load external entity  http   ec europa eu taxation customs vies checkVatService wsdl  taxation customs vies checkVatService wsdl    Call the URL from PHP  Calling the URL from PHP returns error   wsdl   file get contents  http   ec europa eu taxation customs vies checkVatService wsdl    echo  wsdl    Error  Warning   file get contents http   ec europa eu taxation customs vies checkVatService wsdl   failed to open stream  HTTP request failed  HTTP 1 0 503 Service Unavailable   Call the URL from command line  Calling the URL from the linux command line HTTP 200 is returned with a XML response  curl http   ec europa eu taxation customs vies checkVatService wsdl

User · Answer

Adding  wsdl at the end and calling the method    client- gt   setLocation  url wsdl       helped to me

User · Answer

For some versions of php  the SoapClient does not send http user agent information  What php versions do you have on the server vs your local WAMP   Try to set the user agent explicitly  using a context stream as follows   try        opts   array           http    gt  array               user agent    gt   PHPSoapClient                        context   stream context create  opts         wsdlUrl    http   ec europa eu taxation customs vies checkVatService wsdl        soapClientOptions   array           stream context    gt   context           cache wsdl    gt  WSDL CACHE NONE              client   new SoapClient  wsdlUrl   soapClientOptions         checkVatParameters   array           countryCode    gt   DK            vatNumber    gt   47458714               result    client- gt checkVat  checkVatParameters       print r  result     catch Exception  e        echo  e- gt getMessage        Edit  It actually seems to be some issues with the web service you are using  The combination of HTTP over IPv6  and missing HTTP User Agent string  seems to give the web service problems   To verify this  try the following on your linux host   curl  -A     -6 http   ec europa eu taxation customs vies checkVatService wsdl   this IPv6 request fails   curl  -A  cURL User Agent   -6 http   ec europa eu taxation customs vies checkVatService wsdl   this IPv6 request succeeds   curl  -A     -4 http   ec europa eu taxation customs vies checkVatService wsdl curl  -A  cURL User Agent   -4 http   ec europa eu taxation customs vies checkVatService wsdl   both these IPv4 request succeeds   Interesting case    I guess your linux host resolves ec europa eu to its IPv6 address  and that your version of SoapClient did not add a user agent string by default

User · Answer

You cant blame code all the time sometime may be your url is wrong   double check urls

User · Answer

It may be helpful for someone  although there is no precise answer to this question   My soap url has a non-standard port 9087 for example   and firewall blocked that request and I took each time this error      ERROR - 2017-12-19 20 44 11 --  Fatal Error - SOAP-ERROR  Parsing   WSDL  Couldn t load from  http   soalurl test 9087 orawsv wsdl      failed to load external entity  http   soalurl test 9087 orawsv wsdl    I allowed port in firewall and solved the error

User · Answer

Try changing   client   new SoapClient  http   ec europa eu taxation customs vies checkVatService wsdl     trace    gt  true      to   client   new SoapClient  http   ec europa eu taxation customs vies checkVatService wsdl     trace    gt  true   cache wsdl    gt  WSDL CACHE MEMORY      Also  whether that works or not   check to make sure that  tmp is writeable by your web server and that it isn t full

User · Answer

I use the AdWords API  and sometimes I have the same problem  My solution is to add  ini set  default socket timeout   900   on the file vendor googleads googleads-php-lib src Google AdsApi AdsSoapClient php line 65  and in the vendor googleads-php-lib src Google AdsApi Adwords Reporting v201702 ReportDownloader php line 126 ini set  default socket timeout   900    requestOptions  stream context    http    timeout      900    Google package overwrite the default php ini parameter   Sometimes  the page could connect to  https   adwords google com ap   i adwords mcm v201702 ManagedCustomerService wsdl and sometimes no  If the page connects once  The WSDL cache will contain the same page  and the program will be ok until the code refreshes the cache

User · Answer

Try enabling openssl extension in your php ini if it is disabled  This way I could access the web service without need of any extra arguments  i e     client   new SoapClient url

User · Answer

None of the above works for me  so after a lot of research  I ended up pre-downloading the wsdl file  saving it locally  and passing that file as the first parameter to SoapClient    Worth mentioning is that file get contents  serviceUrl  returned empty response for me  while the url opened fine in my browser  That is probably why SoapClient also could not load the wsdl document  So I ended up downloading it with the php curl library  Here is an example   ch   curl init    curl setopt  ch  CURLOPT URL   serviceUrl   curl setopt  ch  CURLOPT RETURNTRANSFER  TRUE    wsdl   curl exec  ch   curl close  ch     wsdlFile     tmp service wsdl   file put contents  wsdlFile   wsdl     client   new SoapClient  wsdlFile     You can of course implement your own caching policy for the wsdl file  so it won t be downloaded on each request

User · Answer

I might have read all questions about this for two days  None of the answers worked for me  In my case I was lacking cURL module for PHP  Be aware that  just because you can use cURL on terminal  it does not mean that you have PHP cURL module and it is active  There was no error showing about it  Not even on  var log apache2 error log How to install module   replace version number for the apropiated one  sudo apt install php7 2-curl sudo service apache2 reload

User · Answer

Try this  I hope it helps   options          cache wsdl        gt  WSDL CACHE NONE       trace             gt  1       stream context    gt  stream context create                         ssl    gt                     verify peer          gt  false                   verify peer name     gt  false                   allow self signed    gt  true                                    client   new SoapClient  url   options

User · Answer

After hours of analysis reading tons of logs and internet  finally found problem  If you use docker and php 7 4  my case  you probably get error because default security level in OpenSSL it too high for wsdl cert  Even if you disable verify and allow self-signed in SoapClient options  You need lower seclevel in  etc ssl openssl cnf from DEFAULT SECLEVEL 2 to DEFAULT SECLEVEL 1  Or just add into Dockerfile RUN sed -i  quot s DEFAULT SECLEVEL 2 DEFAULT SECLEVEL 1 g quot   etc ssl openssl cnf  Source  https   github com dotnet runtime issues 30667 issuecomment-566482876  You can verify it by run on container curl -A  cURL User Agent  -4 https   ewus nfz gov pl ws-broker-server-ewus services Auth wsdl  Before that change I got error  SSL routines tls process ske dhe dh key too small

User · Answer

This issue can be caused by the libxml entity loader having been disabled   Try running libxml disable entity loader false   before instantiating SoapClient

User · Answer

503 means the functions are working and you re getting a response from the remote server denying you  If you ever tried to cURL google results the same thing happens  because they can detect the user-agent used by file get contents and cURL and as a result block those user agents  It s also possible that the server you re accessing from also has it s IP address blackballed for such practices   Mainly three common reasons why the commands wouldn t work just like the browser in a remote situation   1  The default USER-AGENT has been blocked  2  Your server s IP block has been blocked  3  Remote host has a proxy detection

[php] SOAP-ERROR: Parsing WSDL: Couldn't load from - but works on WAMP

Examples related to php

Examples related to soap