Cannot connect to nab.sunnyvalley.cloud

Follow

netadmin

• July 07, 2023 07:16
• Edited

Hi, i have a problem and my pfsense router cannot connect to the cloud server. When i installed it was connected but after some days i noticed that is not connected to the cloud. The logs are:

NAB Connect: Get "https://nab.sunnyvalley.cloud/node/connect": dial tcp 35.184.76.118:443: connect: operation timed out

 

Also i tried with curl and stucks in:

Trying 35.184.76.118:443...

I have extra floating ips on my router and when i am trying the curl with one of my floating ips it sends the request. I search if my ip is blocked and it is clear and i did a packet capture and i saw that i have only tcp retransmissions. Maybe my ip is blocked from your cloud because with curl i can connect to any other site.

Thanks.

0

• Official comment

  

  SVN Support Team

  • July 07, 2023 11:14

  Hi,

  Can you reach the website dash.zenarmor.com? Please stop the the engine service and try again that maybe you cloud block it via a policy rule. To stop engine run the command in the console as root "service eastpect stop"

  Comment actions Permalink
• 

  netadmin

  • July 07, 2023 11:22
  • Edited

  Hi and thanks for the quick replay. I restarted the eastpect service but the problem exists. When i do "curl -v https://dash.zenarmor.com" it returns:

  *   Trying 104.21.75.134:443...
  * Connected to dash.zenarmor.com (104.21.75.134) port 443 (#0)
  * ALPN: offers h2,http/1.1
  * TLSv1.3 (OUT), TLS handshake, Client hello (1):
  *  CAfile: /usr/local/share/certs/ca-root-nss.crt
  *  CApath: /etc/ssl/certs/
  * 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 h2
  * Server certificate:
  *  subject: CN=zenarmor.com
  *  start date: May 30 08:59:15 2023 GMT
  *  expire date: Aug 28 08:59:14 2023 GMT
  *  subjectAltName: host "dash.zenarmor.com" matched cert's "*.zenarmor.com"
  *  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1P5
  *  SSL certificate verify ok.
  * using HTTP/2
  * h2 [:method: GET]
  * h2 [:scheme: https]
  * h2 [:authority: dash.zenarmor.com]
  * h2 [:path: /]
  * h2 [user-agent: curl/8.1.0]
  * h2 [accept: */*]
  * Using Stream ID: 1 (easy handle 0x8336ae800)
  > GET / HTTP/2
  > Host: dash.zenarmor.com
  > User-Agent: curl/8.1.0
  > Accept: */*
  >
  * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  * old SSL session ID is stale, removing
  < HTTP/2 302
  < date: Fri, 07 Jul 2023 11:18:30 GMT
  < content-type: text/html; charset=UTF-8
  < location: https://dash.zenarmor.com/login
  < set-cookie: PHPSESSID=n5081p61357e4rri39vs6688dn; path=/; secure; HttpOnly
  < expires: Thu, 19 Nov 1981 08:52:00 GMT
  < cache-control: no-store, no-cache, must-revalidate
  < pragma: no-cache
  < x-xss-protection: 1; mode=block
  < x-content-type-options: nosniff
  < cf-cache-status: DYNAMIC
  < report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=if2hD53%2B8P5soWkKDjUh5ahSIVCHnF%2FMSqfCO8moKbhwurEcm7d5jjOYtT4tAAreH%2B5X7Avflh2ehjQa4M44SKRVDf%2BtdJshpEH7u6SRnw%2FZKNFD4z6I0reHUeUYxpqRXDpO0g%3D%3D"}],"group":"cf-nel","max_age":604800}
  < nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
  < server: cloudflare
  < cf-ray: 7e2fafe96e3b0394-FRA
  < alt-svc: h3=":443"; ma=86400
  <

   

   

  Without "-v" it returns nothing.

  Thanks.

  0

  Comment actions Permalink
• 

  SVN Support Team

  • July 07, 2023 17:33

  Hi,

  Please share the following log file

  /usr/local/zenarmor/log/active/cloud_agent.log file to support@sunnyvalley.io

  0

  Comment actions Permalink
• 

  netadmin

  • July 07, 2023 19:34

  I sent the email twice, one from my email and the second from my company's  email.

  Thanks

  0

  Comment actions Permalink

Please sign in to leave a comment.