-
Notifications
You must be signed in to change notification settings - Fork 44
Google Account linking fails with 'Invalid ClientID' #28
Comments
The proxy issue will be solved with the update on saturday. This seems like a different issue. First a simple thing, to make sure there is no misunterstanding: Could you read #26 ? Are you linking the account as described there? |
thank you for the assistance @peterkappelt . I mis-read the docs and thought you linked it from web page, my apologies. |
Were you able to resolve the problems? Do you need further assistance? |
@peterkappelt I have been bashing my head against this problem for the past couple of hours. I have a self-hosted instance of it running on docker. I folllowed the documention very closely. I am not sure what I am missing. I am fairly certain there is a bug some where. The form that is rendered for linking account has no client_id value nor it has any other values. its completely empty.
I am hosting it on 192.168.1.107:8888, I even tried hacking the values in but eventually it complains about invalid RedirectURI and rightly so. Since I have a FQDN configured within app settings on Google. I even tried removing all security barriers put by mod_proxy. Exposing the entire gBridge to the internet. But then, authentication stops working. Lastly, I cant even see the project I have registered within Google Actions. Do I have to complete the entire process of deploying to production before I see it? Even that part of Google Actions is broken.
Here is my docker compose file.
|
I have even tried adding
The ClientID problem still persists. My apache2 config contains
|
Same! I am trying to link through the Google Home app. Entering my information there however, gives this error:
Like @shoaibali mentions; the source of I validated that
MQTT and nginx with ssl certificates are running on the server successfully as well. |
I have same problem |
I still get this famous "invalid ClientID" ubuntu@ubuntu:/opt/gbridge$ docker-compose up |
same problem here, any suggestions on how to solve? |
I'm not sure if this service is still running, I believe it was shut down beginning 2020: https://about.gbridge.io/notice/ |
as I understand it is possible to host the service, as I believe that most in this issue are trying. |
I have tried the above fixes to the docker-compose file and ApplicationServiceProvider file and still having issues with the account linking being redirected to /gapi/auth. Is there something else I have missed. I have had a look in the docker-compose logs for errors but everything appears ok, no fatal errors.
To try and get round the proxy issue I used my Sophos firewall WAF function, and stopped apache. I can know add account details as page direct is right but on pressing 'Link Accounts' I get a red error box on the web page saying 'request by Googlehome is malformed .... Invalid ClientID provided'. Checked google console and docker-compose file and clientid entry match. Is this another issue.
Originally posted by @jaseuk73 in #17 (comment)
The text was updated successfully, but these errors were encountered: