Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Apps
-
HD-Enabler:Wirecloud
Description
Created question in FIWARE Q/A platform on 02-04-2017 at 19:04
Please, ANSWER this question AT http://stackoverflow.com/questions/43171367/fiware-wirecloud-mahup-ngsi-source-operator-cant-reach-ngsi-proxy
Question:
Fiware Wirecloud Mahup: ngsi-source operator can't reach NGSI Proxy
Description:
I'm trying to use Wirecloud the latest version available for a simple mashup project. I'm using the ngsi-source operator to retrieve data from Orion, but this is not possible because I often encounter an NGSI Proxy Connection Error (504 Gateway Timeout).
I tried with different installations of the NGSI Proxy in different servers and I have noticed that I have a 200 status in the inner REST calls made by the ngsi-source operator, only when the NGSI Proxy is reachable from the Wirecloud server installation (django server).
When the proxy is reachable only from my browser (local machine), I encounter the 504 status.
The NGSI Proxy has to be reachable from the Wirecloud installation?
Thanks in advance for the answers.
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
HD-Enabler | Wirecloud [ 10857 ] | |
Description |
Created question in FIWARE Q/A platform on 02-04-2017 at 19:04 {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/43171367/fiware-wirecloud-mahup-ngsi-source-operator-cant-reach-ngsi-proxy +Question:+ Fiware Wirecloud Mahup: ngsi-source operator can't reach NGSI Proxy +Description:+ I'm trying to use Wirecloud the latest version available for a simple mashup project. I'm using the ngsi-source operator to retrieve data from Orion, but this is not possible because I often encounter an NGSI Proxy Connection Error (504 Gateway Timeout). I tried with different installations of the NGSI Proxy in different servers and I have noticed that I have a 200 status in the inner REST calls made by the ngsi-source operator, only when the NGSI Proxy is reachable from the Wirecloud server installation (django server). When the proxy is reachable only from my browser (local machine), I encounter the 504 status. The NGSI Proxy has to be reachable from the Wirecloud installation? Thanks in advance for the answers. |
Created question in FIWARE Q/A platform on 02-04-2017 at 19:04
{color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/43171367/fiware-wirecloud-mahup-ngsi-source-operator-cant-reach-ngsi-proxy +Question:+ Fiware Wirecloud Mahup: ngsi-source operator can't reach NGSI Proxy +Description:+ I'm trying to use Wirecloud the latest version available for a simple mashup project. I'm using the ngsi-source operator to retrieve data from Orion, but this is not possible because I often encounter an NGSI Proxy Connection Error (504 Gateway Timeout). I tried with different installations of the NGSI Proxy in different servers and I have noticed that I have a 200 status in the inner REST calls made by the ngsi-source operator, only when the NGSI Proxy is reachable from the Wirecloud server installation (django server). When the proxy is reachable only from my browser (local machine), I encounter the 504 status. The NGSI Proxy has to be reachable from the Wirecloud installation? Thanks in advance for the answers. |
HD-Chapter | Apps [ 10836 ] |
Assignee | Álvaro Arranz [ aarranz ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
36d 17h 59m | 1 | Backlog Manager | 09/May/17 3:04 PM | |||||
|
3h | 1 | Backlog Manager | 09/May/17 6:04 PM | |||||
|
1d 3h | 1 | Álvaro Arranz | 10/May/17 9:05 PM |
2017-04-02 21:05|CREATED monitor | # answers= 0, accepted answer= False