push-notifications.nextcloud.com port 443 is down #2133
Labels
Comments
webagroprom
changed the title
|
Works fine here. Is it still current for you? |
|
ConnectException |
|
Since you have Cyrillic characters in your output, the only assumption I have atm is that your ISP has blocked us. |
all services are pinged |
|
Well, it works here: $ curl -L -m 10 https://push-notifications.nextcloud.com:443 -v
* Trying 2a01:4f9:2b:29dc::153:443...
* Connected to push-notifications.nextcloud.com (2a01:4f9:2b:29dc::153) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=push-notifications.nextcloud.com
* start date: Dec 3 01:03:40 2024 GMT
* expire date: Mar 3 01:03:39 2025 GMT
* subjectAltName: host "push-notifications.nextcloud.com" matched cert's "push-notifications.nextcloud.com"
* issuer: C=US; O=Let's Encrypt; CN=E6
* SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/1.1
> Host: push-notifications.nextcloud.com
> User-Agent: curl/7.81.0
> Accept: */*
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Server: nginx
< Date: Sun, 29 Dec 2024 22:26:19 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 19
< Connection: keep-alive
< X-Content-Type-Options: nosniff
<
404 page not found
* Connection #0 to host push-notifications.nextcloud.com left intact
So it has to be something being blocked by your provider, hsoter or ISP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
https://push-notifications.nextcloud.com/ is down (along with help.nextcloud.com).
in nextcloud.log :
cURL error 7: Failed to connect to push-notifications.nextcloud.com port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://push-notifications.nextcloud.com/notifications
Can you please fix it ?
curl -L -m 10 https://push-notifications.nextcloud.com:443 -v
curl: (28) Connection timed out after 10000 milliseconds
The text was updated successfully, but these errors were encountered: