when i try connect amazon develper with raspberry pi, using ngrok, only output 502 Bad Gateway.
I tried all, and i saw a lot fórums like this, but anything worked. I'm trying https://developer.amazon.com/blogs/post/Tx14R0IYYGH3SKT/flask-ask-a-new-python-framework-for-rapid-alexa-skills-kit-development.
Can you help me? Thanks
try using ./ngrok http 127.0.0.1:YOUR_PORT
Make sure your program is running on the Pi. Check localhost:"Your port number" and see if your default page shows up. ngrok simply tunnels whatever is on your localhost onto a web endpoint. Make sure your port number is correct. I know Flask-Ask uses port 5000.
Related
I have my flask app running in backend on port number 5000 and reactjs front end running on port number 3000, How can I make both running on same port number?
Can anyone help on this.
It would be great help.
You can't. It is not about React. It is how networking works. Each port can only bind to one and only one process.
However, I kind of get what you are trying to achieve, you may use proxy to achieve a similar effect.
https://create-react-app.dev/docs/proxying-api-requests-in-development
at my wits end here. I am trying to view my react app hosted at: http://localhost:3000 on a mobile device. When I navigate to http://xxx.xxx.xx.x:3000 on my mobile device (x being my ip address) I get the error that the server refused to respond.
-I have tried adding an incoming rule in my windows defender firewall to allow access on port 3000 from tcp connections. Yet the error still persists.
-I have even temporarily attempted to turn off my firewall to test the connection and I still get the same result.
-my mobile and my localhost are on the same network
i have specified an outgoing rule for port 3000 as well
I am using create react app for my boilerplate code so I haven't edited any of the webpack settings. I am hoping someone might have a suggestion for me as to what I can try next?
I used my ipv6 address instead of my ipv4 address which was the incorrect address
I would like a solution for the following problem:
I have a client in angular running on gulp in this configuration I can navigate throw my page writing in my browser the following:
(for example) localhost:3000/show/05-05-2017/10
I have the same client in loopback and it is working with localhost:3000, the problem is when I want to get the same parameter url with loopback localhost:3000/show/05-05-2017/10 I get an error 404 can not get /show/05-05-2017/10
I would like to know some idea where I could find a solution to that or somewhere to look for.
Thank you!
Are you running both services on the same port 3000 ? If so that can't work only one server per port is possible.
Change the port of one of them and it should work.
I hope this helps.
I could find the solution here:
https://groups.google.com/forum/#!topic/loopbackjs/qt9CurkKi_s
I've successfully started RendezVous_Hans_A_Multicast_Participant on one PC and on another I've started Edge_Teyacapan_Another_Multicast_Participant but the connection between them is not getting established. Both the PCs are behind the same Wifi router NAT.
Is this the correct way to connect peers behind a Wifi router using JXTA 2.6 ? Am I missing something?
Thank you.
Holly,
Please do use JXTA version 2.7 instead of 2.6. Also, can you post the log messages that JXTA spits out. The messages are very helpful in finding out the problem.
Thanks
DD
I am using openCyc and I am trying to connect to an image of a Cyc KB. I can browse this image on my browser (using chrome) and can successfully ping the address from the command line.
Now, when I try to create a new CycAccess("server", "port) the correct server and port of the image I am browsing on the browser I get an error saying connection refused which is printed out to the terminal.
For the server, it is simply xxxxx.yyyyy.com and the port is just for example 6622. Am I formatting this wrong or something?
Why would this happen?
Thank you,
Rich
I found out the answer to my question. IDK if this well help anyone else so I am going to post it.
Answer:
The port that you typically access a CYC Image through the browser is not necessarily the port that you will access it through the OpenCyc API. When I changed the port, it solved my problem.
Rich