tomekowal
Oban Pro website down
Hey, it seems that the Oban Pro website is down: https://oban.pro/
We are using:
mix hex.repo add oban https://getoban.pro/repo \
--fetch-public-key SHA256:4/OSKi0NRF91QVVXlGAhb/BIMLnK8NHcx/EWs+aIWPc \
--auth-key $OBAN_LICENSE_KEY
to get it, so it kills our CI.
Anyone knows what could be the problem?
Marked As Solved
zaljir
Also Liked
sorentwo
This is indeed because of the worldwide cloudflare outage. Our servers are up, but we can’t switch the DNS over because the Cloudflare dashboard isn’t operational ![]()
jamesvl
In case this helps, this was posted on HN:
If anyone needs commands for turning off the CF proxy for their domains and happens to have a Cloudflare API token.
First you can grab the zone ID via:
curl -X GET "https://api.cloudflare.com/client/v4/zones" -H "Authorization: Bearer $API_TOKEN" -H "Content-Type: application/json" | jq -r '.result[] | "\(.id) \(.name)"'
And a list of DNS records using:
curl -X GET "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records" -H "Authorization: Bearer $API_TOKEN" -H "Content-Type: application/json"
Each DNS record will have an ID associated. Finally patch the relevant records:
curl -X PATCH "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records/$RECORD_ID" -H "Authorization: Bearer $API_TOKEN" -H "Content-Type: application/json" --data '{"proxied":false}'
Copying from a sibling comment - some warnings:
- SSL/TLS: You will likely lose your Cloudflare-provided SSL certificate. Your site will only work if your origin server has its own valid certificate.
- Security & Performance: You will lose the performance benefits (caching, minification, global edge network) and security protections (DDoS mitigation, WAF) that Cloudflare provides.
- This will also reveal your backend internal IP addresses. Anyone can find permanent logs of public IP addresses used by even obscure domain names, so potential adversaries don’t necessarily have to be paying attention at the exact right time to find it.
sorenone
Hi @barkerja,
Thanks for the ping!
Yes, this was a DNSSEC issue caused by our registrar automatically rotating keys. We are unable to disable this during the rotation, and out provider didn’t respond to our request. (Probably due to the holiday/weekend combo).
We are tightening up our DNS to prevent any future issues during rotations. We have kicked off the process and anticipate this being completed in the next week. Essentially, once it’s unlocked.
We apologize for any inconvenience this has caused!!
Last Post!
sorenone
Hi @barkerja,
Thanks for the ping!
Yes, this was a DNSSEC issue caused by our registrar automatically rotating keys. We are unable to disable this during the rotation, and out provider didn’t respond to our request. (Probably due to the holiday/weekend combo).
We are tightening up our DNS to prevent any future issues during rotations. We have kicked off the process and anticipate this being completed in the next week. Essentially, once it’s unlocked.
We apologize for any inconvenience this has caused!!
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security









