-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Returns 500 301 #43
Comments
Hello @Ivan-Igorevich, please specify some more information, as we cannot reproduce the described issue on our side:
|
Of course you cannot, cos you have the Internet connection))) here's my root@node:/home/srv/docker/docker-onlyoffice-nextcloud# uname -a
Linux node 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux
root@node:/home/srv/docker/docker-onlyoffice-nextcloud# cat docker-compose.yml
version: '3'
services:
app:
container_name: app-server
image: nextcloud:fpm
stdin_open: true
tty: true
restart: always
expose:
- '80'
- '9000'
volumes:
- ./app_data:/var/www/html
onlyoffice-document-server:
container_name: onlyoffice-document-server
image: onlyoffice/documentserver:latest
stdin_open: true
tty: true
restart: always
expose:
- '80'
- '443'
volumes:
- ./document_data:/var/www/onlyoffice/Data
- ./document_log:/var/log/onlyoffice
nginx:
container_name: nginx-server
image: nginx
stdin_open: true
tty: true
restart: always
ports:
- 8880:80
- 2443:443
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf
- ./app_data:/var/www/html
volumes:
mysql_data:
root@node:/home/srv/docker/docker-onlyoffice-nextcloud# Folders were ported to host, cos they were ported to host and filled with files on an online machine. My guess is that these files were not enough, and container still wants to get something from the Internet |
here's what i found in my
|
Hello, i installed this repository on my pc with internet connection enabled, almost everything went fine (except it refused to connect to my
pg database
), savedimages
andapp_data
, transferred 'em to a close network server, loaded images, and ported volumes to a server directories (with contents, copied earlier). As idocker-compose up -d
this repo, it turns up and running, but as i enter the homepage in browser, it returns aninternal server error
. i can see500 301
innginx
log and just500
inapp_server
log. Can i use some help, solving this one?The text was updated successfully, but these errors were encountered: