Workspace installed succesfully but nothing when going to ip address of host

mefisto74 · 5 July 2024 12:35

hello. i succesfully installed onlyoffice workspace using docker. according to docs i should go to ip address of host to contitnue configuring this product but when i trying this nothing happens, even no nginx errors although service is running

my docker containers : (docker ps output)

sudo docker ps
CONTAINER ID   IMAGE                                    COMMAND                  CREATED       STATUS       PORTS                                                                                                                                                                                  NAMES
c6a9844c29ef   onlyoffice/communityserver:12.6.0.1900   "/app/run-community-…"   2 hours ago   Up 2 hours   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 9888/tcp   onlyoffice-community-server
22c56bce42de   onlyoffice/controlpanel:3.5.2.530        "/var/www/onlyoffice…"   2 hours ago   Up 2 hours   80/tcp, 443/tcp                                                                                                                                                                        onlyoffice-control-panel
ded042ba54c2   onlyoffice/documentserver:8.1.0.1        "/app/ds/run-documen…"   2 hours ago   Up 2 hours   80/tcp, 443/tcp                                                                                                                                                                        onlyoffice-document-server
8c7fe1f48841   onlyoffice/elasticsearch:7.16.3          "/bin/tini -- /usr/l…"   2 hours ago   Up 2 hours   9200/tcp, 9300/tcp                                                                                                                                                                     onlyoffice-elasticsearch
50ee8b8baf9b   mysql:8.0.29                             "docker-entrypoint.s…"   2 hours ago   Up 2 hours   3306/tcp, 33060/tcp                                                                                                                                                                    onlyoffice-mysql-server

docker exec -it onlyoffice-community-server service nginx status
showing me that nginx is running

also searched in logs. looks like all started for me although there was some errors

sudo docker logs onlyoffice-community-server output:

Nikolas · 8 July 2024 13:52

Hello @mefisto74

At first glance, the installation appears to have completed successfully.

Could you please share the output of the following command executed on the system where ONLYOFFICE Workspace is installed:

curl http://localhost

Thank you:)

mefisto74 · 8 July 2024 15:03

curl http://localhost
nothing happens when i do this. like timeout

Nikolas · 12 July 2024 10:06

@mefisto74
I suspect that something might be blocking access.

Feel free to share this information via private messages if you prefer not to post it publicly.

Docker Network Configuration

Check Docker Network Settings: Ensure the container is properly attached to the network.
```
docker network inspect onlyoffice
```

Retrieve IPv4 Address: Find the IPv4 address of the onlyoffice-community-server.

docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' onlyoffice-community-server

Test Network Connectivity

From within the Container: Test network connectivity to ensure the web server is responding.
```
docker exec -it c6a9844c29ef    curl http://localhost
```

Check Host and Docker Network

Access from the Host: Verify that the host can access the container’s IP and ports. Replace <container_ip> with the actual IP of the onlyoffice-community-server.
```
curl http://<container_ip>
```

Check Firewall Rules on the Host

Verify Firewall Rules: Ensure that firewall rules on the host are not blocking port 80.
```
sudo iptables -L
sudo ufw status
```

Additional Network Diagnostics

Routes and IP Addresses:
```
route -n
```
Status of Network Interfaces:
```
ifconfig
```

mefisto74 · 24 July 2024 04:09

well for me looks like all ok with network and fo firewalls at all on system, selinux also disabled

docker network inspect onlyoffice

[
{
“Name”: “onlyoffice”,
“Id”: “0fdda53e731dc0a4f30186620e8566ea9ef72f2cf12842828818aa46487ccefd”,
“Created”: “2024-07-03T18:22:27.486886356+05:00”,
“Scope”: “local”,
“Driver”: “bridge”,
“EnableIPv6”: false,
“IPAM”: {
“Driver”: “default”,
“Options”: {},
“Config”: [
{
“Subnet”: “172.18.0.0/16”,
“Gateway”: “172.18.0.1”
}
]
},
“Internal”: false,
“Attachable”: false,
“Ingress”: false,
“ConfigFrom”: {
“Network”: “”
},
“ConfigOnly”: false,
“Containers”: {
“251a878617487fc04fba0f8f99d161b3021f48b55051b8c34ac69a70b57ad5bf”: {
“Name”: “onlyoffice-elasticsearch”,
“EndpointID”: “f1adc12596c7511f97013f3d366f6895c3f29bb2afe078ce953dc4426a86f696”,
“MacAddress”: “02:42:ac:12:00:05”,
“IPv4Address”: “172.18.0.5/16”,
“IPv6Address”: “”
},
“b6e1902997468c35fbf51b896e7d94d47d6774801311a8c2408c27f6b9b10c60”: {
“Name”: “onlyoffice-document-server”,
“EndpointID”: “afa2e1782e84ebd3c7c9608da744a4579b1fd1cb293fb5ff2dca3314255679c4”,
“MacAddress”: “02:42:ac:12:00:03”,
“IPv4Address”: “172.18.0.3/16”,
“IPv6Address”: “”
},
“ba986bc03e2eca1a8a39a0c4345d85d225b8dc095d8957442ef2a6786afa51e4”: {
“Name”: “onlyoffice-community-server”,
“EndpointID”: “a0cc62b72cacb51edaee5955c6327bf059a7eaf61db5ae25c5e95dc82118ad21”,
“MacAddress”: “02:42:ac:12:00:06”,
“IPv4Address”: “172.18.0.6/16”,
“IPv6Address”: “”
},
“c4bcfe6054aea3eb14f51266aa2909fdbaec28379ac3977b6fbb7763e7d091fc”: {
“Name”: “onlyoffice-mysql-server”,
“EndpointID”: “54bf9baa1fc83c69e7a7d80a9d40df264295128def600bfd9fda37602e3fd750”,
“MacAddress”: “02:42:ac:12:00:04”,
“IPv4Address”: “172.18.0.4/16”,
“IPv6Address”: “”
},
“f878ea4f02c2e051c7cd69e2f5d4dc627b32269cb2ed4b2794404167cb9101a8”: {
“Name”: “onlyoffice-control-panel”,
“EndpointID”: “3e92605f1191e03c502c46fc5b022d323dfa57be2e92c59a6a8e872e43625b23”,
“MacAddress”: “02:42:ac:12:00:02”,
“IPv4Address”: “172.18.0.2/16”,
“IPv6Address”: “”
}
},
“Options”: {},
“Labels”: {}
}
]

docker inspect -f ‘{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}’ onlyoffice-community-server

172.18.0.6

3.  docker exec -it onlyoffice-community-server curl http://localhost 
nothing happens. timeouting

4. curl http://172.18.0.6
the same. nothing happens

5. sudo iptables -L


> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> 
> Chain FORWARD (policy DROP)
> target     prot opt source               destination
> DOCKER-USER  all  --  anywhere             anywhere
> DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
> ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
> DOCKER     all  --  anywhere             anywhere
> ACCEPT     all  --  anywhere             anywhere
> ACCEPT     all  --  anywhere             anywhere
> ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
> DOCKER     all  --  anywhere             anywhere
> ACCEPT     all  --  anywhere             anywhere
> ACCEPT     all  --  anywhere             anywhere
> 
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> 
> Chain DOCKER (2 references)
> target     prot opt source               destination
> ACCEPT     tcp  --  anywhere             172.18.0.6           tcp dpt:xmpp-client
> ACCEPT     tcp  --  anywhere             172.18.0.6           tcp dpt:https
> ACCEPT     tcp  --  anywhere             172.18.0.6           tcp dpt:http
> 
> Chain DOCKER-ISOLATION-STAGE-1 (1 references)
> target     prot opt source               destination
> DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
> DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
> RETURN     all  --  anywhere             anywhere
> 
> Chain DOCKER-ISOLATION-STAGE-2 (2 references)
> target     prot opt source               destination
> DROP       all  --  anywhere             anywhere
> DROP       all  --  anywhere             anywhere
> RETURN     all  --  anywhere             anywhere
> 
> Chain DOCKER-USER (1 references)
> target     prot opt source               destination
> RETURN     all  --  anywhere             anywhere


5.1 i dont have ufw at all.

6. route -n

> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 0.0.0.0         192.168.6.254   0.0.0.0         UG    100    0        0 eth0
> 172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
> 172.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-0fdda53e731d
> 192.168.6.0     0.0.0.0         255.255.255.0   U     100    0        0 eth0


7. ip a


> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
>     link/ether 00:15:5d:dc:cd:8b brd ff:ff:ff:ff:ff:ff
>     inet 192.168.6.15/24 brd 192.168.6.255 scope global dynamic noprefixroute eth0
>        valid_lft 689511sec preferred_lft 689511sec
>     inet6 fe80::215:5dff:fedc:cd8b/64 scope link noprefixroute
>        valid_lft forever preferred_lft forever
> 3: br-0fdda53e731d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
>     link/ether 02:42:5c:49:f1:1e brd ff:ff:ff:ff:ff:ff
>     inet 172.18.0.1/16 brd 172.18.255.255 scope global br-0fdda53e731d
>        valid_lft forever preferred_lft forever
>     inet6 fe80::42:5cff:fe49:f11e/64 scope link
>        valid_lft forever preferred_lft forever
> 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
>     link/ether 02:42:da:db:8c:8e brd ff:ff:ff:ff:ff:ff
>     inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
>        valid_lft forever preferred_lft forever
> 6: veth35fbe09@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0fdda53e731d state UP group default
>     link/ether 1e:9c:76:21:55:e4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
>     inet6 fe80::1c9c:76ff:fe21:55e4/64 scope link
>        valid_lft forever preferred_lft forever
> 8: vethed6ae29@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0fdda53e731d state UP group default
>     link/ether 56:35:fd:52:cc:ae brd ff:ff:ff:ff:ff:ff link-netnsid 1
>     inet6 fe80::5435:fdff:fe52:ccae/64 scope link
>        valid_lft forever preferred_lft forever
> 12: vetha830a04@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0fdda53e731d state UP group default
>     link/ether 42:82:df:75:07:42 brd ff:ff:ff:ff:ff:ff link-netnsid 3
>     inet6 fe80::4082:dfff:fe75:742/64 scope link
>        valid_lft forever preferred_lft forever
> 14: veth4729749@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0fdda53e731d state UP group default
>     link/ether 9e:3b:54:d5:82:3a brd ff:ff:ff:ff:ff:ff link-netnsid 4
>     inet6 fe80::9c3b:54ff:fed5:823a/64 scope link
>        valid_lft forever preferred_lft forever
> 18: vethb1504ad@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0fdda53e731d state UP group default
>     link/ether 22:be:05:34:ee:06 brd ff:ff:ff:ff:ff:ff link-netnsid 2
>     inet6 fe80::20be:5ff:fe34:ee06/64 scope link
>        valid_lft forever preferred_lft forever

Nikolas · 7 August 2024 08:49

@mefisto74

Sorry for the late response.
Thank you for the detailed information.

Based on your description, it seems that the network and firewall configurations look correct. However, I’d like to gather a bit more information to better assist you:

Operating System: Could you please specify the OS you are using?
Docker Version: Could you also provide the version of Docker you have installed?

Considering that SELinux is disabled, it indicates you might be using an RPM-based distribution. In such cases, it would be helpful to check if firewalld is active and potentially affecting the connections.

As a potential solution, I recommend the following steps:

Remove the Community Server Container:

docker rm -f onlyoffice-community-server

Update the ONLYOFFICE Workspase :
```
bash workspace-install.sh -u true
```

This will recreate the Community Server container and might resolve the issue.

Please try these steps and let us know if the problem persists. Additionally, any other relevant details, such as modifications to configuration files or the use of a proxy server, would be helpful.

pospos369 · 30 August 2024 07:36

I also encountered the same problem, the investigation is basically the same

Alexandre · 3 September 2024 09:38

Hello,
If you don’t mind I will join this thread as well.
@pospos369 Was the situation resolved or have you encountered an issue?