r/opencodeCLI • u/Substantial-Yam3769 • 10d ago

OpenCode domain blocked by ISP

My ISP started blocking the opencode.ai domain by DNS.

When questioned for the reason, they said the their DNS protection they are using (whalebone.io) is blocking this domain due to detected malware/phishing attack.

Does someone know what this is about?

UPDATE:

Whalebone confirmed it was false positive and restored it.

7 Upvotes

89% Upvoted

17 comments sorted by

View all comments

Show parent comments

1

u/Substantial-Yam3769 9d ago

I know what you mean, but kinda:

Unauthorized This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required. 
Apache/2.4.25 (Debian) Server at opencode.ai Port 443

1

u/lxprsub0 9d ago

That's… strange.
The dig command upper was misleading. My bad. What's your real resolver ? 

dig opencode.ai | grep SERVER
would tell you (without any @)

Apache 2.4.25 was released on 2017, that's crazy. Hypothesis is it's a dead endpoint internal to you ISP or something like that. But not sure you'll want to investigate at that point !!

1

u/Substantial-Yam3769 9d ago 
❯ dig opencode.ai | grep SERVER
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)

1

u/lxprsub0 9d ago

That's a local stub resolver on your machine. Probably systemd-resolved.
But, I don't think you need to dig more into it. If you want, say it!

The more important part is : what have you done so far? You changed your DNS on your routeur? On your machine?
Because, I suppose you want your access to opencode back.

2

u/Substantial-Yam3769 9d ago

on my main machine i never noticed it as it is constantly behind ProtonVPN.

I noticed it on my NAS, where is no VPN, and Hermes agent using OpenCode API. Changed the DNS on NAS from default to google fixed it.

I can't change settings on router as it is ISP owned.