Can't connect to web interface.

xan

I got fusionauth running in a docker in ubuntu and have the 9011 port opened to my ip, but when I put in the servers address(and/or with the ip, and/or http/s) it times out.

xxx.xxx.xxx.xxx took too long to respond.

I am not sure what to do next, though I still need to setup the .env file which is my next step.

Here is some info that might be helpful

~$ docker ps
CONTAINER ID   IMAGE                                                 COMMAND                  CREATED      STATUS          PORTS                    NAMES
77842e098721   fusionauth/fusionauth-app:latest                      "/usr/local/fusionau…"   6 days ago   Up 30 seconds   0.0.0.0:9011->9011/tcp   ubuntu_fusionauth_1
dcbfc8978431   docker.elastic.co/elasticsearch/elasticsearch:7.8.1   "/tini -- /usr/local…"   6 days ago   Up 30 seconds   9200/tcp, 9300/tcp       ubuntu_search_1
3e5cb9c95e25   postgres:11.9-alpine                                  "docker-entrypoint.s…"   6 days ago   Up 30 seconds   5432/tcp                 ubuntu_db_1

~$ curl -v http://fusionauth:9011
* Could not resolve host: fusionauth
* Closing connection 0
curl: (6) Could not resolve host: fusionauth
ubuntu@ip-172-31-80-105:~$ curl -v localhost:9011
*   Trying 127.0.0.1:9011...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 9011 (#0)
> GET / HTTP/1.1
> Host: localhost:9011
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302
< Location: /login
< Content-Length: 0
< Date: Mon, 28 Dec 2020 16:26:30 GMT
<
* Connection #0 to host localhost left intact

~$ curl -v http://fusionauth:9011
* Could not resolve host: fusionauth
* Closing connection 0
curl: (6) Could not resolve host: fusionauth

It does look like elasticsearch keeps restarting.

xan

On further inspection, it seems that elasticsearch is using alot of cpu

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  17770 ubuntu    20   0 3143044 907224 181732 S 168.3  45.4   0:18.27 /usr/share/elasticsearch/jdk/bin/java -Xshare:auto -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.ne

dan

How much memory are you giving to the java process?

You can also switch to the database search engine and see if removing ES resolves the issue. At that point it might be a resource issue.

https://fusionauth.io/docs/v1/tech/tutorials/switch-search-engines/ has instructions on how to change these.