diff options
| -rw-r--r-- | issues/cd-gn3-configurations.gmi | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/issues/cd-gn3-configurations.gmi b/issues/cd-gn3-configurations.gmi index d699849..dac5280 100644 --- a/issues/cd-gn3-configurations.gmi +++ b/issues/cd-gn3-configurations.gmi @@ -1,5 +1,14 @@ # GN3 API Configurations on CD +## Tags + +* assigned: alexm, Bonfacem +* keywords: configurations, CD, API, genenetwork3 +* type: bug +* priority: high + +## Description + The issue is that there is no straightforward way of knowing how to call the GN3 API from GN2. Multiple configurations, such as GN_SERVER_URL and GN3_LOCAL_URL, exist, making it difficult to understand how to debug. The `GN_SERVER_URL` which from config is running on port 8880 results into this error: @@ -7,10 +16,3 @@ The `GN_SERVER_URL` which from config is running on port 8880 results into this ``` "HTTPConnectionPool(host='localhost', port=8880): Max retries exceeded with URL: /api/llm/gnqna (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdd45a8d5a0>: Failed to establish a new connection: [Errno 111] Connection refused'))" ``` - -## Tags - -assigned: alexm, Bonfacem -keywords: configurations, CD, API, genenetwork3 -type: bug -priority: high
\ No newline at end of file |