Opencloud with NPM (Nginx proxy manager)

[philliphs]

I'm trying to set up Opencloud on a standalone VM using docker compose method. My network are behind Nginx Proxy Manager (NPM) on another VM.
I set up NPM to reverse proxy my domain to internal IP and opencloud works. It's just the collabora produced error.

Anyone can point out to me where I did wrong?
Please let me know what reports need to be attached here, I'm a total linux noob.

[Watashi26]

Hey, I'm using the same setup and i don't have this problem. For reference check out my compose file. What settings are you using for your proxy host in NPM? I'm seeing you are using the whole setup with apps unlike me. For this you need to use Trafic, at least as far as I know.

[philliphs]

I think NPM only passing through the opencloud docker server. When I tried to open collabora server and wopiserver it produced 404

[Watashi26]

Hi. Thanks for responding. Yes I'm using a whole setup with apps following the guide https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose/ May I know how did you install your setup?

Sorry I'm a bit confused on where exactly the compose file for the setup according to the guide.

My setup is the compose file I linked in my prevoius post. This setup works, yet only without apps. Additionally i can not sign in into any client, thus my post. Sharing files and via the web app is working though.

[philliphs]

Same as mine. All file sharing and text editor works. Only the collabora part did not work as per screenshot.
I think either the collabora server failed to run or I can't reach the collabora server on my settings

[philliphs]

Finally figure it out. Duh!
Installation wise, just follow https://docs.opencloud.eu/docs/admin/getting-started/container/docker-compose/ exactly.
On NPM, forward https to local IP address on port 443. Then enable web-socket support and collabora works.

[ptC7H12]

@philliphs how did you get all running? It seems youre using the Opencloud/Traefik behind NPM?
I'm getting Certificate errors, even when NPM is saying it has an valid certificate.
Can you post your .env maybe?

[JoaGamo]

For people as dumb as me, simply do this. I run NPM on a different server than OpenCloud. Read the entire documentation, but at the nginx part, do this. Check this @ptC7H12

Using Nginx Proxy Manager, you don't need certificates on the internal OpenCloud server.

On the OpenCloud server, you need nginx listening for external connections, so create a nginx config file without certificate validation, a nginx server listening for HTTP connections instead of HTTPS. Like this

root@opencloud:/etc/nginx/sites-available# cat opencloud

# OpenCloud (oCIS)
server {
    listen 80;
    server_name cloud.YOUR.DOMAIN;

    access_log /var/log/nginx/ocis-access.log;
    error_log /var/log/nginx/ocis-error.log;

    # Increase max upload size 
    client_max_body_size 10M;
    

    proxy_buffering off;
    proxy_request_buffering off;


    proxy_read_timeout 3600s;
    proxy_send_timeout 3600s;

    keepalive_requests 100000;
    keepalive_timeout 5m;
    http2_max_concurrent_streams 512;

    proxy_next_upstream off;

    location / {
        proxy_pass http://127.0.0.1:9200;
        
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }
}

# Collabora
server {
    listen 80;
    server_name collabora.YOUR.DOMAIN;


    client_max_body_size 10M; 


    location / {
        proxy_pass http://127.0.0.1:9980;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }

    # Websockets Collabora
    location ~ ^/cool/(.*)/ws$ {
        proxy_pass http://127.0.0.1:9980;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto https;
    }
}

# WOPI Server
server {
    listen 80;
    server_name wopiserver.YOUR.DOMAIN;

    location / {
        proxy_pass http://127.0.0.1:9300;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
    }
}

Don't forget to enable the nginx configuration with sudo ln -s /etc/nginx/sites-available/opencloud /etc/nginx/sites-enabled/ and
sudo nginx -t && sudo systemctl reload nginx

Of course if you are not checking for certificates, your .env file should have INSECURE=true

Last point, on Nginx Proxy Manager, now that your OpenCloud server has a nginx server inside of it listening for incoming connections and forwarding them internally, you need your Nginx Proxy Manager to listen on YOUR.DOMAIN for port 80 for all of them. create 3 proxies like this

http | opencloud.local | cloud.YOUR.DOMAIN | port=80
http | opencloud.local | collabora.YOUR.DOMAIN | port=80
http | opencloud.local | wopiserver.YOUR.DOMAIN | port=80
(replace "opencloud.local" with your opencloud server's IP or domain-name)

for the Collabora proxy, enable websockets support. You technically could create a single reverse proxy housing 3 different external domains pointing to a local domain, but I prefer to create multiple proxies for clarity with 1:1 mappings.

You should be done after this, and your server will be accessible on cloud.YOUR.DOMAIN :)