Android app - "[fqdn] does not seem to be a Pydio server." when ran behind an nginx reverse proxy

Hi!

I installed Pydio Cells through docker on a server running Debian.
As I am accessing this server through Tailscale, I am using nginx to reverse proxy it so that I can use the Tailscale cert for HTTPS. This works without error when accessing the web app, with nginx redirecting to where Pydio is on port 8080 making it accessible from just the tailnet’s URL.

However, where this is not working is on the Android app. When I enter the FQDN of the server to log in on the Android app, I am met with the error mentioned in this post’s title.
My nginx config is the following:

server {
    listen 443 ssl;
    ssl_certificate /opt/seafile/[fqdn].ts.net.crt;    # Path to your fullchain.pem
    ssl_certificate_key /opt/seafile/[fqdn].ts.net.key;  # Path to your privkey.pem
    server_name [fqdn].ts.net;
    server_tokens off;

    location / {
        proxy_pass         https://127.0.0.1:8080;
        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-Host $server_name;
        proxy_read_timeout 1200s;

        proxy_set_header   X-Forwarded-Proto https;
    }
}

I have also noticed that changing the location from / to /pydio causes it to become stuck on the pydio logo with “Loading…” text.

Is my nginx configuration wrong? Am I approaching this the wrong way? I would love to hear what best to do.
Thanks a million!

Nevermid, I had completely missed the config specified at Running Cells behind a Nginx reverse proxy | Pydio.

Using it and tweaking the URL and certs to match those of my tailnet, it now works fine!
Only weird thing is that the Android app will try to access localhost:8080 where the fqdn resolves to for oauth, so I had to change the URL in the browser.

For the Android issue, you have to configure the external URL using cells configure sites (with the pydio user or any user that runs the app) on the server.

This topic was automatically closed 11 days after the last reply. New replies are no longer allowed.