Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
None
-
None
Description
I think it’s simultan to MDEV-34342 where some ip-ranges was blocked. Since today I got this error from my strato-servers again. If I try to load the url from my home-network, there is no error.
Err:17 http://downloads.mariadb.com/Tools/ubuntu jammy Release
|
404 Not Found [IP: 2606:4700::6811:bf0e 443]
|
Err:2 https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/ubuntu jammy InRelease
|
Could not handshake: Decryption has failed. [IP: 104.18.135.24 443]
|
Err:4 https://dlm.mariadb.com/repo/maxscale/latest/apt jammy InRelease
|
Could not handshake: Decryption has failed. [IP: 104.18.135.24 443]
|
Reading package lists... Done
|
E: The repository 'http://downloads.mariadb.com/Tools/ubuntu jammy Release' no longer has a Release file.
|
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
|
N: See apt-secure(8) manpage for repository creation and user configuration details.
|
Can someone take a look if the IPs from this posts https://jira.mariadb.org/browse/MDEV-34342?focusedCommentId=286171&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-286171 are blocked again?
Thanks, Alex
Attachments
Activity
I've verified we are not blocking these IPs. App logs and our account logs in cloudflare are showing only successful connections, which means the errors are happening on the global cloudflare level before the request gets to our account.
Is this still happening? If so I will open a ticket with cloudflare support.
Hi @Bryan, it’s seams to work fine again. Perhaps there was a Cloudflare issue global as you expected. Thanks for verifying it.
Glad to hear that, although these transient errors are very frustrating. I will close this out but let us know if you run into anything else in the future.
New observation: I think because of the blocking other services where hosted by cloudflare are affected too like heartbeat.uptimerobot.com - the Heartbeat test seams to break (can't connect in the same time when apt-update false) on the same host.
The error is the same - SSL is not valid on both URLs the mariadb-repo and the on cloudflare hosted uptimerobot.