Ghost in the machine

Seafile Server
1

I have installed Seafile CE 12 on a fresh machine with Armbian, using Docker. Everything worked perfect … for a while.
The installation was done according to this page: Setup community edition - Seafile Admin Manual

I wish to use port 80 for other content, so I let my router forward external 8000 to local 80. After doing this, uploads and downloads gives “network error”. Everything else works as expected as far as I can see.

I can not understand why this happens, and I did not find any errors in any logs.
Any explanations?

As a work-around I wish to change port in caddy.yml. I asume
ports:
- 8000:80
should be correct.
But what then? Is it just to run ```
docker compose up -d ?

Thanks

2

Hello!

I could be wrong, but if you’ve already set the router to forward from 8000 (incoming router) to 80 (incoming Seafile server), I don’t think you’d want to change your caddy.yml. If you wanted to use port 80 for other things, do you mean router port 80 incoming? Or Seafile server port 80 incoming? If router, then you’d just need to add :8000 to your browser URL.

I’m not 100% sure that would work though; perhaps try that and see?

3

Sorry for being unclear.
I wish to use the external port 80 to be directed to another machine, running a website.

I did the following attempts:
ports:

  • 80:80
    Set external port 8000 to internal 80 on the Seafile machine.
    Seafile site worked good, except upload and download.

Made the change
ports:

  • 8000:80
    in caddy.yml
    docker compose down
    docker compose up -d
    Set external port 8000 to internal 8000 on the Seafile machine.
    Seafile site worked good, except upload. I did not try download.
    Even tried to reboot the server.

When it runs on 80 all the way, everything works good.

4

Hello!

I still don’t have much of an idea what is happening, but next I would say let’s check your browser’s Developer mode. In other words, login to Seafile site, open up Developer mode, then try to do the upload. It will fail with Network error, but the Developer console in the browser there may give us a clue.

Also, if I am thinking of the same thing, I may have run into this exact issue, and I ended up leaving Caddy at 80:80 but set up another reverse proxy out front for HTTPS certificate termination. After a request comes in on 443, I remapped the request & ensured that my reverse proxy passed both HTTP and WebSocket traffic. After that the issue went away.

5

Hello! Looks like another user may have had a similar issue? Check this out: