Closed Peter-Ries closed 1 month ago
Hi, this is indeed confusing. Just tried your config and it works fine.
What I can think of is an aggressive https redirection from your browser, shouldn't be the default though (at least for what I can see on Firefox and Chromium), but maybe you have some extension like https everywhere that could interfere?
Then come the stupid questions, but is the server reachable (I guess it should since you've probably opened a ssh connection)? Any firewall or something? Sorry but I can't help much more, everything seems absolutely normal to me...
Thanks for your reply. I just tried directly from the box with "lxny http://localhost:80"... No luck, no log. If at least some log would tell me what's happening...
It's a fresh instal of Armbian (debian bookwork) firewall is not in place.
If I find a solution I'll post it here.
Hi, thanks for your scripts. I could so start off to test-run seafile in my LAN on my old BananaPi.
I followed your instructions carefully and made changes to .env and seafile.noswag.conf as mentioned here: https://github.com/ChatDeBlofeld/seafile-arm-docker/issues/11#issuecomment-1416703040
Starting up the container gives me no errors, no logs, but my browser calling http://192.168.178.10 times out after minutes...
.env is
and seafile.noswag.conf starts with this
starting docker without -d to see anything at all returns this:
seafile.log has kind of these entries:
docker stats show reverse_proxy_1 and seafile_1 running
I'm clueless where to start analyzing without errors or logs. Do you have any ideas?
Thx!!