Aug 30, 2019
When I'm trying to link my Bose Music account in the Google Home app, after the login I receive a proxy error 500. Tried with several WiFi networks and 4G connections.
Please, see the attachments. Thx!
Thank you for your post and welcome to the Bose Community.
I am sorry to hear that you are having some trouble linking Google Home with the Bose Music app.
I would recommend following these steps:
Let me know how you get on with this.
Charlotte G - Community Support
Aug 25, 2019
I went through all of the steps provided by the moderator for the exact same issue (proxy 500 error) and none of these worked for me. I tried ios, android, iphone, ipad, deleting app, resetting sound bar etc etc
It was then suggested to try to have the same email address for your bose id, and google home/google assistant.
I deleted the app, reinstalled, and created a new bose id using the same email address I used for google home/assistant (but of course not the same password) -- then everything worked, and google assistant setup.
Hope this helps,
Sep 29, 2019
Thanks for reaching out via the Bose Community. Welcome to the website!
I am sorry to hear you are also having issues connecting your Bose Music profile to your Google account. I understand you have followed the above steps, but can you please confirm which country it is you are contacting us from, and also, are you using a VPN at all?
Oct 7, 2019
Same issue here! this error its internal (bose api).
No matter how many times you do the steps above.
It is an INTERNAL SERVER ERROR. Please fix this issue.
Thanks for reaching out and welcome to the Bose Community Forums.
I am sorry that you are having issues and would love to assist you. To start with please can I confirm:
I look forward to your response.
Hello Belen Cartes,
Thank you for posting and welcome to the community.
In your situation Belen, it is most likely connected to the fact you are in Chile, as we do not have support for Google home on our speakers in your region yet.
You can see a full list of voice assistant availability at this time from this link. We are actively working to expand which regions we are able to support these voice assistants in and will update the community and the list when we do.
Let us know if there is anything else we can help you with.
Jan 6, 2020
I’m located in Canada and have been experiencing the same issue.
Are there any plans to solve this issue in the near future?