Permission denied after successful build - read-the-docs

I am trying to import my first project into Read the Docs (readthedocs.io). After much fidgeting with the git hooks, I am now able to import and successfully build my mkdocs repo.
But as soon as I click on "View Docs", I have the following error on the page:
Permission Denied
You don't have the proper permissions to view this page. Please contact the owner of this project to request permission.
I cannot find any reason why that could happen (i'm logged in with my owner credentials).

I had the same problem. I tried setting the "latest version" to public instead of private, and now I can view my doc. I don't know why I couldn't view it as the owner of the project before... Nevermind. Hope that helps.
Best,
Kristina

Related

Page not found with POST request in the django's admin when i click any of the save button in Production environment

At first, I tried installing MySQLclient via the terminal in a shared hosting platform only to get GCC permission denied, I contacted the admin pertaining the domain but to no assistance. I decided to use SQLite instead, everything worked fine, to my surprise no migrations were requested. Now when I wanted to add a product in the django admin page, when I click the save button I get an error that page not found with request Post. Everything works fine in development also when i request the same page while online in the admins page it loads fine. Kindly help
Here is the gcc permission denied
Got this error when i tried pip install mysqlclient in cpanel terminal
Here is the the product page at the admin
This is the product page while at the admin page
Here is the error when i click any of the save buttons
This the error i get when i try to save the product by clicking any of the save buttons
I escaped gcc permission denied by installing django 2.1 and followed this Error loading MySQLdb Module 'Did you install mysqlclient or MySQL-python?' worked for me but now the problem is when i add a product with an imagefield i get page not found with request post

Clasp Could not read API credentials. Are you logged in globally?

I'm logging in with clasp login --creds <file> which produces a local .clasprc.json file.
It says that I am logged in, but when I run another command I get:
Could not read API credentials. Are you logged in globally?
Any thoughts on why its not looking at my local clasprc file first?
Currently using version clasp v. 2.2.0
I ran into the same problem on Windows 10 and found that you need to login both globally and locally to use clasp run. There should be a .clasprc.json file in both your project folder and user folder.
I think I have finally found the solution for the same problem
Follow along with the comments from this github issue
Add the "oauthScopes" field to your local code and push it to your app
If you can't push, then copy-paste it to manifest file in the browser
Then you have to publish the app, and there were few things I've done, not sure which one helped. In the app in browser:
add the app version in File->Manage Versions
Publish -> Deploy as API executable
try to login with clasp and creds.json file
try to run something clasp run testRun
it may show the error that you're missing some oauth permissions, but it will list which ones, and you can add them
In my case, one weird thing that also helped was to enable some Google API
so in the app in browser: Resources -> Advanced Google Services -> enable some API
then try to do clasp run
if it works, you can disable the API that you have enabled previously.
Hope that helps

upload fail the google api after redirecting to localhost

After I run the following code from:
https://developers.google.com/drive/api/v3/quickstart/python
I get the link:
https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=792377765624-8l03cnfmj1km5gd27227kuaem37okdip.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A41245%2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive.metadata.readonly&state=8xHuMrgWMisZa7Hww6HpIZrRdkRTjq&access_type=offline
I click it and get new pages.
I was not allowed to upload pictures here,sorry.
Because my score is low in stackoverflow
Finally, it tell me I can not connect to:
http://localhost:44637
Screenshots of the behaviour: https://blog.csdn.net/appleyuchi/article/details/102940981
According to the screenshots you provided and the url you are getting redirected to, the problem is that the Google account with which you downloaded the credentials file is not the same as the one with which you grant authorization to Drive. Both should be the same, because the credentials file contains information that identifies the account that downloaded them.
Check these for further information on the authentication process:
https://developers.google.com/identity/protocols/OAuth2
https://developers.google.com/identity/protocols/OAuth2WebServer

Sharing a script to everyone with link raises an Internal error

I'm trying to share a script via Library.
I publish a library using "Manage versions", but when I navigate to "File" > "Share", and trying to gain read access to "Anyone who has the link", I got an "Sorry, an internal error has occurred and your request was not completed." while saving.
Any way to fix this?
P.S. I try to do it in 2 accounts.
Answer:
Permissions for a script that is bound to a Drive file must be the same as the permissions of the file to which it is bound. Make sure that the permissions are set on the file first, and then you can get the share link for the script using the same permission settings for sharing.

Reauthenticate or Remove authentication Pydrive during runtime in Google Colab

I want to reauthenticate my Google Drive Credentials so that I can login from a different Google account and access it using pydrive. How can I do that?
I am using the following code to authenticate:
auth.authenticate_user()
gauth = GoogleAuth()
gauth.credentials = GoogleCredentials.get_application_default()
drive = GoogleDrive(auth = gauth)
I want to get a fresh token and option to login again into a different google account?
Thanks for helping!
Try deleting the credential file produced by auth.authenticate_user() based on the auth module
rm /content/adc.json
I have just found a solution to this issue. If one goes to his/hers Google Account Settings->Security->Signing in to other sites(all the way down)->YOUR PROCESS NAME and then simply remove it. If you try simply listing the files in the authenticated drive again it should fail with "Token has been expired or revoked."
Just make sure when you create and enter your correct account credentials to delete the credentials/client_secret.json file as the settings.yaml does not seem to overwrite
To reset credentials just remove the gdrive config folder with a shell command from a code block
rm ~/.config/Google/DriveFS/ -rf
I ran into a similar problem where I clicked on the wrong account for Google Drive authentication. None of the files I needed to access were available, and I couldn't figure out a way to revoke a token by the comments above. I tried both restarting the runtime and changing from GPU to TPU. When I tried the latter, it worked and the authorization prompt returned. However, I'm not sure if it worked or just reached the token refresh time.
I factory reset my runtime and was able to get it to accept a different credential.
Runtime -> factory reset runtime