TrueNAS 25.04.2.3 Is Now Available!

Hi WiteWulf,

I have same issue here on two servers now and again. I had this before once back in time, and at that time it was my ISP that blocked the access. I called them and they fixed it.
So just to confirm again, they need to make sure that my servers can reach
(http://storjshare.io/), can you confirm that…??.

BR

@elvisimprsntr can you confirm/deny this is the issue for your systems?

Yes, your ISP needs to allow access to the storjshare.io decentralised storage network.

Doing a quick search online suggests that storjshare is quite regularly blocked for hosting malware and copyright infringing materials, among other things.

@Captain_Morgan

When I check Quad9 it shows storjshare.io is not blocked, but when when I perform a DNS lookup it will not resolve, even with Google DNS added.

If storjshare.io is routinely blocked or will not resolve, seems iXsystems needs to move to another provider. Just my 2¢

1 Like

We’ll get it fixed.

Can you confirm where you are based and what ISP?

1 Like

Location: West Palm Beach, FL
ISP: ATT Fiber

link.storjshare.io is now resolving and not blocked by Quad9

1 Like

Official response from Quad9. Since storj.io seems to be an open cesspool, still seems like iXsystems needs to move to another provider.

Hello,

Please accept our apologies for the delayed response/action.

Earlier this year, we informed Storj.io that all that was needed for Quad9 to set a permanent exclusion for this FQDN was to add a “Report Abuse” link to the footer of their website, which is a common practice for CDNs, and would only serve to help Storj.io by encouraging netizens to report any malicious files to them directly, as opposed to reporting them to threat lists.

Quad9 initially tried getting this removed as a false positive with one of our threat intelligence partners, but this kept filtering down from various upstream threat feeds [0], and it became a game of whack-a-mole. We had no idea this was going to be a multi-week episode.

We’ve added a permanent exclusion for link.storjshare.io, despite Storj.io not complying with our requirement.

We apologize for any inconvenience caused.