support.pine64.org is down

[marty1885]

Hi all.

I was having conversations with Pine64's sales team to find out why my shipment was stopped. Then I found the support page is down one day and the sales team stops responding. Maybe that is the cause? Hopefully this thread can notify the pine teams that the page is down and they could get the page working again.

[8453sixtyfour]

Can confirm, the support site is down for me as well.

[Luke]

Thanks, will look into it.

[Luke]

It seems to be an issue with the system host. Also appears to work on some browsers (Chrome) while not others (Firefox).
While this is getting sorted out, please email support@pine64.org

[marty1885]

It seems to be an issue with the system host. Also appears to work on some browsers (Chrome) while not others (Firefox).
While this is getting sorted out, please email support@pine64.org

Thank you! FYI, I can't load the support page using either Chrom or FireFox.

[Luke]

It seems to be an issue with the system host. Also appears to work on some browsers (Chrome) while not others (Firefox).
While this is getting sorted out, please email support@pine64.org

Thank you! FYI, I can't load the support page using either Chrom or FireFox.

Could you try to clear cache and cookies and attempt again?

[marty1885]

Could you try to clear cache and cookies and attempt again?

Yes, it doesn't work even after cleaning cache or using other browsers like Epiphany(Gnome Web). cURL also comes up with nothing

Code:

*   Trying 136.143.190.74:443...
* Connected to support.pine64.org (136.143.190.74) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
 CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* 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=support.iaminweb.com
*  start date: Mar  4 13:01:37 2020 GMT
*  expire date: Jun  2 13:01:37 2020 GMT
*  subjectAltName: host "support.pine64.org" matched cert's "support.pine64.org"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
> GET / HTTP/1.1
> Host: support.pine64.org
> User-Agent: curl/7.69.1
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 301
< Server: ZGS
< Date: Mon, 13 Apr 2020 15:10:09 GMT
< Content-Type: text/html;charset=UTF-8
< Content-Length: 9
< Connection: keep-alive
< Set-Cookie: 34f6831605=7a9b9629f4a8678e41deb8190cc04fa7; Path=/
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1
< Set-Cookie: crmcsr=ff6f8914-e12f-4b51-8f61-a469095f734a;path=/;SameSite=None;Secure;priority=high
< Pragma: no-cache
< Cache-Control: no-cache
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< X-Frame-Options: SAMEORIGIN
< Set-Cookie: JSESSIONID=6EFA9AE7954E23ABD56020C3800B30EF; Path=/; Secure
< Strict-Transport-Security: max-age=63072000
<









* Connection #0 to host support.pine64.org left intact

In fact, the response I get from the page is very weird. It's a HTTP 301 but no location information. The server is redirecting me but doesn't tell me where to go.

[sundog]

While this is getting sorted out, please email support@pine64.org

I can't even email support anymore - mx.zoho.com is rejecting mail "due to antispam policy" for any email address @pine64.org that I attempt to email.

I was able to email back and forth with support@pine64.org previously from the same email address, mail server, and IP address I am currently using, so it looks like a change on your end broke mail delivery for some percentage of your customers. For reference, the email is coming from domain reclaim.technology

---

While this is getting sorted out, please email support@pine64.org

I can't even email support anymore - mx.zoho.com is rejecting mail "due to antispam policy" for any email address @pine64.org that I attempt to email.

I was able to email back and forth with support@pine64.org previously from the same email address, mail server, and IP address I am currently using, so it looks like a change on your end broke mail delivery for some percentage of your customers. For reference, the email is coming from domain reclaim.technology

Emailing support@pine64.org from a different email address results in an auto-response directing me to use the ticketing system at support.pine64.org:


Dear Backer/Maker,

In order to serve you better, we have implemented the support ticket system.  Please kindly file a support ticket at https://support.pine64.org with full detail of the issues you are facing. Our support team will response your ticket within 48 hours.

Thanks.

Regards,
PINE64 Support Team

[Luke]

Admins are looking into it. Looks like an issue with zoho :/

[sundog]

Thanks for the update, @Luke