Failed to load API definition. NetworkError when attempting to fetch resource.

[bugger11]

All services give the error:
Failed to load API definition.
NetworkError when attempting to fetch resource. http://192.168.1.1:8529/_db/_system/_admin/aardvark/foxxes/docs/swagger.json?mount=/aye-aye

I start ArangoDB like this: # /usr/bin/arangod --server.endpoint "http+tcp://192.168.1.1:8529"

INFO ArangoDB 3.4.0 [linux] 64bit, using jemalloc, build , VPack 0.1.33, RocksDB 5.16.0, ICU 58.1, V8 5.7.492.77, OpenSSL 1.1.1a 20 Nov 2018

INFO detected operating system: Linux version 4.19.12-arch1-1-ARCH (builduser@heftig-21538) (gcc version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Fri Dec 21 13:56:54 UTC 2018

Mode: Single-Server
Storage-Engine: mmfiles
Total RAM in your machine: 8 GB

free -m
              total        used        free      shared  buff/cache   available
Mem:           7902         513        4641           1        2746        7120
Swap:          8073           0        8073

Used Package: AUR (en) - arangodb https://aur.archlinux.org/packages/arangodb/

I'm using Firefox to access the Web UI.

These are the steps to reproduce:

open the browser on http://192.168.11:8529
log in as root
use database _system (or any other db)
click 'Services', on any service, navigate to API tab, then you would the error shown above

At first I thought my issue was the same as an existing issue, but now I believe they are different. See older issue here: Failed to load API definition · Issue #4453 · arangodb/arangodb #4453

[maxkernbach]

Hi @bugger11,

we were not able to reproduce this issue, are you still facing this problem?

In order to reproduce, we executed the following steps:

1. Install the given AUR package (ArangoDB 3.4.0) on Arch Linux
2. Access UI with Firefox
3. Install a service (e.g. aye-aye) via "Add Service" in the Services Menu
4. Access API tab of a service (e.g. aye-aye)

-> The API is correctly displayed, no error occured

[maxkernbach]

@bugger11

In addition to installation packages (distribution dependent) a tar.gz archive is available starting from version 3.4.0.
Since we were not able to reproduce your issue, could you please check if this problem persists when using the latest linux tar.gz archive (section Tar package) to start a server?

Basic usage instructions can be found in the README after extracting the archive.

[bugger11]

I can still reproduce the issue with linux tar.gz archive version 3.4.0. The steps to reproduce it are the same. However, I can add that ArangoDB is not running on localhost. It is running on another machine on the lan. Everything works correctly except this issue. Thanks for looking into it. I'll add more info when I get more clues about what might be causing it.

…

On Tue, Feb 5, 2019 at 7:17 AM maxkernbach ***@***.***> wrote: @bugger11 <https://github.com/bugger11> In addition to installation packages (distribution dependent) a tar.gz archive is available starting from version 3.4.0. Since we were not able to reproduce your issue, could you please check if this problem persists when using the latest linux tar.gz archive <https://www.arangodb.com/download-major/ubuntu/> (section *Tar* package) to start a server? Basic usage instructions can be found in the README after extracting the archive. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7892 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArwaF73q3zxDA-edpLqyCNHGCeiORC8eks5vKXZRgaJpZM4Zys2n> .

[dothebart]

do you by any chance also use an SSL-Endpoint? for some reason swagger fails to properly create the URL to the API-definitions in some cases. It can be found by carefully looking into the network tab of the Browser-tools (f12)

[bugger11]

My endpoint is not SSL, but I do define it with this URL string: "http+tcp://192.168.1.2:8529" Could that URL format be related to the issue perhaps? To confirm that my endpoint is not SSL, I did use the browser tools and the endpoint is shown as "not secure".

…

On Thu, Feb 7, 2019 at 5:40 AM Wilfried Goesgens ***@***.***> wrote: do you by any chance also use an SSL-Endpoint? for some reason swagger fails to properly create the URL to the API-definitions in some cases. It can be found by carefully looking into the network tab of the Browser-tools (f12) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7892 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ArwaF0gQn9rlIp3laI0tC987CBW7s4oWks5vLAKbgaJpZM4Zys2n> .