TheRouce
commented
7 months ago It's working now, turns out it was an nginx issue, which I probably should have expected, here's the working ocis config I ended up with:
server {
ssl_stapling on;
ssl_stapling_verify on;
server_name cloud.domain.tld;
listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/cloud.domain.tld/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/cloud.domain.tld/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
location / {
#proxy_buffers 4 256k;
#proxy_buffer_size 128k;
#proxy_busy_buffers_size 256k;
proxy_request_buffering off;
proxy_buffering off;
proxy_http_version 1.1;
client_max_body_size 0;
proxy_pass https://localhost:9200;
#proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}
}
server {
if ($host = cloud.domain.tld) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80;
listen [::]:80;
server_name cloud.domain.tld;
return 404; # managed by Certbot
}I mostly just combined the config file from the bare metal docs on doc.owncloud.com with the config file from the tusd github
Describe the bug
TUS 404 after configuring onlyoffice
Steps to reproduce
Expected behavior
Upload through TUS passing properly
Actual behavior
After setting up onlyoffice web editor I get a new error:
Setup
OCIS .env file and nginx config file
```console OCIS_INSECURE=false PROXY_HTTP_ADDR=0.0.0.0:9200 OCIS_LOG_PRETTY=true OCIS_LOG_COLOR=true OCIS_LOG_LEVEL=warn NATS_NATS_HOST=0.0.0.0 NATS_NATS_PORT=9233 OCIS_URL=https://cloud.domain.tld OCIS_CONFIG_DIR=/etc/ocis OCIS_BASE_DATA_PATH=/var/lib/ocis SEARCH_EXTRACTOR_TYPE=tika SEARCH_EXTRACTOR_TIKA_TIKA_URL=http://tika:9998 FRONTEND_FULL_TEXT_SEARCH_ENABLED=true MICRO_REGISTRY_ADDRESS=0.0.0.0:9233 GATEWAY_GRPC_ADDR=0.0.0.0:9142 WOPISERVER_DOCKER_TAG=v10.3.0 WOPI_JWT_SECRET="secret" WOPISERVER_INSECURE=false WOPISECRET="secret" ONLYOFFICE_DOMAIN=onlyoffice.cloud.domain.tld APP_PROVIDER_WOPI_APP_ICON_URI=https://onlyoffice.cloud.domain.tld/web-apps/apps/documenteditor/main/resources/img/favicon.ico APP_PROVIDER_WOPI_APP_URL=https://onlyoffice.cloud.domain.tld APP_PROVIDER_WOPI_FOLDER_URL_BASE_URL=https://cloud.domain.tld APP_PROVIDER_WOPI_WOPI_SERVER_EXTERNAL_URL=https://wopi.cloud.domain.tld ```
```console server { client_max_body_size 2000M; server_name cloud.domain.tld; location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Host $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass https://localhost:9200; proxy_buffers 16 4k; proxy_buffer_size 2k; } error_page 500 502 503 504 /error_code.html; location /error_code.html { root /etc/nginx/error_pages; internal; } location /.well-known/carddav { return 301 $scheme://$host/remote.php/dav; } location /.well-known/caldav { return 301 $scheme://$host/remote.php/dav; } listen [::]:443 ssl http2; listen 443 ssl http2; ssl_certificate /etc/letsencrypt/live/cloud.domain.tld/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/cloud.domain.tld/privkey.pem; include /etc/letsencrypt/options-ssl-nginx.conf; ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; } server { if ($host = cloud.domain.tld) { return 301 https://$host$request_uri; } server_name cloud.domain.tld; listen [::]:80; listen 80; return 404; } ```
OCIS docker log:
Additional context
I am almost 100% sure this is user error, I am running an OCIS instance just to test how it works and maybe move it to a production server in the future. I would love feedback on anything I did wrong or anything I'm missing.
EDIT When I get a chance to restart the server I'll enable debug log level