When Installing nextcloud+onlyoffice, onlyoffice failed to start and report an error:
enter the container to see the error information of out.log
[[email protected] ~]# docker ps -a
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a7c97fb93556 docker.io/onlyoffice/documentserver:latest 30 hours ago Up 30 hours ago 0.0.0.0:8080->80/tcp, 0.0.0.0:9000->443/tcp onlyoffice
[[email protected] ~]# docker exec -it a7c97fb93556 /bin/bash
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[email protected]:/# cd /var/log/onlyoffice/documentserver/converter/
[email protected]:/var/log/onlyoffice/documentserver/converter# ls
err.log out.log-20220729
[email protected]:/var/log/onlyoffice/documentserver/converter#
Disabling Document Server Access Authentication
Next, disable access authentication for Document Server, which by default rejects unauthenticated requests (i.e., self-signed HTTPS requests).
I am now running Document Server with Docker, using the docker exec command to log into the container.
There seems to be only the nano editor in the container, but that’s enough.
Open /etc/onlyoffice/documentserver/default.json, go down and find the rejectUnauthorized field and change its value to false.
Restart the container.
Modify default.json
[email protected]:/var/log/onlyoffice/documentserver/converter# cd /etc/onlyoffice/
[email protected]:/etc/onlyoffice# ls
documentserver documentserver-example
[email protected]:/etc/onlyoffice# cd documentserver
[email protected]:/etc/onlyoffice/documentserver# ls
default.json local.json production-linux.json
development-linux.json log4js production-windows.json
development-mac.json logrotate supervisor
development-windows.json nginx
[email protected]:/etc/onlyoffice/documentserver# pwd
/etc/onlyoffice/documentserver
[email protected]:/etc/onlyoffice/documentserver#
Modify as follows: “rejectunauthorized”: false
"requestDefaults": {
"headers": {
"User-Agent": "Node.js/6.13",
"Connection": "Keep-Alive"
},
"gzip": true,
"rejectUnauthorized": false
},
Restart container
[email protected]:/etc/onlyoffice/documentserver# exit
exit
[[email protected] ~]# docker stop a7c97fb93556
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: given PIDs did not die within timeout
[[email protected] ~]# docker start a7c97fb93556
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: unable to start container "a7c97fb93556650c83dd763f9578705a82f34b2673f9759e8d0ce62afc63e77c": container a7c97fb93556650c83dd763f9578705a82f34b2673f9759e8d0ce62afc63e77c must be in Created or Stopped state to be started: container state improper
[[email protected] ~]# reboot
Restart nextcloud
login as: root
[email protected]'s password:
Activate the web console with: systemctl enable --now cockpit.socket
Last login: Fri Jul 29 15:59:59 2022 from 192.168.182.1
[[email protected] ~]# setenforce 0
[[email protected] ~]# systemctl start https
Failed to start https.service: Unit https.service not found.
[[email protected] ~]# systemctl start httpd
Enter TLS private key passphrase for localhost:443 (RSA) : ******
[[email protected] ~]# docker ps -a
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a7c97fb93556 docker.io/onlyoffice/documentserver:latest 31 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:9000->443/tcp onlyoffice
[[email protected] ~]# docker start a7c97fb93556
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
a7c97fb93556
[ro[email protected] ~]#
Start onlyoffice
run as prompted
[[email protected] ~]# sudo docker exec a7c97fb93556 sudo supervisorctl start ds:example
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
sudo: unable to send audit message: Operation not permitted
ds:example: started
Successfully opened word document
Read More:
- Docker starts MySQL container and reports an error driver failed programming external connectivity on endpoint mysq
- When docker creates a container command: Error response from daemon: No command specified
- Common command of docker
- Error: path not specified when the docker 1.7 file is uploaded to the container in CentOS
- Vscode configuration connection server docker write code
- Fedora32 start container error – OCI runtime create failed: This version of runc doesn’t work on cgroups V2: unknown
- ERROR: Rancher must be ran with the –privileged flag when running outside of Kubernetes
- Error response from daemon for private harbor login
- [Sovled] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
- Job for docker.service failed because the control process exited with error code. See systemctl sta
- Error response from daemon: Conflict: unable to delete 8598c91556dc (must be forced)
- Error during connect when installing docker in Windows 10
- Docker creation container cannot find network card: error response from daemon: network XXXX not found
- systemctl start docker Job for docker.service failed because the control process exited with error
- Centos7 quick installation of docker and configuration of image acceleration
- An error occurred trying to connect: get http: / / var / run/ docker.sock/v1 .21/containers/json?all
- [Win 10] Docker Error: error during connect: In the default daemon configuration on Windows
- linux docker Error Failed to get D-Bus connection: Operation not permitted
- Docke Run: response from daemon: OCI runtime create failed: container with id exists:XXX:unknown
- Docker CentOS Failed to get D-Bus connection: Operation not permitted