Http://docs.opennebula.io/ link cannot be accessed

docs.opennebula.io website maintenance staff Hello. I don’t know if you can see this post. If you know the maintenance staff of this website, please inform them. This website, in China, has some network operators network types and is not available. This is not conducive to opennebula’s promotion in the Chinese market, which is a large market.

Hello @chengyk,

Apologies for the inconvenience, and the delay on the reply, but it looks like it was a temporary issue. From our side everything works normal, and we’ve double checked if there’s an issue with the URL, or if there’s any restriction from the authorities, but that’s not the case.

Please check again, and let us know if the problem persists.

Regards,

@FrancJP I am very glad to see your reply. I ran the test again.
The three major network providers in China are China Telecom, China Unicom and China Mobile.
China Telecom network: docs.opennebula.io unavailable. opennebula.io and forum.opennebula.io are accessible.
China Mobile network: docs.opennebula.io unavailable(or occasionally accessible). opennebula.io and forum.opennebula.io are accessible. China Unicom network, not tested.

Hello @chengyk,

I’ve personally tested on a VPN simulating China Mainland (although it’s not 100% confident), and double checked using this site: Blocked in China | Easily tell if a website is blocked in China

On both cases I could access all the OpenNebula sites. So I assume it might be some random blocking from the ISP. As you can imagine, if the ISP is blocking one IP, and not the others, we cannot do much from our side.

In any case, have you tried using the whole path?: OpenNebula 6.8 Documentation — OpenNebula 6.8.3 documentation
Instead of only docs.opennebula

Cheers,

@FrancJP Thank you very much. OpenNebula 6.8 Documentation — OpenNebula 6.8.3 documentation will not be able to access. All other opennebula.io domains are working correctly. It is possible that the IP mapped by docs.opennebula.io is blocked. We’ve seen cases like this before. It was fixed after the IP was changed.