Not Able to add SEARCH_CONSOLE_PRIVATE_KEY to Docker or Fly #75
-
SEARCH_CONSOLE_PRIVATE_KEY=-----BEGIN PRIVATE KEY-----\nMIIEvgIBADANBgkqhkiG9w0BA\nvnwq7Zd3diJpxE46aRQwlJ9LRNitjt2/OUcXkc7AIy7xasAl8c0jADttPpW26Slk\nd/VCCxH7JssXsV8dHvn1Xc3r\n-----END PRIVATE KEY-----\n Error Im getting : Error could not parse secrets: ‘PRIVATE’: must be in the format NAME=VALUE basically, its saying that I cannot have ----- added as variable. how do I pass the value to docker? should I use " " ? |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 16 replies
-
Yes, You can try that. |
Beta Was this translation helpful? Give feedback.
-
Added " " for both email and private key but keywords not loading. Not for discover nor the insight. Discover says loading keywords and then says "Could Not fetch Keyword Data for this Domain from Google Search Console." Insight tab remains same. Please check screenshots. |
Beta Was this translation helpful? Give feedback.
-
just checked the Google Cloud Console: under service accounts - > metrics - https://prnt.sc/bCgtamly6Alz so the request are being sent but are hitting errors and not data is sent. why is this happening? |
Beta Was this translation helpful? Give feedback.
-
Can you please check your docker log and see if there are any messages related to Google Search Console? |
Beta Was this translation helpful? Give feedback.
-
Just checked. I see this. (also this is on Fly.io) 2023-01-31T00:00:01.581 app[3c232d15] lax [info] [0] [ERROR] Search Console API Error for domain.com (3days) : 403 Forbidden 2023-01-31T00:00:01.694 app[3c232d15] lax [info] [0] [ERROR] Search Console API Error for domain.com (7days) : 403 Forbidden 2023-01-31T00:00:01.811 app[3c232d15] lax [info] [0] [ERROR] Search Console API Error for domain.com (30days) : 403 Forbidden 2023-01-31T00:00:01.938 app[3c232d15] lax [info] [0] [ERROR] Search Console API Error for domain.com (30days) : 403 Forbidden |
Beta Was this translation helpful? Give feedback.
-
I have went through the steps listed here : https://docs.serpbear.com/miscellaneous/integrate-google-search-console In the Step 3: Part 2 - Its said "You should Already see a service account created." But I dnt see any service account created. I have to create one and I make it Owner.
Clearly there's some permissions error but I'm not sure whats missing. Please help me out as its been like 4 days of googling and testing with no results. |
Beta Was this translation helpful? Give feedback.
-
@yuvrajsagoo Can you please remove the last google project you created and start over? |
Beta Was this translation helpful? Give feedback.
-
I did a fresh installation. Login Access is in the screenshots below. you are login and check as well. Im not sure whats wrong. I did everything according to whats told in the documentation and the service account as told above. |
Beta Was this translation helpful? Give feedback.
-
Request are being made. but it throws 100% error. |
Beta Was this translation helpful? Give feedback.
-
Is there a way to set SEARCH_CONSOLE_PRIVATE_KEY and SEARCH_CONSOLE_CLIENT_EMAIL via fly.toml or some other file during installing? |
Beta Was this translation helpful? Give feedback.
-
Could you please reply. Been waiting from last week. |
Beta Was this translation helpful? Give feedback.
-
@towfiqi any update on this? |
Beta Was this translation helpful? Give feedback.
-
i have the same problem and I think that it correlates to this topic #50 I try to change the property on my site, but I think it would be easier to implement both ways as in the issue requested EDIT: i created a domain property in the search console, linked my page to the new property, set permissions for the service account and voila: its working now |
Beta Was this translation helpful? Give feedback.
i have the same problem and I think that it correlates to this topic #50
serpbear uses domain level properties and most of the properties in google search console is a URL-prefix property.
I try to change the property on my site, but I think it would be easier to implement both ways as in the issue requested
EDIT: i created a domain property in the search console, linked my page to the new property, set permissions for the service account and voila: its working now