Bad Remote Endpoint in Amazon Developer Console about geemusic HOT 5 CLOSED

For ngrok, I use something like Screen or Tmux (two terminal management programs) to easily keep it in the foreground. From what I can tell foreman is used to load the .env file which stores your google credentials. I have no idea on the advantages though.

from geemusic.

I also use tmux to keep ngrok running in the foreground and it has worked great for me. I just accept the fact that if my server power cycles I have to run through a few setup steps again. But then I don't have to pay so it works for me. Here's my setup steps, in case it is useful (I just stuck all this in a text file on the server to remind me how to do this down the road when I inevitably forget):

Open session and start ngrok:
tmux new -s ngrok
./ngrok http 5000
Copy ngrok address
Disconnect with Ctl+b then d

Paste ngrok address into ~/geemusic/.env
Paste ngrox address (with /alexa at the end) into amazon developer console under configuration tab

Open session and start server
tmux new -s server
cd geemusic
foreman start
Disconnect with Ctl+b then d

Test server on amazon developer test section
If needed, connect to tmux sessions with tmux a -t

from geemusic.

Thanks - I may have to do the same as I'm about out of ideas to turn this into a service. It appears that letsencrypt is supported, so that shouldn't be the problem. When I hit the URL in my browser it shows as secure and I see the GET request in the server log. However I'm still getting `The remote endpoint could not be called, or the response it returned was invalid.' in the Service Simulator. I'm at pretty much a dead end until I can get a better error message.

Regarding foreman doh! I should have remembered that. I was too busy messing w/ the endpoint I didn't realize that even though the server was up, it wouldn't have authenticated!

Anyways thanks for the tmux instructions!

from geemusic.

Going to close this, as this seems like more of an issue with setup than the library itself. Thanks for handling this @PostsDesert and @alexbaucom17!

from geemusic.

I keep getting "There was an error calling the remote endpoint, which returned HTTP 503 : Service Unavailable" when trying to test in the Amazon Alexa service simulator. I built the app in Heroku following the instructions. I rebuilt the app multiple times with the same result. Any ideas?

from geemusic.