Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Despite the repo name, www.ziglang.org times out (works without www.) #34

Open
ghost opened this issue Apr 9, 2019 · 4 comments
Open

Comments

@ghost
Copy link

ghost commented Apr 9, 2019

https://www.ziglang.org/ 😯

@hspak
Copy link
Sponsor

hspak commented Jun 30, 2019

It looks like http://www.ziglang.org redirects fine, but https://www.ziglang.org doesn't.

@gunnarahlberg
Copy link

gunnarahlberg commented Oct 1, 2019

Seems like this is the recomendation
https://support.cloudflare.com/hc/en-us/articles/115003011431#522error

Error 522: connection timed out

Error 522 occurs when Cloudflare times out contacting the origin web server. Two different timeouts cause HTTP error 522 depending on when they occur between Cloudflare and the origin web server:

Before a connection is established, the origin web server does not return a SYN+ACK to Cloudflare within 15 seconds of Cloudflare sending a SYN.
After a connection is established, the origin web server doesn’t acknowledge (ACK) Cloudflare’s resource request within 90 seconds.

An HTTP 524 error occurs if the origin web server acknowledges (ACK) the resource request after the connection is established, but does not send a timely response.

Resolution

Contact your hosting provider to check the following common causes at your origin web server:

(Most common cause) Cloudflare IP addresses are rate limited or blocked in .htaccess, iptables, or firewalls. Confirm your hosting provider whitelists Cloudflare IP addresses.
An overloaded or offline origin web server drops incoming requests.
Keepalives are disabled at the origin web server.
The origin IP address in your Cloudflare DNS app does not match the IP address currently provisioned to your origin web server by your hosting provider.
Packets were dropped at your origin web server.

If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before contacting Cloudflare support:

An MTR or traceroute from your origin web server to a Cloudflare IP address that most commonly connected to your origin web server before the issue occurred. Identify a connecting Cloudflare IP recorded in the origin web server logs.
Details from the hosting provider’s investigation such as pertinent logs or conversations with the hosting provider.

@bsljth
Copy link

bsljth commented Aug 13, 2022

Can't this be fixed from within the server hosting the Zig website? If we are using something like Nginx, www can be added in as a sub-domain to the conf file, right?

@kristoff-it
Copy link
Member

@andrewrk do you want to have www.ziglang.org work? It currently fails to resolve at the DNS level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants