Private versions are not accessible even by admins

[nadiaya]

Details

Private documentation version is not accessible even by admins: 'Permission Denied' returned to everyone.

• Read the Docs project URL: https://readthedocs.org/projects/sagemaker/
• Build URL (if applicable): N/A
• Read the Docs username (if applicable): awsml

Expected Result

After making 'latest' version to be private, according to https://docs.readthedocs.io/en/latest/privacy.html#private, we should be able to view the documentation for this version when logged in an admin account for this project.

Actual Result

When going to https://sagemaker.readthedocs.io/en/latest/ getting 'Permission Denied' even when logged in an admin account.

[stsewd]

Are you still having this problem? Also, I only see one maintainer in the project (awsml).

And we are about to remove/deprecate the privacy levels #2663

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. Thanks!

[taradinoc]

@stsewd I'm experiencing this too.

https://mdl-language.readthedocs.io/en/latest/ - Public. No problems.

https://mdl-language.readthedocs.io/en/sphinx/ - Private. It has built successfully, but I can't view it even though I'm logged in as the only project maintainer.

[daianagan]

@taradinoc or anyone was able to solve this? I am still gettig the same error...

[dojutsu-user]

@stsewd Seems like this is still valid. I am reopening the issue.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. Thanks!

[taradinoc]

@stsewd This is still reproducible using the links in my last comment. https://mdl-language.readthedocs.io/en/sphinx/ gives me a "Permission Denied" error even though I'm logged in as the admin.

[kmaehashi]

Same case here. https://docs.chainer.org/en/v6/ (v6 branch is set to Private) cannot be browsed even when I logged in as a maintainer account.

[stsewd]

Hi all, we are planning to remove the privacy levels from the community site, since all projects hosted in readthedocs.org are public open source projects. If you are relying on this feature to host private versions, you should use readthedocs.com instead.

With that said, I don't think this bug isn't going to be fixed soon (the core team is going to put more effort into removing the privacy levels)

Ref #2663 #3781

If you are using private versions with public open source projects, we would love to hear your use cases.

[daianagan]

Dear @stsewd,
Thanks for your reply. I didn't know that readthedocs.org was exclusively for open source projects, I thought readthedocs is an OS project itself but not that it was made for OS only also.
In my case I work as a Bioinformatician in a public hospital in Argentina and regularly I document patient's info which of course cannot be public. Another example are hospital's SOPs which cannot be made available for everyone. I found readthedocs & sphinx to be a very friendly way to show the documentation, but it won't be possible in my case if it has to be either public or paid (and regretfully I have no resources to pay for documentation). Or do you plan to have an option for non-profitable organizations? :)
I think I'll use Sphinx and local files for now
Thank you for your help!!
Best regards,
Daiana

[stsewd]

@daianagan we do offer a discount for non-profitable organizations, and if that isn't enough or you have more questions, please write us to [email protected]

[kmaehashi]

@stsewd Thank you for your reply! Let me explain our use-case.

We are currently developing in 2 branches; docs of master / v6 branches are built as latest / v6 version on RTD respectively. Our open-source project requires a bit complicated setup (building Python C++ extension modules that use CUDA), so we'd like to make sure that every commit of master / v6 branches can be built successfully on RTD to avoid tagging a commit which cannot render docs correctly. Actually we once experienced that issue; of course, we're testing every commit by running sphinx-build on our own CI, but it is difficult to correctly reproduce the RTD build container environment.

To avoid confusion to users (because v6 sounds like a docs of the latest released version of v6.x series, but actually it is a docs of HEAD of v6 branch), we had been using Protected settings to v6 branch, but unfortunately it was removed in #5833, so we considered migrating to Private, and found this issue.

I also think it's useful to have a Private mode as a "staging" feature so that we can try changing configuration in readthedocs.yml and see how it works in a separate branch. (So, actually what we need is the environment that can reproduce RTD results locally, not privacy levels.)

I understand that readthedocs.org is for public open source projects and thank you for providing a great service!

[stsewd]

@kmaehashi would having build docs from a PR to preview the changes help with your use case? #1340

Also, we are going to have a replacement for protected, something like hide version, so those wouldn't be listed.

[kmaehashi]

@stsewd

would having build docs from a PR to preview the changes help with your use case? #1340

Yes, that feature would be very useful for us.

Also, we are going to have a replacement for protected, something like hide version, so those wouldn't be listed.

Thank you, looking forward to see that feature!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[saadmk11]

Hi, @kmaehashi. We have The PR Builder Feature in BETA now. You can learn more about it in this blog post: https://blog.readthedocs.com/building-docs-for-pull-requests/

[kmaehashi]

@saadmk11 Thanks for letting me know! I'll look into it.

[bsipocz]

Also, we are going to have a replacement for protected, something like hide version, so those wouldn't be listed.

do you have an ETA for this? We routinely used the "Protected" feature to hide our older versions, while keeping the direct lint to it alive. IMO the confusion could have been cleaned up with documentation rather than punishing with removal for those who it as intended.

[stsewd]

We don't have a specific date, but it's on our roadmap #6194

[Borda]

the same problem also for https://torch-lightning.readthedocs.io/en/docs
from Lightning-AI/pytorch-lightning#465 (comment)

[humitos]

I think we can close this issue. We are not going to support PRIVATE versions on readthedocs.org --although, they will be fully supported on readthedocs.com

[Borda]

So pls disable such option.

[humitos]

@Borda we are working on that. Thanks,

[zilinc]

I'm new to rtd. My use case is that I use private versions for debugging my docs (or as a preview as I fix things). Is there an alternative to it? Thanks in advance.

[humitos]

@zilinc Hi! As mentioned in this issue, we are removing the support for private versions. In case you want to have "preview" of what a version will look like, you can ask to enable PR builder in your project. See https://blog.readthedocs.com/building-docs-for-pull-requests/