Bug 29612

Summary:	Connection refused on mageia.org and blog.mageia.org
Product:	Websites	Reporter:	Nicolas Peifer <nic>
Component:	All	Assignee:	Sysadmin Team <sysadmin-bugs>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins
Version:	trunk
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Nicolas Peifer 2021-11-01 11:59:42 CET

Description of problem:
Since October 28th I cannot access mageia.org (www.mageia.org works) or blog.mageia.org as I was used to.

How reproducible:
1. With your browser: Clean your history and try to access 'mageia.org' or 'blog.mageia.org' or

2. with curl:
$ curl http://mageia.org
curl: (7) Failed to connect to mageia.org port 80: Connection refused

$ curl https://mageia.org
curl: (7) Failed to connect to mageia.org port 443: Connection refused

$ curl https://blog.mageia.org/en/
curl: (7) Failed to connect to blog.mageia.org port 443: Connection refused

Comment 1 David Walser 2021-11-01 14:40:23 CET

binrepo.mageia.org gives error 503 as well.

Assignee: atelier-bugs => sysadmin-bugs

Comment 2 Thomas Backlund 2021-11-01 16:20:19 CET

no such issues here

Severity: major => normal

Comment 3 Dave Hodgins 2021-11-01 19:00:11 CET

Ok here too.
$ curl http://mageia.org
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://www.mageia.org/">here</a>.</p>
$ traceroute -I mageia.org|grep -v '* * *'
traceroute to mageia.org (163.172.148.228), 30 hops max, 60 byte packets
 1  router (192.168.10.11)  0.243 ms  0.366 ms  0.499 ms
 2  135-23-236-129.cpe.pppoe.ca (135.23.236.129)  9.766 ms  9.789 ms  9.808 ms
 3  london.rcable-tsi.tor.teksavvy.com (104.195.128.74)  12.078 ms  12.100 ms  12.104 ms
 4  london.tsi-rcable.tor.teksavvy.com (104.195.128.73)  12.948 ms  12.972 ms  12.993 ms
 5  ae2-0-bdr01-tor2.teksavvy.com (206.248.155.17)  15.750 ms  15.759 ms  15.797 ms
 6  ae12-0-bdr01-tor.teksavvy.com (206.248.155.10)  21.148 ms  20.724 ms  20.736 ms
 7  et-4-3-0.mpr1.tor2.ca.zip.zayo.com.zip.zayo.com (128.177.110.222)  12.243 ms  11.712 ms  11.719 ms
 8  ae6.mpr1.yyz1.ca.zip.zayo.com (64.125.23.121)  12.242 ms  13.138 ms  13.152 ms
11  ae2.cs1.cdg12.fr.eth.zayo.com (64.125.29.24)  94.348 ms  94.395 ms  94.481 ms
12  ae0.cs1.cdg11.fr.eth.zayo.com (64.125.29.85)  94.337 ms  94.333 ms  94.380 ms
13  ae1.mcs1.cdg11.fr.eth.zayo.com (64.125.29.95)  100.227 ms  100.223 ms  91.944 ms
15  49-infra-dc2-a9k2.dc3.poneytelecom.eu (195.154.1.119)  96.293 ms  96.413 ms  96.433 ms
20  neru.mageia.org (163.172.148.228)  96.038 ms  94.343 ms  96.112 ms

CC: (none) => davidwhodgins

Comment 4 Nicolas Peifer 2021-11-01 19:23:50 CET

Now, it's working here again, too. But it wasn't working this noon for sure (I double checked it on my local machine and on a remote server so as to exclude possible ISP issues).

Comment 5 katnatek 2021-11-01 23:33:51 CET

In this moment planet.mageia.org /en and /es don't works

Comment 6 Thomas Backlund 2021-11-02 14:02:28 CET

yeah, the planet code probably needs updating/rewriting for php8