i added my credit card and all of that crap. i test by using the free static deployment. cant even access my site.
https://joecooldoo.replit.app/
was deploying so I can access a .sh file using curl on another computer
the site loads fine for me
1 Like
Joecooldoo,
Unfortunately I can’t reproduce the issue you are seeing. When I run a curl -v I get the following. Can you run this command exactly?
[Replit] [aelchert] [11:29:48] [~]: curl -v https://joecooldoo.replit.app/test.sh
- Trying 34.117.33.233:443…
- Connected to joecooldoo.replit.app (34.117.33.233) port 443 (#0)
- ALPN: offers h2,http/1.1
- (304) (OUT), TLS handshake, Client hello (1):
- CAfile: /etc/ssl/cert.pem
- CApath: none
- (304) (IN), TLS handshake, Server hello (2):
- (304) (IN), TLS handshake, Unknown (8):
- (304) (IN), TLS handshake, Certificate (11):
- (304) (IN), TLS handshake, CERT verify (15):
- (304) (IN), TLS handshake, Finished (20):
- (304) (OUT), TLS handshake, Finished (20):
- SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
- ALPN: server accepted h2
- Server certificate:
- subject: CN=replit.app
- start date: Oct 23 08:05:37 2023 GMT
- expire date: Jan 21 09:01:32 2024 GMT
- subjectAltName: host "joecooldoo.replit.app" matched cert's "*.replit.app"
- issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1D4
- SSL certificate verify ok.
- using HTTP/2
- h2 [:method: GET]
- h2 [:scheme: https]
- h2 [:authority: joecooldoo.replit.app]
- h2 [:path: /test.sh]
- h2 [user-agent: curl/8.1.2]
- h2 [accept: _/_]
- Using Stream ID: 1 (easy handle 0x13e814200)
> GET /test.sh HTTP/2
> Host: joecooldoo.replit.app
> User-Agent: curl/8.1.2
> Accept: _/_
>
> < HTTP/2 200
> < content-length: 16
> < content-type:
> < strict-transport-security: max-age=63072000; includeSubDomains
> < date: Mon, 30 Oct 2023 15:29:55 GMT
> < via: 1.1 google
> < alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
1 Like
can you curl to it
yes I can!
In fact, the page loads unexpectedly fast.