Closed nuentes closed 7 years ago
@nuentes it is because the URLs is not correct, refer to the installation of guide, it's http://ALEXA.DEVICE.IP.ADDRESS:5050/code where different to the alexa-avs-sample-app install guide.
I'm going to the addresses provided by alexa-pi in the 2nd to last line of my last post:
both give the error I mentioned above.
Both give a 500 Internal Server error.
Try to use not local IP address, but rather your full.domain.name:5050 . Ensure port 5050 on your Raspberry is available from internet for Amazon servers. For me it works.
I've tried all the following: 192.168.1.11:5050 (tested on both host and client) localhost:5050 (tested on host only) www.mydomain.com:5050 (tested on host and client)
All of them result in the Amazon error which I displayed. Isn't receiving the Amazon error proof that the connection is being made, anyway? Why else would all these tests resolve to Amazon.com? The connection can't possibly be the issue.
I've turned off my Pi's VPN entirely, and the issue persists. Port 5050 is not being used by any other service, as far as I know. If it were, I doubt I'd be able to load the page at all.
So just to be sure,
You went to developer.amazon.com and logged in.
Navigated to the settings for your alexa device.
Under Security Profile / Web settings, you entered:
Now, edit your config file with sudo nano /etc/opt/AlexaPi/config.yaml
Go down to the Amazon Alexa settings, and verify that you have the right things entered for:
They should match everything in your developer.amazon.com account from above. Exit and save changes.
sudo /opt/AlexaPi/src/auth_web.py
.
From a separate computer, on the same network, navigate to 192.168.1.11:5050 and log in with your amazon credentials.That should work. If it doesn't, go back and make sure you haven't mis-typed something. Every time I've run into this problem I've fat-fingered something.
Ah - there we go. I forgot to change the Allowed Origins and Allowed Return URLs in the Developer console from alexa-avs-sample-app. That took care of it. My bad. I'm an idiot.
No worries! I've previously lost a couple days on a space where it shouldn't have been. :)
I am getting the same error. Checked config.yaml, it matches everything I have for my security profile. The one difference is in the web settings it doesn't allow to use http for anything other than localhost. Here are my entries
Allowed Origins | http://localhost:5050 https://192.186.86.40:5050 |
---|---|
Allowed Return URLs | http://localhost:5050/code |
https://192.186.86.40:5050/code
Here is the error I'm getting from amazon. It's weird because I think it needs to have the return URL set to http://my.pi.ip.address:5050 but it won't let me add that on the amazon developer page. It only accepts https.
Error Summary 400 Bad Request The redirect URI you provided has not been whitelisted for your application. Please add your redirect URI in the 'Allowed Return URLs' section under 'Web Settings' for your Security Profile on Amazon Developer Portal. Request Details scope=alexa%3Aall redirect_uri=http%3A%2F%2F192.168.86.40%3A5050%2Fcode response_type=code client_id=I redacted this but verified it is correct in config.yaml. scope_data=%7B%22alexa%3Aall%22%3A+%7B%22productInstanceAttributes%22%3A+%7B%22deviceSerialNumber%22%3A+%22721d24bab2580c6cbe4fdb8f610b0d88c10144b6f4c88db74b216699a595deb2%22%7D%2C+%22productID%22%3A+%22Grace%22%7D%7D
In my case it was a cherrpy issue. I installed the 10.x version, but later installing the 17.4.0 version fixed the issue.
sudo pip install CherryPy==17.4.0
Details:
When I tried to see if it was a cherrpy issue and tested a simple server, I started to get the below error:
Module_six_moves_urllib_parse' object has no attribute 'unquote_to_bytes
I have upgraded the package called six
(from v10 to v11) but it didn't solve the issue.
Why not upgrading to the latest version of cheerypy? Because <18.x requires <=python 3.5
I can't seem to complete the install... I'm stuck at the very last step. The amazon page will not load either on the local device or through the network, I always get this error message. From searching this issues list, it seems it's possible this is related to the .asoundrc file, which I did modify to:
This was working fine while I was using the alexa-avs-sample-app, but I have decided to migrate to this fork. Here is my install log: