Reverse Proxy HTTPS

[Inaciomcr]

Hi,

I am trying to access my seafile server from https but i'm stuck.

I added the following line to the docker-compose.yml seafile server file:

  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./nginx-data/conf.d:/etc/nginx/conf.d
      - ./nginx-data/certs:/etc/nginx/certs
      - ./nginx-data/vhost.d:/etc/nginx/vhost.d
      - ./nginx-data/html:/usr/share/nginx/html
      - /var/run/docker.sock:/tmp/docker.sock:ro

  nginx-letsencrypt:
    image: jrcs/letsencrypt-nginx-proxy-companion
    container_name: nginx-letsencrypt
    restart: always
    volumes_from:
      - nginx-proxy
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - [email protected]
      - NGINX_PROXY_CONTAINER=nginx-proxy

my caddy config is:

 seafile-caddy:
    image: ggogel/seafile-caddy:1.0.6
#    ports:
#      - "80:80" # Point your reverse proxy to port 80 of this service
    expose:
    - "80"
    networks:
      - seafile-net
      - default
    environment:
    - VIRTUAL_PORT=80
    - VIRTUAL_HOST=site.com,192.168.0.101

I can access the server using http but when I try to access ussing https I receive the error :

500 Internal Server Error

Can you help me? I want to allow only https connection.

[ggogel]

Hi, you cannot specify an IP address in the VIRTUAL_HOST parameter. A reverse proxy works with HTTP/HTTPS, meaning OSI Layer 7 (Application). IP is situated in OSI Layer 3 (Network). In this layer, we use routers to "change the direction" of traffic. So try to remove the IP address and see if it works.

[Inaciomcr]

Hi,

I added the server local IP address to the VIRTUAL_HOST to be able to connect to Seahub through the local network.

I followed the example that you provided here and successfully accessed the Seahub from internet but cannot access it directly from the local network.

[ggogel]

Then this is a DNS problem. Run nslookup to see if your local DNS has an entry for your seafile domain.

[ggogel]

Also, your modem/router might have a safety feature called DNS rebind protection preventing this.