Running Debian12 latest, portainer latest, seafile latest
Need help
how to access seafile?
how to check and/or adjust ports for seafile, this is not in .env?
not using caddy can I activate letsencrypt , this is not in .env?
Sequence:
added port forwarding for 80 and 443 for my local IP 192.168.2.100
DynDNS is properly connected
Installed seafile on a separate partition.
Deployed the seafile-server.yml using my adjusted .env. (see .env below) Seems all is OK, in portainer all 3 container created for seafile on green but cannot access seafile.
Tried http/https local ip:80/8000/443 also dyndns address → nothing!
Checked seafile gui and tried re-installation → says already here
Checked folders created by seafile → looks perfect
OK, system restart → portainer shows the 3 container on red
started container in portainer manuelly → no problem all green
When I check the log in Portainer, what shows me if properly running or not, any specific message you are interested in?
I don’t use any proxy nor Nginx, wouldn’t really know how to use such tools.
So you mean I should use a different port for 80 in the compose file, and edit and deploy the stack again?
When using 8900 should that also added in my router for port forwarding?
I selected https in the .env will that change the way I need to access?
Can I and how add something for let’s encrypt in the compose file cause used https in .env?
Thanks
Yes is there, but why I removed it from .env cause I thought don´t need this - and I have no glue how to use.
Is it running, how to check and does it need any further activity from myside?
OK this is the conf
OK log looks good but what is that beast doing
I deleted caddy entries from .env. but is there, right.
Also nginx is created. Is that all necessary? I don´t know how to handle that:
What confuses me I can see in the log:
port of seafile fileserver: 8082
port of seahub: 8000
I selected https in the .env so I expected 443, right?
This the portainer log for the seafile container:
ccnet database: ccnet_db
seafile database: seafile_db
seahub database: seahub_db
database user: seafile
Generating seafile configuration ...
done
Generating seahub configuration ...
----------------------------------------
Now creating seafevents database tables ...
----------------------------------------
----------------------------------------
Now creating ccnet database tables ...
----------------------------------------
----------------------------------------
Now creating seafile database tables ...
----------------------------------------
----------------------------------------
Now creating seahub database tables ...
----------------------------------------
creating seafile-server-latest symbolic link ... done
-----------------------------------------------------------------
Your seafile server configuration has been finished successfully.
-----------------------------------------------------------------
run seafile server: ./seafile.sh { start | stop | restart }
run seahub server: ./seahub.sh { start <port> | stop | restart <port> }
-----------------------------------------------------------------
If you are behind a firewall, remember to allow input/output of these tcp ports:
-----------------------------------------------------------------
port of seafile fileserver: 8082
port of seahub: 8000
When problems occur, Refer to
https://download.seafile.com/published/seafile-manual/home.md
for information.
[2025-03-18 19:06:42] Updating version stamp
Starting seafile server, please wait ...
Seafile server started
Done.
Starting seahub at port 8000 ...
----------------------------------------
Successfully created seafile admin
----------------------------------------
Seahub is started
Done.
*** Shutting down /scripts/enterpoint.sh (PID 17)...
*** Shutting down runit daemon (PID 16)...
*** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/01_create_data_links.sh...
*** Booting runit daemon...
*** Runit started as PID 21
*** Running /scripts/enterpoint.sh...
2025-03-18 20:21:42 Nginx ready
2025-03-18 20:21:42 This is an idle script (infinite loop) to keep container running.
[2025-03-18 20:21:53] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.
Starting seafile server, please wait ...
Seafile server started
Done.
Starting seahub at port 8000 ...
Seahub is started
Done.
Cause I see seehub on port 8000 i have added this to my port forwarding.
Trying to reach it localy myIP:8000 I am getting “not found”
When I try to reach it with mydyndns:8000 I am getting the answer
and when scrolling through the nginc.conf I can see two entries with 8080, this is already used by my openhab installation.
Is this NGinx running or just a file created in case I would use it?
location /seafdav/ {
proxy_pass http://127.0.0.1:8080/seafdav/;
location /:dir_browser {
# Logo of WebDAV
proxy_pass http://127.0.0.1:8080/:dir_browser;
Trouble again!
After changing the port settings I redeployed seafile
I am selecting “latest” so it took 12.0.11 (before 12.0.10)
I don´t want reverse proxy neither caddy nor nginx.
Please how to change the setup to get rid of these?
After restart of router and seafile server my access is gone!
It looks like my network is messed up.
I only port forwarded 8020 what i am also using in the compose file (8020:80)
When starting openhab remote - Nothing!
When starting wireguard on my mobile - No access to internet!
This is nothing I really need!
Quite sure this nginx, I don´t want that peace of trouble at all, can I remove that - I don´t understand so I don´t want that.
When trying to access seafile via my DynDns:
I am getting a message “502 Bad gateway - Nginx”
When trying to reach locally:
This site can’t provide a secure connection
192.168.2.100 sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
Seafile container log:
waiting for mysql server to be ready: mysql is not ready
Now stopped the containers, deleted all, changed 8020:80 to 8099:80
adjusted router port forwarding
created all from scratch
deployed running all green
mysql server is now running as well but
Would use a nginx proxy manager docker container with simple docker compose. This will allow you to use ssl certificates for your DynDNS. If not, you are sending your passwords unencrypted over the Internet, which you certainly don’t want.
NGINX Proxy Manager
You can find docker compose here:
When applied is the 8099:80 port assignment in the seafile-compose still be required?
No need to change something for “Quick Setup”?
In Details: You are describing Scheme: http and 80 or 8099
Is this for the router port forwarding, or is this for Nginx manager?
To mention: I did choose https in the .env is this contradicting?
I realized ports 80 and 443 are somehow open for my Telekom router by default (SpeedportSmart3) do I still need to forward?
Yes, same network all running on my ThinClient but what do you mean with seafile:80 where to use?
SSL and Advanced is that what I need to check/change in the Nginx manager?
Do I still need to portforward 443, when this seems to be open by default, or is this specifically 443 to my local IP?
Is that Nginx, Letsencrypt, seafile setup somehow impacting the rest of my network?
Asking cause I realized that I suddenly cannot access my Openhab remotely anymore. OH is also running on the same machine. Openhab locally is using port 8080 but I don´t know what the Android Openhab app is using.
Error message is like check the SSL certificate and assure that the server is using basic authentification … therefore I think this is something with that Nginx on that machine, right?
Also trouble with my Wireguard connection served on the Telekom router, I cannot access local network when activating Wireguard on my mobile phone to my Router anymore!
One thing remains, what with that Nginx folder and conf created by seafile setup, ignore?