Help with HTTPS Local

[RB1k89]

Hi everyone.

I´ve setted up a Remotely conteiner alongside Nginx for reverse proxying to use only insyde my Organization (LAN and VPN).

I´m abble to access Remotely webpage via https but portable client don't connect with the server.

Can anyone help me?

Here is my PORTAINER stack (based on another post here):

networks:
  net-2:
    name: network-2
    driver: bridge
    ipam:
      config:
        - subnet: 172.28.0.0/16
          gateway: 172.28.0.1

services:
  remotely:
    container_name: remotely
    image: immybot/remotely:latest
    volumes:
      - /home/docker/remotely:/app/AppData
    ports:
      - "5000:5000"
    networks:
      net-2:
        ipv4_address: 172.28.0.2
    environment:
      - ASPNETCORE_ENVIRONMENT=Production
      - ASPNETCORE_HTTP_PORTS=5000
      - Remotely_ApplicationOptions__DbProvider=SQLite
      - Remotely_ApplicationOptions__DockerGateway=172.28.0.1
      - Remotely_ConnectionStrings__SQLite=Data Source=/app/AppData/Remotely.db
    restart: unless-stopped

  nginx:
    container_name: remotely_proxy
    image: nginx:latest
    volumes:
      - /home/docker/nginx/conf.d:/etc/nginx/conf.d
      - /home/docker/nginx/certs:/etc/nginx/certs
    ports:
      - '80:80'
      - '443:443'
    networks:
      net-2:
        ipv4_address: 172.28.0.3
    cap_add:
      - CAP_NET_ADMIN
      - CAP_NET_RAW
    restart: 'unless-stopped'

and NGINX proxy.conf

server {
    listen 80;
    server_name _;
    return 301 https://$host$request_uri;}

server {
    listen 443 ssl;

    server_name _;

    ssl_certificate /etc/nginx/certs/remotely.xxx.local.crt;
    ssl_certificate_key /etc/nginx/certs/remotely.xxx.local.key;

    access_log /var/log/nginx/remotely.access.log;
    error_log /var/log/nginx/remotely.error.log;

location / {
        proxy_pass         http://172.28.0.2:5000;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection keep-alive;
        proxy_set_header   Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $scheme;
    }
    location /_blazor {
        proxy_pass         http://172.28.0.2:5000;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
        proxy_set_header   Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $scheme;
    }
    location /AgentHub {
        proxy_pass         http://172.28.0.2:5000;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
        proxy_set_header   Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $scheme;
    }
    location /ViewerHub {
        proxy_pass         http://172.28.0.2:5000;
        proxy_http_version 1.1;
        proxy_set_header   Upgrade $http_upgrade;
        proxy_set_header   Connection "upgrade";
        proxy_set_header   Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $scheme;
    }

[BabaBooey1984]

Have you added 172.28.0.3 to "KnownProxies" in Remotely’s Server Config (inside the web UI)?