www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Firefox can't establish a connection to the server at

reply kdevel <kdevel vogtner.de> writes:
$ host issues.dlang.org
Host issues.dlang.org not found: 3(NXDOMAIN)

BTW: Why is the domain hostet at cloudflare?

$ host -t ns dlang.org
dlang.org name server brian.ns.cloudflare.com.
dlang.org name server kiki.ns.cloudflare.com.

and why is the forum TLS operated by cloudflare?

$ host forum.dlang.org
forum.dlang.org has address 104.21.37.229
forum.dlang.org has address 172.67.214.172
[...]

$ jwhois  104.21.37.229
NetRange:       104.16.0.0 - 104.31.255.255
CIDR:           104.16.0.0/12
NetName:        CLOUDFLARENET

$ jwhois
NetRange:       172.64.0.0 - 172.71.255.255
CIDR:           172.64.0.0/13
NetName:        CLOUDFLARENET

Are you aware that cloudflare has access to the plaintext of the 
whole communication?
Aug 18 2022
next sibling parent reply bauss <jacobbauss gmail.com> writes:
On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)

 BTW: Why is the domain hostet at cloudflare?

 $ host -t ns dlang.org
 dlang.org name server brian.ns.cloudflare.com.
 dlang.org name server kiki.ns.cloudflare.com.

 and why is the forum TLS operated by cloudflare?

 $ host forum.dlang.org
 forum.dlang.org has address 104.21.37.229
 forum.dlang.org has address 172.67.214.172
 [...]

 $ jwhois  104.21.37.229
 NetRange:       104.16.0.0 - 104.31.255.255
 CIDR:           104.16.0.0/12
 NetName:        CLOUDFLARENET

 $ jwhois
 NetRange:       172.64.0.0 - 172.71.255.255
 CIDR:           172.64.0.0/13
 NetName:        CLOUDFLARENET

 Are you aware that cloudflare has access to the plaintext of 
 the whole communication?
Does it really matter here? Nothing is really confidential.
Aug 18 2022
parent kdevel <kdevel vogtner.de> writes:
On Thursday, 18 August 2022 at 14:26:16 UTC, bauss wrote:
[...]
 Does it really matter here?
As cloudflare is virtually everywhere: Yes it matters here, too.
 Nothing is really confidential.
Who decides that? Of course my password for this forum is confidential. CF is a man in the middle. Surprisingly GDPR issues of A records pointing to CF have AFAICS not yet been discussed. If website operators get sued for embedding google fonts the wrong way [1] how can directing a visitor to CF via the A record be in conformance with the GDPR? [1] https://www.google.de/search?q=embedding+google+fonts+gdpr
Aug 18 2022
prev sibling next sibling parent Iain Buclaw <ibuclaw gdcproject.org> writes:
On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)
This has been fixed and will come back online (along with tour) within the hour after the record has been propagated to all NS servers.
Aug 18 2022
prev sibling parent reply Mike Parker <aldacron gmail.com> writes:
On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)
Should work for you now.
 BTW: Why is the domain hostet at cloudflare?
This is part of our initiative to move all D ecosystem services under foundation control. A few hours ago we put dlang.org behind CloudFlare. Looks like there was a bit of a configuration issue in that a couple of subdomains didn't get picked up automatically in the DNS records by CloudFlare. I've just updated the issues record. Should have tour.dlang.org operating once I (or someone else) has the info for the record.
Aug 18 2022
next sibling parent reply Ruby The Roobster <rubytheroobster yandex.com> writes:
On Thursday, 18 August 2022 at 14:45:18 UTC, Mike Parker wrote:
 On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)
Should work for you now.
 BTW: Why is the domain hostet at cloudflare?
This is part of our initiative to move all D ecosystem services under foundation control. A few hours ago we put dlang.org behind CloudFlare. Looks like there was a bit of a configuration issue in that a couple of subdomains didn't get picked up automatically in the DNS records by CloudFlare. I've just updated the issues record. Should have tour.dlang.org operating once I (or someone else) has the info for the record.
run.dlang.io is also down, though issues.dlang.org is now back up. Trying to access run.dlang.io results in this error: ``` Secure Connection Failed An error occurred during a connection to run.dlang.io. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. ``` While trying to ping the site gives a "host not found" error.
Aug 18 2022
parent reply Mike Parker <aldacron gmail.com> writes:
On Thursday, 18 August 2022 at 15:41:29 UTC, Ruby The Roobster 
wrote:

 run.dlang.io is also down, though issues.dlang.org is now back 
 up.

 Trying to access run.dlang.io results in this error:

 ```
 Secure Connection Failed

 An error occurred during a connection to run.dlang.io. Cannot 
 communicate securely with peer: no common encryption 
 algorithm(s).

 Error code: SSL_ERROR_NO_CYPHER_OVERLAP

     The page you are trying to view cannot be shown because the 
 authenticity of the received data could not be verified.
     Please contact the website owners to inform them of this 
 problem.
 ```

 While trying to ping the site gives a "host not found" error.
I don't know what that's about. I didn't migrate dlang.io to CloudFlare yet. And it was working just a little while ago.
Aug 18 2022
parent reply Ruby The Roobster <rubytheroobster yandex.com> writes:
On Thursday, 18 August 2022 at 15:43:02 UTC, Mike Parker wrote:
 On Thursday, 18 August 2022 at 15:41:29 UTC, Ruby The Roobster 
 wrote:

 [SNIP]
I don't know what that's about. I didn't migrate dlang.io to CloudFlare yet. And it was working just a little while ago.
Now there is a "run.dlang.org", but instead of pointing to the online editor, it is a copy of the tour. Is this intended?
Aug 18 2022
next sibling parent Mike Parker <aldacron gmail.com> writes:
On Friday, 19 August 2022 at 01:01:43 UTC, Ruby The Roobster 
wrote:

 Now there is a "run.dlang.org", but instead of pointing to the 
 online editor, it is a copy of the tour.  Is this intended?
No. It'll be sorted soon. run.dlang.io is working again, though.
Aug 18 2022
prev sibling parent reply Mike Parker <aldacron gmail.com> writes:
On Friday, 19 August 2022 at 01:01:43 UTC, Ruby The Roobster 
wrote:

 Now there is a "run.dlang.org", but instead of pointing to the 
 online editor, it is a copy of the tour.  Is this intended?
It should work once the DNS changes propagate.
Aug 18 2022
parent reply Max Samukha <maxsamukha gmail.com> writes:
On Friday, 19 August 2022 at 01:27:07 UTC, Mike Parker wrote:

 It should work once the DNS changes propagate.
The 'Shorten' button still doesn't work. Requests to 'https://run.dlang.io/api/v1/shorten' fail with "object.Exception ../../../.dub/packages/vibe-core-1.8.1/vibe-core/source/ ibe/core/net.d(71): Failed to lookup host 'is.gd'."
Aug 18 2022
parent Mike Parker <aldacron gmail.com> writes:
On Friday, 19 August 2022 at 04:20:10 UTC, Max Samukha wrote:
 The 'Shorten' button still doesn't work. Requests to 
 'https://run.dlang.io/api/v1/shorten' fail with 
 "object.Exception ../../../.dub/packages/vibe-core-1.8.1/vibe-core/source/
ibe/core/net.d(71): Failed to lookup host 'is.gd'."
Yes, that's something the maintainers have to deal with. I believe there's a plan to do a bit of rearchitecting when we get ready to move everything over to the foundation's servers.
Aug 18 2022
prev sibling next sibling parent Mike Parker <aldacron gmail.com> writes:
On Thursday, 18 August 2022 at 14:45:18 UTC, Mike Parker wrote:
 On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)
Should work for you now.
 BTW: Why is the domain hostet at cloudflare?
This is part of our initiative to move all D ecosystem services under foundation control. A few hours ago we put dlang.org behind CloudFlare. Looks like there was a bit of a configuration issue in that a couple of subdomains didn't get picked up automatically in the DNS records by CloudFlare. I've just updated the issues record. Should have tour.dlang.org operating once I (or someone else) has the info for the record.
tour.dlang.org should work now once the DNS change propagates. And I should have thought of this earlier: tour.dlang.io is the host URL.
Aug 18 2022
prev sibling parent reply Bastiaan Veelo <Bastiaan Veelo.net> writes:
On Thursday, 18 August 2022 at 14:45:18 UTC, Mike Parker wrote:
 On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)
Should work for you now.
I know this is WIP, but in case this comes as a surprise: issues.dlang.org just shows the apache test page at the moment. It would be nice that when parts of the infrastructure are taken offline for maintenance, that there is an announcement for how long the downtime is expected to be on the main entry ways (like https://dlang.org/bugstats.html in this case) or the announce forum. -- Bastiaan.
Aug 19 2022
parent Mike Parker <aldacron gmail.com> writes:
On Friday, 19 August 2022 at 14:18:37 UTC, Bastiaan Veelo wrote:
 On Thursday, 18 August 2022 at 14:45:18 UTC, Mike Parker wrote:
 On Thursday, 18 August 2022 at 14:15:43 UTC, kdevel wrote:
 $ host issues.dlang.org
 Host issues.dlang.org not found: 3(NXDOMAIN)
Should work for you now.
I know this is WIP, but in case this comes as a surprise: issues.dlang.org just shows the apache test page at the moment. It would be nice that when parts of the infrastructure are taken offline for maintenance, that there is an announcement for how long the downtime is expected to be on the main entry ways (like https://dlang.org/bugstats.html in this case) or the announce forum. -- Bastiaan.
It wasn’t taken offline. It was working when I went to bed last night and then stopped at some point after. We’ve been trying to get it up again but hit a wall. I don’t know when we’ll get there. But anyway, point taken. Next time I’m aware something has gone down I’ll make an announcement.
Aug 19 2022