Then I add seafile to my Nginx Proxy Manager as subfolder in custom locations:
http 127.0.0.1 8090
Next I search in Seafile configuration to add base url /seafile but cannot find that option.
I set in Admin settings>settings SERVICE_URL: ........net/seafile/ FILE_SERVER_ROOT: .....myserver.......net/seafile/seafhttp
There’s no other option that I can use for base url.
I search in docker-compose folder and find nginx directory: ~/seafile-server/data/app/nginx/conf/seafile.nginx.conf
I checked docker-compose logs and I see there’s also some nginx sevice starting, meybe I need to make changes in ~/seafile-server/data/app/nginx/conf/seafile.nginx.conf?
I see there lines:
I wanted to just mention something, when you have an nginx proxy running in docker and it needs to communicate with another container, it’s communicating in parallel. This means your proxy_pass is going to be the internal port - which if you used 8090:80 in docker compose that’s port 80 or just the IP of the seafile docker container such as:
Now, of course, the nginx and seafile containers have their own IP addresses outside the local host. Docker containers generally get ips in the 172.17. 0.0/16 address space, but of course these could be manually assigned.
You can dig a little deeper into getting the ips of your containers.
One example - my own setup:
docker-compose.yml of seafile uses ports 8090:80
Ubuntu Server running docker IP: 192.168.1.100
Inside docker, two containers:
Nginx: 10.0.0.100
Seafile: 10.0.0.101
The proxy_pass in my nginx server looks like this:
proxy_pass http://10.0.0.101/;
Thanks for answer @kevinc , Can You tell me that proxy_pass I need to set in seafile.nginx.conf? What about that ports:
location / {
proxy_pass http://127.0.0.1:8000/;
location /seafhttp {
rewrite ^/seafhttp(.*)$ $1 break;
proxy_pass http://127.0.0.1:8082;
location /seafdav {
proxy_pass http://127.0.0.1:8080;
I have Nginx Proxy Manager set in host mode:
version: ‘3’
services:
nginx-proxy-manager:
image: jlesage/nginx-proxy-manager
restart: unless-stopped
network_mode: host
volumes:
- “/home/dietpi/.config/nginx-proxy-manager:/config:rw”
I see in Portainer I have IPs for Seafile:
Seafile = 172.21.0.4
Seafile-mysql = 172.21.0.2
Seafile-memcached = 172.21.0.3
Can You help me with that becaouse I really don’t understand docker and nginx?
Regards.
Alright, I’ll do what I can… but please tell me more about your setup. Can you tell me what base os you’re using? Also, the seafile.nginx.conf - where did you get that conf file? Was it a template? When you terminal into the seafile (172.21.0.4) container can you ping the nginx container (whatever that IP is) and vice versa?
Also, just share your docker-compose (maybe on pastebin) for seafile and seafile.nginx.conf files (redact personal or sensitive info) and I’ll take a look.
I post my Seafile docker-compose and seafile.nginx.conf in my first post. That seafile.nginx.conf I find in dietpi@DietPi:~/seafile-server/data/app/nginx/conf/seafile.nginx.conf. I never use any nginx conf file. I use Nginx Proxy Manager and add apps as subfolders. Then just set in apps base url and that just works.
I use DietpiOS (debian 11) on HP intel miniPC, kernel 5.10 x86_64.
I don’t know how to ping that Nginx Proxy Manager because I don’t see any IP with docker ps or in Pointainer
dietpi@DietPi:~/seafile-server/data/app/nginx/conf$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
93142aabc162 mariadb:latest "docker-entrypoint.s…" 2 hours ago Up 2 hours 3306/tcp seafile-mysql
8bf08ecc0ffb seafileltd/seafile-mc "/sbin/my_init -- /s…" 16 hours ago Up 16 hours 0.0.0.0:8090->80/tcp, :::8090->80/tcp seafile
1b58e86d9298 memcached "memcached -m 256" 16 hours ago Up 16 hours 11211/tcp seafile-memcached
fbb37b6c6c1a koenkk/zigbee2mqtt:latest "docker-entrypoint.s…" 2 days ago Up 2 days 0.0.0.0:8081->8080/tcp, 0.0.0.0:9999->8080/tcp, :::8081->8080/tcp, :::9999->8080/tcp zigbee2mqtt
0022ef2e1e7b lscr.io/linuxserver/wireguard "/init" 3 days ago Up 2 days 0.0.0.0:51820->51820/udp, :::51820->51820/udp wireguard
62569b171261 jlesage/nginx-proxy-manager:latest "/init" 9 days ago Up 2 days npm_nginx-proxy-manager_1
145c06ce4b4f eclipse-mosquitto:2.0 "/docker-entrypoint.…" 3 weeks ago Up 2 days 0.0.0.0:1883->1883/tcp, :::1883->1883/tcp, 0.0.0.0:9001->9001/tcp, :::9001->9001/tcp dietpi_mqtt_1
d6bb53ee93e7 portainer/portainer-ce "/portainer -H unix:…" 3 weeks ago Up 2 days 8000/tcp, 9443/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp portainer
2492862a0f7d hrfee/jfa-go "/opt/jfa-go/jfa-go …" 4 weeks ago Up 2 days 0.0.0.0:8056->8056/tcp, :::8056->8056/tcp, 8057/tcp jfago
ec78fe2025e1 containrrr/watchtower "/watchtower" 4 weeks ago Up 2 days 8080/tcp watchtower
dietpi@DietPi:~/seafile-server/data/app/nginx/conf$
Ok, yea… thanks… I should have checked your first post… busy day for me.
But, let’s just do something basic, get into the terminal of your nginx container (use a command like this) - the /bin/sh might need to be /bin/bash: docker exec -it -u root npm_nginx-proxy-manager_1 /bin/sh
Once in that terminal, do these things to make sure nginx can see seafile:
Ping all the other containers: Seafile = 172.21.0.4, Seafile-mysql = 172.21.0.2, Seafile-memcached = 172.21.0.3 - does that succeed?
Determine where web interfaces might be and see if you can get any data, such as the seafile hub: curl -Is http://172.21.0.4 | head -n 1
This an example, something is there, there will be no response if nothing:
Doing those things might show some things that might be going on, give them a try and let me know and I’ll look at your files in a bit.