Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Forecast.Solar Forecast.Solar
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Issue trackers
  • Forecast.SolarForecast.Solar
  • Issues
  • #23

Closed
Open
Created Aug 20, 2021 by Ryan May@spockmay1 of 3 tasks completed1/3 tasks

API is returning 502 errors

Quick Information

  • Device: Computer / Tablet / Mobile
  • Operating System:

What Happened?

API is down and not returning any data. Every call returns an HTTP 502 error

Expected result

API returns data and HTTP 200

Steps to reproduce

Call any API

Screenshots

`$ curl -v https://api.forecast.solar/estimate/52/12/37/0/5.27

  • Trying 91.228.53.233...

  • TCP_NODELAY set

  • Connected to api.forecast.solar (91.228.53.233) 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-AES256-GCM-SHA384

  • ALPN, server accepted to use http/1.1

  • Server certificate:

  • subject: CN=forecast.solar

  • start date: Jul 5 21:31:42 2021 GMT

  • expire date: Oct 3 21:31:41 2021 GMT

  • subjectAltName: host "api.forecast.solar" matched cert's "*.forecast.solar"

  • issuer: C=US; O=Let's Encrypt; CN=R3

  • SSL certificate verify ok.

GET /estimate/52/12/37/0/5.27 HTTP/1.1 Host: api.forecast.solar User-Agent: curl/7.52.1 Accept: /

< HTTP/1.1 502 Bad Gateway < Server: nginx < Date: Fri, 20 Aug 2021 18:56:02 GMT < Content-Type: text/html < Content-Length: 1254 < Connection: keep-alive < Keep-Alive: timeout=60 < ETag: "5ebc2284-4e6" <

500 — Internal Sever Error body {font-size:14px; color:#777777; font-family:arial; text-align:center;} h1 {font-size:180px; color:#99A7AF; margin: 70px 0 0 0;} h2 {color: #DE6C5D; font-family: arial; font-size: 20px; font-weight: bold; letter-spacing: -1px; margin: -3px 0 39px;} p {width:320px; text-align:center; margin-left:auto;margin-right:auto; margin-top: 30px } div {width:320px; text-align:center; margin-left:auto;margin-right:auto;} a:link {color: #34536A;} a:visited {color: #34536A;} a:active {color: #34536A;} a:hover {color: #34536A;}

api.forecast.solar

<h1>500</h1>
<h2>Internal Server Error</h2>
<div>
    Sorry, something went wrong :(
</div>
* Curl_http_done: called premature == 0 * Connection #0 to host api.forecast.solar left intact `

Priority/Severity

  • High (anything that impacts the normal user flow or blocks app usage)
  • Medium (anything that negatively affects the user experience)
  • Low (anything else e.g., typos, missing icons, layout issues, etc.)
Assignee
Assign to
Time tracking