Blocked on Proxy #16

New Issue

2024-05-23T22:17:31-04:00

Korbs commented

2024-05-23 22:17:31 -04:00

When 4get is on my NGINX proxy(NGINX Proxy Manager), I get a blocked error. This works fine in the local IP.

The Docker Compose file is setup like this via Dockge:

services:
  fourget:
    image: quay.io/sudovanilla/4get-arm64:latest
    restart: always
    ports:
      - 5901:80
    environment:
      - FOURGET_VERSION=6
      - FOURGET_SERVER_NAME=4get.sudovanilla.org
      - FOURGET_PROTO=http
    volumes:
      - /sudovanilla/docker/volumes/4get/banners:/var/www/html/4get/banner
      - /sudovanilla/docker/volumes/4get/certs:/etc/4get/certs
      - /sudovanilla/docker/volumes/4get/captcha:/var/www/html/4get/data/captcha
networks:
  dockge_default:
    external: true

Docker Image is up to date as of May 23rd, 2024.

NGINX Proxy Manager generated:

# ------------------------------------------------------------
# 4get.sudovanilla.org
# ------------------------------------------------------------
  map $scheme $hsts_header {
    https   "max-age=63072000; preload";
  }

server {
    set $forward_scheme http;
    set $server         "192.168.1.175";
    set $port           6258;

  # Error Page
  error_page 404 /404.html;
  location /404.html {
        root /errors/;
  }

  error_page 502 /502.html;
  location /502.html {
        root /errors/;
  }

  listen 80;
  listen [::]:80;
  listen 443 ssl;
  listen [::]:443 ssl;
  server_name 4get.sudovanilla.org;
  
  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-44/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-44/privkey.pem;
  
  # Asset Caching
  include conf.d/include/assets.conf;
  
  # Block Exploits
  include conf.d/include/block-exploits.conf;
  
  # Force SSL
  include conf.d/include/force-ssl.conf;
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_http_version 1.1;


  access_log /data/logs/proxy-host-67_access.log proxy;
  error_log /data/logs/proxy-host-67_error.log warn;

  location / {    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    

    # Proxy!
    include conf.d/include/proxy.conf;
  }

  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

![image](/attachments/e720e30f-c61d-41e3-8981-d1edf88db581) When 4get is on my NGINX proxy(NGINX Proxy Manager), I get a blocked error. This works fine in the local IP. The Docker Compose file is setup like this via Dockge: ```yml services: fourget: image: quay.io/sudovanilla/4get-arm64:latest restart: always ports: - 5901:80 environment: - FOURGET_VERSION=6 - FOURGET_SERVER_NAME=4get.sudovanilla.org - FOURGET_PROTO=http volumes: - /sudovanilla/docker/volumes/4get/banners:/var/www/html/4get/banner - /sudovanilla/docker/volumes/4get/certs:/etc/4get/certs - /sudovanilla/docker/volumes/4get/captcha:/var/www/html/4get/data/captcha networks: dockge_default: external: true ``` > Docker Image is up to date as of May 23rd, 2024. NGINX Proxy Manager generated: ```yml # ------------------------------------------------------------ # 4get.sudovanilla.org # ------------------------------------------------------------ map $scheme $hsts_header { https "max-age=63072000; preload"; } server { set $forward_scheme http; set $server "192.168.1.175"; set $port 6258; # Error Page error_page 404 /404.html; location /404.html { root /errors/; } error_page 502 /502.html; location /502.html { root /errors/; } listen 80; listen [::]:80; listen 443 ssl; listen [::]:443 ssl; server_name 4get.sudovanilla.org; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-44/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-44/privkey.pem; # Asset Caching include conf.d/include/assets.conf; # Block Exploits include conf.d/include/block-exploits.conf; # Force SSL include conf.d/include/force-ssl.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; access_log /data/logs/proxy-host-67_access.log proxy; error_log /data/logs/proxy-host-67_error.log warn; location / { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } ```

image.png

632 KiB

lolcat commented

2024-05-23 22:25:54 -04:00

#10

:)

https://git.lolcat.ca/lolcat/4get/issues/10 :)

👍 1 ❤️ 1

lolcat closed this issue

2024-05-23 22:25:54 -04:00

Sign in to join this conversation.