Connection refused by NGSI-Proxy
Using the last version of ngsi-proxy to make Orion related wirecloud components work I get the following error when configuring my Orion Source component:
2fb0de97f49a.js:1737 GET http://localhost:3000/eventsource/12caae10-30eb-11e7-95ac-d72bca8f4488 net::ERR_CONNECTION_REFUSED
My configuration of the component is the following:
And I am running both Orion Context Broker (v1.7) and Wirecloud (v1.0) running locally. Version of the Orion Source operator is the latest I have found (3.0.7). No security is configured.
Could anyone help me to figure out what I am doing wrong?
Solution
The problem was that the ngsi-proxy didn't answer properly. I solved by using the public ngsi-proxy: https://ngsiproxy.lab.fiware.org (as it comes by default).
- Connect system which includes OPC UA IoT Agent, Orion Context Broker. Cygnus and Historic data with Postgres
- ERROR: Pool overlaps with other one on this address space
- Displaying Irrelevant Sensor Data in FIWARE Orion When Using IoT Agent-JSON and Mosquitto
- Get all Fiware-ServicePath for a specific Fiware-Service
- FIWARE PEP Proxy Wilma server fails to start
- FIWARE Orion-LD upsert replace endpoint: only attributes or completely (including type)?
- FIWARE FIROS Publish cmd_vel from Non-ROS-World
- Orion context broker doesn't create tenant databases "on the fly"
- IoTAgent (JSON) over MQTT doesn't receive measurements from mosquitto
- Orion sending error message "connection failed, after 100 retries"
- Orion-ld fails to establish a connection with the MongoDB Community Operator due to a connection string issue
- How to get the missing table Schema while using quantumleap in cratedb using orion LD context broker though the subscriptions are working?
- yum error "Cannot retrieve metalink for repository: epel. Please verify its path and try again" updating ContextBroker
- Specifying attributes to be aggregated by STHSink
- Why Orion-ld after 0.8.0 is not supporting the formation of service/subservice in quantumleap logs?
- issues configuring a device via bidirectional attributes using IOT agent JSON and Orion LD
- Error downloading and installing Java JDK in CentOS (FIWARE)
- Context provider application: MongoDB connection unsuccessful
- How to maintain a FIWARE apikey?
- How to get the servicePath from /v2/entities GET call
- Orion APIs authentication through Keycloak
- My dockerized service doesn't receive the notification sent by Orion Context Broker
- How to send massive data of sensors in Orion
- Notify python orion/quantumleap subscription changes
- Can I send a notification in the creation and deletion of an entity?
- HTTP POST request gets transformed to GET request
- Orion APIs authorization through Keycloak
- Fiware orion /op/query endpoint working explaination
- Subscription between Orion context broker and Quantumleap works, but table is not created in CrateDB
- Calling external APIs through fiware orion context broker to validate using keyrock