After logging in, an error is coming with the following:
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
(Screenshot attached)
I followed the instructions: Fix, Log out and log back in, also to restart the panel, getting the same error message, I attempted to Repair the panel from the server's CLI and then restarting it, the error is still there.
I tried: curl -v https://brandnew.aapanel.com
ping brandnew.aapanel.com -c 5
ping google.com -c 5
cat /etc/hosts
If those of any help, here's the response:
curl -v https://brandnew.aapanel.com
- Trying 172.67.171.7:443...
- Connected to brandnew.aapanel.com (172.67.171.7) 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.3 (IN), TLS handshake, Certificate (11):
- TLSv1.3 (IN), TLS handshake, CERT verify (15):
- 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 h2
- Server certificate:
- subject: CN=aapanel.com
- start date: Sep 9 05:45:33 2023 GMT
- expire date: Dec 8 05:45:32 2023 GMT
- subjectAltName: host "brandnew.aapanel.com" matched cert's "*.aapanel.com"
- issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1P5
- SSL certificate verify ok.
- Using HTTP2, server supports multiplexing
- Connection state changed (HTTP/2 confirmed)
- Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- Using Stream ID: 1 (easy handle 0x555d35fe5e90)
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
GET / HTTP/2
Host: brandnew.aapanel.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.3 (IN), TLS handshake, Newsession Ticket (4):
- old SSL session ID is stale, removing
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- TLSv1.2 (OUT), TLS header, Supplemental data (23):
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 200
< date: Fri, 15 Sep 2023 03:40:42 GMT
< content-type: text/html
< last-modified: Wed, 06 Sep 2023 02:36:39 GMT
< set-cookie: ea51a7a196c8dab799ce2c2fd69504e7=2fa7e8ce6204af6eaf0bddf14cbfdef4; expires=Fri, 15-Sep-23 15:59:59 GMT; Max-Age=44357; httponly;
< strict-transport-security: max-age=31536000
< accept-ranges: bytes
< cf-cache-status: DYNAMIC
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=D%2BZF%2Fy7jb4K5MsQAvtww2bDK8pDJLQKs5TH8poCJdX7U%2FDuz7WMY%2Bur7kh%2BI2J%2BFNGYc7ED3PBBrL%2B6obLTANTmRhqb3uNAPcFNQ3mSQM9Cw7C3H54fJpSKdhXYTMKvNxO6WIb%2Fvdg%3D%3D"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< server: cloudflare
< cf-ray: 806dd9886a517166-DUS
< alt-svc: h3=":443"; ma=86400
<
- TLSv1.2 (IN), TLS header, Supplemental data (23):
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
- TLSv1.2 (IN), TLS header, Supplemental data (23):
- Connection #0 to host brandnew.aapanel.com left intact
the pings are fine and the hosts file is the same as it was yesterday, the last time I checked the server.