404 There is nothing here! after all setup completed

Exchange self-hosting
#1

After all setup completed and while trying to enter my domain i get the error below

404 There is nothing here!

If you are an exchange administrator, and facing this page after the initial setup, You probably missed to setup domain(s) for the exchange.

If you haven’t bind domain(s) for the exchange yet, please run ‘hollaex prod’ command to do so.

Please visit docs.hollaex.com to see guides, forum.hollaex.com to get further help.

Regards, HollaEx Team.

I set hollaex prod to my domain many times but still same problem and when i try to get ssl i got error
Detail: No valid IP addresses found for …

/v2/health is ok and everything seems fine but i got stuck to see my exchange website :frowning:

#2

Have you rebuilt the web after using the prod command? Most likely your web is pointing still to localhost instead of the correct domain/ip address.

#3

Yes i did it. But still same :frowning:

#4

Hi there.

Can you go to your /settings directory of your HollaEx Kit folder, and check the configmap file?

They’re gonna be 2 values for setting up domains:

  • HOLLAEX_CONFIGMAP_DOMAIN
  • HOLLAEX_CONFIGMAP_API_HOST

Could you please post those values here?

Thank you.

#5

Hi,

I’m facing this issues as well. Deployed the exchange to a Kubernetes cluster. All the pods are running, the Ingress + Cert-Manager are running (certs have been issued).
These 2 variables:

  • HOLLAEX_CONFIGMAP_DOMAIN
  • HOLLAEX_CONFIGMAP_API_HOST

Are set, and the corresponding configmap, ‘holla2-env’ in the cluster has the correct data, e.g.
:
data:
ADMIN_EMAIL: “”
API_HOST: https://trade.[redacted].com/api
API_NAME: holla2
CURRENCIES: xht,usdt
DB_DIALECT: postgres
DB_SSL: “false”
DEFAULT_THEME: dark
DOMAIN: https://trade.[redacted].com
:

What else can I check?

Thanks in advance.

#6

hollaex status --kube

Calling the exchange health page (https://trade.[redacted].com/api/v2/health) …
The health page is not responding. Please check the exchange is up.

There are 3 ingresses:

holla2-ingress-plugins
holla2-ingress-stream
holla2-ingress-web

Is there supposed to be one ingress for the ‘api’ as well?

All the pods are running:

holla2-db-7446d98dc-llxkm               1/1     Running   0          5h39m
holla2-redis-68878888c4-cbjf5           1/1     Running   0          5h39m
holla2-server-api-76fbc7644-vqtqn       1/1     Running   0          5h39m
holla2-server-plugins-d96994cc6-bpzcv   1/1     Running   0          5h39m
holla2-server-stream-585759fff5-xv5xp   1/1     Running   0          5h39m
holla2-web-6fd6b667c9-xcb2j             1/1     Running   0          6h2m
1 Like
#7

I think there should be an ingress for the /api/v2/health path.
At the moment, the ingress-plugins path is:

path: /api/plugins(/|$)(.*)

The “ingress-stream” path is:

path: /stream

And the ingress-web path is:

path: /

Running “hollaex status --kube” showed:

kubectl and helm detected

kubectl version:

Client Version: version.Info{Major:“1”, Minor:“22”, GitVersion:“v1.22.8”, GitCommit:“7061dbbf75f9f82e8ab21f9be7e8ffcaae8e0d44”, GitTreeState:“clean”, BuildDate:“2022-03-16T14:10:06Z”, GoVersion:“go1.16.15”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“22”, GitVersion:“v1.22.8”, GitCommit:“7061dbbf75f9f82e8ab21f9be7e8ffcaae8e0d44”, GitTreeState:“clean”, BuildDate:“2022-03-16T14:04:34Z”, GoVersion:“go1.16.15”, Compiler:“gc”, Platform:“linux/amd64”}

helm version:

version.BuildInfo{Version:“v3.9.0”, GitCommit:“7ceeda6c585217a19a1131663d8cd1f7d641b2a7”, GitTreeState:“clean”, GoVersion:“go1.17.5”}

NAME READY STATUS RESTARTS AGE
holla2-db-7446d98dc-llxkm 1/1 Running 0 6h25m
holla2-redis-68878888c4-cbjf5 1/1 Running 0 6h25m
holla2-server-api-76fbc7644-vqtqn 1/1 Running 0 6h25m
holla2-server-plugins-d96994cc6-bpzcv 1/1 Running 0 6h25m
holla2-server-stream-585759fff5-xv5xp 1/1 Running 0 6h25m
holla2-web-6fd6b667c9-xcb2j 1/1 Running 0 6h48m

Calling the exchange health page (https://trade.[redacted].com/api/v2/health) …

The health page is not responding. Please check the exchange is up.

Do I need create an Ingress to the /api/v2/health ? Or does the pods communicate internally via the services to access the /api/v2/health endpoint?

Checking the api pod for the log output:

{“level”:“info”,“message”:“fa6a89b3-db1b-4800-af04-91eba8ac42a1 middleware/hostname localhost GET /v2/health”,“timestamp”:“2022-06-25T14:47:51.089Z”}
{“level”:“verbose”,“message”:"fa6a89b3-db1b-4800-af04-91eba8ac42a1 origin “,“timestamp”:“2022-06-25T14:47:51.089Z”}
{“level”:“info”,“message”:”::1 - - [25/Jun/2022:14:47:51 +0000] “GET /v2/health HTTP/1.1” 200 94 “-” “curl/7.64.0”\n ",“timestamp”:“2022-06-25T14:47:51.091Z”}
{“level”:“info”,“message”:“ca442059-acf4-46d8-8ec4-a8ea2eee8ead middleware/hostname localhost GET /v2/health”,“timestamp”:“2022-06-25T14:48:06.087Z”}
{“level”:“verbose”,“message”:"ca442059-acf4-46d8-8ec4-a8ea2eee8ead origin “,“timestamp”:“2022-06-25T14:48:06.087Z”}
{“level”:“info”,“message”:”::1 - - [25/Jun/2022:14:48:06 +0000] “GET /v2/health HTTP/1.1” 200 94 “-” “curl/7.64.0”\n ",“timestamp”:“2022-06-25T14:48:06.088Z”}
{“level”:“info”,“message”:“d85d9755-9d3c-4d97-80ff-ff99ba13972f middleware/hostname localhost GET /v2/health”,“timestamp”:“2022-06-25T14:48:21.085Z”}
{“level”:“verbose”,“message”:"d85d9755-9d3c-4d97-80ff-ff99ba13972f origin “,“timestamp”:“2022-06-25T14:48:21.085Z”}
{“level”:“info”,“message”:”::1 - - [25/Jun/2022:14:48:21 +0000] “GET /v2/health HTTP/1.1” 200 94 “-” “curl/7.64.0”\n ",“timestamp”:“2022-06-25T14:48:21.088Z”}

It gets a HTTP 200 response code, so it would appear to be OK!
hollaex status --kube says unreachable!

Also, out of curiousity, what does this ‘middleware/hostname localhost’ mean?

{“level”:“info”,“message”:“d85d9755-9d3c-4d97-80ff-ff99ba13972f middleware/hostname localhost GET /v2/health”,“timestamp”:“2022-06-25T14:48:21.085Z”}

1 Like