Hallo,
wie haben genau das identische Problem, dass hier sagt unser Hoster (Timmehosting):
ich denke nicht, dass das Problem bei uns liegt. wenn ich vom Server aus versuche die [http://Domain](http://Domain) zu erreichen wird mir folgendes ausgegeben; -----------------%http://mws-eu.amazonservices.com:443 \* Rebuilt URL to: [http://mws-eu.amazonservices.com:443/](http://mws-eu.amazonservices.com:443/) \* Trying 54.239.39.211... \* TCP\_NODELAY set \* Connected to mws-eu.amazonservices.com (54.239.39.211) port 443 (#0)
GET / HTTP/1.1 Host: mws-eu.amazonservices.com:443 User-Agent: curl/7.58.0 Accept: */*
\< HTTP/1.1 400 Bad Request \< Server: Server \< Date: Fri, 21 Sep 2018 14:11:57 GMT \< Content-Type: text/html \< Content-Length: 265 \< Connection: close \< <title>400 The plain HTTP request was sent to HTTPS port</title><center><h1>400 Bad Request</h1></center><center>The plain HTTP request was sent to HTTPS port</center>
* * *
<center>Server</center> \* Closing connection 0 -----------------\>%----------------- -----------------%https://Domain:443 versuche zu erreichen bekomme ich folgendes: curl -v [https://mws-eu.amazonservices.com:443](https://mws-eu.amazonservices.com:443) \* Rebuilt URL to: [https://mws-eu.amazonservices.com:443/](https://mws-eu.amazonservices.com:443/) \* Trying 54.239.39.211... \* TCP\_NODELAY set \* Connected to mws-eu.amazonservices.com (54.239.39.211) port 443 (#0) \* ALPN, offering h2 \* ALPN, offering http/1.1 \* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH \* successfully set certificate verify locations: \* CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs \* TLSv1.2 (OUT), TLS header, Certificate Status (22): \* TLSv1.2 (OUT), TLS handshake, Client hello (1): \* TLSv1.2 (IN), TLS handshake, Server hello (2): \* TLSv1.2 (IN), TLS handshake, Certificate (11): \* TLSv1.2 (IN), TLS handshake, Server key exchange (12): \* TLSv1.2 (IN), TLS handshake, Server finished (14): \* TLSv1.2 (OUT), TLS handshake, Client key exchange (16): \* TLSv1.2 (OUT), TLS change cipher, Client hello (1): \* TLSv1.2 (OUT), TLS handshake, Finished (20): \* TLSv1.2 (IN), TLS change cipher, Client hello (1): \* TLSv1.2 (IN), TLS handshake, Finished (20): \* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 \* ALPN, server accepted to use http/1.1 \* Server certificate: \* subject: CN=mws-eu.amazonservices.com \* start date: Apr 23 00:00:00 2018 GMT \* expire date: Apr 23 12:00:00 2019 GMT \* subjectAltName: host "mws-eu.amazonservices.com" matched cert's "mws-eu.amazonservices.com" \* issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon \* SSL certificate verify ok.
GET / HTTP/1.1 Host: mws-eu.amazonservices.com User-Agent: curl/7.58.0 Accept: */*
\< HTTP/1.1 200 OK \< Server: Server \< Date: Fri, 21 Sep 2018 14:12:01 GMT \< Content-Type: text/xml \< Content-Length: 145 \< Connection: keep-alive \< x-mws-request-id: 7ee65d4a-458b-4755-8a21-4750257e84bc \< x-mws-timestamp: 2018-09-21T14:12:01.625Z \< x-mws-response-context: TBgrhG/gudKrLDKqphlQ5YCJSYinqaZ+YDVgt3jIlW3bRkkuxRhQIN9dJz01qjRZemaWNevM37Q= \< x-amz-rid: 81V6RK9X5291TJ6GWJVH \< Vary: Accept-Encoding,User-Agent \< <?xml version="1.0"?><pingresponse xmlns="<a" href="https://mws.amazonservices.com">"https://mws.amazonservices.com">
<timestamp timestamp="2018-09-21T14:12:01.625Z"></timestamp>
</pingresponse> \* Connection #0 to host mws-eu.amazonservices.com left intact -----------------\>%-----------------
Muss also irgendwie mit Amazon zu tun haben. Jemand eine Idee?