500 Error after auth_web

[alexa-pi]

500 Error after auth_web

[maso27]

I saw this error when I tried to use the built-in browser on the Raspbian desktop. Tried in Chrome on my Windows box and it worked with no issues.

[thesingingmoose]

I had the error on the Raspbian browser as well as chrome on a Windows laptop. Could the browser matter?

[maso27]

Did you put all four of the addresses into developer.amazon.com?

http://localhost:5000
http://[ip_address]:5000

http://localhost:5000/code
http://[ip_address]:5000/code

And did your IP address change for your raspberry pi maybe?

[thesingingmoose]

Yeah, had first 2 as origin and second 2 as return. I am sshing into the pi at the same time, so I dont think IP changed

[tdicola]

I just ran into this and what was happening was me accessing http://raspberrypi:5000/ and it trying to redirect to http://raspberrypi:5000/code without that URL being set in the security profile web settings. Make sure your security profile web settings have exactly the URL you're using to access the Pi. The instructions call for using localhost but it seems like that will only work if you're using the browser on the Pi itself to access localhost. Probably best to add http://raspberrypi:5000 and http://raspberrypi:5000/code so you can access under that URL from another machine.

[thesingingmoose]

I have both localhost:5000 and RPi_IP:5000 added in the web settings (and /code for both for return).

I now get to the login screen, login, hit "OKAY" to access my device, and then hit the error.

[thesingingmoose]

There's also no longer a 500, just an error message and a link to Amazon home page

[burf2000]

Has anyone found a fix for this?

[thesingingmoose]

Worked when I made a new device in Amazon Dev Portal

[chimeranzl]

Has anyone found a fix for this?

Old post I know, but for anyone else... Delete the line refresh_token: "token_code"

and replace with...

refresh_token:

(no double quotes after it) then try again. It seems the internal error 500 is caused by the token line existing in the /etc/opt/Alexpi/config.yaml file. Also seems re-running setup.sh, doesn't actually replace with a fresh one when selecting the menu option, nor does it mention that the refresh token should be deleted. You don't need to create a new device or new security profile in AWS - just make sure everything matches