I am hosting a RASA chatbot inside a docker-container in Okteto cloud. I have a custom action which writes data to a remote airtable base. Everything works perfectly when I test the bot locally, but it fails when the bot in hosted in the cloud. The logs return me Couldn't connect to the server at 'http://rasa-actions:5055/webhook'. Is the server running? Error: Server disconnected when I know my server is running and connected with the bot.
Do I need to add anything to my docker file or the docker-compose file to get this working?
Related
I have an nodejs application where I connecto to devices via opcUA and send data via websocket to web page which works fine so far...but now I want to add a device where the server ip and the available endpoint is different.
The server ip is opc.tcp://192.168.5.65:4840 and the endpoint is opc.tcp://proto-01:4840.
I can connect to the server, read and console.log the available endpoint but when I try to create a session I get the error: endpoint opc.tcp://192.168.5.65:4840 does not exist.
I can connect to the device with UA-Expert without any problems but get the message that the naming was changed to proto-1.
Does anybody know how to convince node opcua to connect to endpoint? I haven't found anything related to such a problem.
I started using Node-Red from IBM Bluemix. I successfully created the Node-Red Starter plan and started working with Node-Red. After about a week of using my browser started responding with
This site can’t provide a secure connection mybluemixapp.us-south.cf.appdomain.cloud sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
I can access the URL from my companies network and the connection is secure. I have done a bit of googling and tried the solution post here
but no luck. Any ideas?
I am running Ignite Web Console and Web Agent in k8s v1.9, but connection fails when using security - works fine without security. I am able to access Ignite REST API by passing 'X-Signature' value in Header using Postman, but see no way to do this through the Web Console. Same with dBeaver.
Web Console do not support connection to secured cluster.
I created issue: IGNITE-8428 Web Console: Support connect to secured cluster.
You can track it.
i'm trying to trigger builds on jenkins when ever a pull request is merged, and trying to add the webhook, which is throwing me the below error.
payload url: http://localhost:8080/job/hook-test/
error: "We couldn’t deliver this payload: Couldn't connect to server "
The URL for the webhook is localhost. GitHub is trying call the webhook on itself.
You need to deploy Jenkins in a publicly accesible URL. It won't work with a local Jenkins install in your PC.
localhost refers to the address of the current machine. When you type localhost in the browser and you access Jenkins, that works because you have Jenkins installed and running in your PC. Access localhost from a different machine and you won't be able to access Jenkins. When you tell github to send the webhook to localhost it will not try to send it to your machine, instead, it will send the webhook to the same machine in which github server is running, and that machine doesn't have Jenkins installed.
The problem here is localhost means something different for you and for github.
To solve this problem, you'll either need to install Jenkins in a public server accesible from internet (so that github can send the webhooks) or use some online service which provides hosted Jenkins servers.
You could also just get a domain and configure it to point to your PC. You would probably need to do some networking configuration but once it's done you (and github) will be able to access your jenkins via some-domain.example.io instead of localhost. Be careful, you would be making your (I asume personal) PC accesible from the internet, and that has security risks.
If you can afford it I recommend using a server in the cloud to run this.
Many cloud platforms even provide a quite long free trial period (I know Amazon and Google Cloud do).
I have a Liberty Websphere application hosted on Bluemix that connects to Exchange Web Services. When I run this api on localhost it works fine and returns the desired results. But when I host it on bluemix, it returns the error
"500 Error: Failed to establish a backside connection"
No errors in the logs.
i have tried the solutions given in other posts and searched a lot on internet. But still not able to solve this issue.
Finally the problem is resolved. There was a configuration error in the application as my company's Bluemix server is on dev environment and the application was trying to connect to the prod environment.
When we connected using the dev IDs, from dev bluemix servers to dev exchange servers, the application works fine.