-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port forwarding is not working #62
Comments
Typically NATing will create the network listener on your EXTERNAL
(internet facing) interface, not the internal one (192.168.1.254).
You should try telneting to port 8080 on your external address. If you
don't know what it is, you can go to http://www.whatsmyip.org/ and it
should tell you what it is.
The next part of the NAT is to make sure that this is actually passing
traffic down your DirecTV. You can test this in the browser by going to
http://[external address]:8080/info/getLocations {updated this comment}
If you connect, the browser should respond with some details about your
setup.
…On Sat, Jan 6, 2018 at 6:32 PM, royatatl ***@***.***> wrote:
Hello guys,
I followed the instructions from #12
<#12>
I found out that the port forwarding is not working.
When I typed http://[local_ip of my direct TV]:8080/remote/processKey?key=pause&hold=keyPress
in the internet browser, my tv actually paused.
Then I typed http://192.168.1.254:8080/remote/processKey?key=pause&
hold=keyPress in the browser, it shows "safari could not connect to the
server".
So I logged in my modem http://192.168.1.254, and allowed the port
forwarding with port 8080.
[image: untitled copy]
<https://user-images.githubusercontent.com/35180944/34645304-b383f642-f317-11e7-8654-5ffb80229c38.jpg>
Ideally, that should allow the port forwarding. But it did not help.
I telnet the ip of modem with port 8080, it was refused, while telnetting
direct tv is connected.
[image: untitled1]
<https://user-images.githubusercontent.com/35180944/34645332-3c550f7e-f318-11e7-8b58-283ef5f425e6.jpeg>
Any suggestion?
Thanks,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#62>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACibPVHOzdmkNydfcfn3VLo4Jap2vLWqks5tIBCDgaJpZM4RVfX6>
.
|
@mawrew19 Thank you so much for your response. Then I tested https:///info/getLocations. However, it did not get any response. Any suggestion? |
http://192.168.1.254/info/getLocations for local lan replace with wan if you want to do it from outside your network. |
@bklavet I don't believe this will work since the NAT isn't likely on the internal interface as well as the external. 192.168.1.254 is the inside address of the router, I believe. @royatatl If the pause worked from your mobile on LTE, then your NAT config looks to be good. The "index" file should include this "[external address]" on line 8. Are there any more detailed messages on the errors you post? Was this when attempting to upload the project? |
@mawrew19 "http://[externalAddress]:8080/info/getLocations" on my phone finally works Did you mean the format of IP address in the index file is like var local_ip = "xx.xx.xxx.xxx" instead of var local_ip = 'xx.xx.xxx.xxx' ? Here are the detailed error messages after I configured a test event on https://console.aws.amazon.com 02:53:50 |
Good news on the NAT! No. I was more clarifying which address you should put on line 8. This should be your EXTERNAL Address. |
My bad. |
Cool. So you get the error while uploading the zip file?
…On Sat, Jan 6, 2018 at 9:54 PM, royatatl ***@***.***> wrote:
My bad.
http://[externalAddress]:8080/info/getLocations works
The index file zipped up with the AlexaSkill file as I did follow b
Money's tutorial video.
:(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#62 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACibPRaNB099FpHHmT4tFKALA1JbTFzrks5tID_hgaJpZM4RVfX6>
.
|
No error when I upload and save it. |
Hey royatatl! What happens when you test from the service simulator in the developer site? |
I figured out the reason. It is working now!!!!! I am so glad. Thank you folks so much for your help and patience. Have a wonderful weekend! |
Hello guys,
I followed the instructions from #12
I found out that the port forwarding is not working.
When I typed http://[local_ip of my direct TV]:8080/remote/processKey?key=pause&hold=keyPress in the internet browser, my tv actually paused.
Then I typed http://192.168.1.254:8080/remote/processKey?key=pause&hold=keyPress in the browser, it shows "safari could not connect to the server".
So I logged in my modem http://192.168.1.254, and allowed the port forwarding with port 8080.
Ideally, that should allow the port forwarding. But it did not help.
I telnet the ip of modem with port 8080, it was refused, while telnetting direct tv is connected.
Any suggestion?
Thanks,
The text was updated successfully, but these errors were encountered: