dockur
Can't access behind Nginx Proxy Manager (NPM)
Operating system
Ubuntu 20.04.6 LTS
Description
Hi, To begin I want to thank you for this amazing feature. What I want to achieve may not be possible.
I can reach from the LAN using the container IP with port (192.168.2.190:8006) I have a 502 Bad Gateway if I use a subdomain and NPM. My subdomain is OK (redirects to my public IP as a lot of others).
NPM config redirects subdomain to my container's IP (192.168.2.190). (I also tried with the server's IP and the windows' IP) RDP connection works well from LAN (on windows IP) and from WAN (port forwarded to 3389 on the windows IP). NPM is able to redirect some other subdomains directly to IPs in my LAN and to other containers by their docker's IP or their names in the same network ("npm_network" - external in each docker compose) .
Can you see any error?
tks Alex
Docker compose
services: windows: image: dockurr/windows container_name: windows environment: #VERSION: "11" LANGUAGE: "French" USERNAME: "" PASSWORD: "*" DHCP: "Y" devices: - /dev/kvm - /dev/vhost-net device_cgroup_rules: - 'c : rwm' cap_add: - NET_ADMIN ports: - 8006:8006 - 3389:3389/tcp - 3389:3389/udp stop_grace_period: 2m volumes: - ./tiny10.iso:/custom.iso - ./datas:/data networks: vlan: ipv4_address: 192.168.2.190 networks: vlan: external: true
Docker log
❯ Starting Windows for Docker v4.04... ❯ For support visit https://github.com/dockur/windows ❯ CPU: Intel Xeon X5650 | RAM: 14/32 GB | DISK: 4726 GB (ext4) | KERNEL: 5.4.0-198...
❯ Booting Windows securely using QEMU v9.1.1... BdsDxe: loading Boot0003 "Windows Boot Manager" from HD(1,GPT,99A2204D-CC56-47C1-B034-5AC78EFA6B8E,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi BdsDxe: starting Boot0003 "Windows Boot Manager" from HD(1,GPT,99A2204D-CC56-47C1-B034-5AC78EFA6B8E,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi ❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
Screenshots (optional)
No response
OK, I managed to make it work using streams but...it's not secured at all ^^ Maybe it's not a good idea...
OK, I managed to make it work using streams but...it's not secured at all ^^ Maybe it's not a good idea...
How did you exactly manage t get it working?
OK, I managed to make it work using streams but...it's not secured at all ^^ Maybe it's not a good idea...
How did you exactly manage t get it working?
Hi,
I used the stream in NPM :
But this method makes your access totally opened so not a good idea...
@acwebdesign This is now implemented recently, you can now set:
environment:
USER: "admin"
PASS: "123"
to set authentication for the VNC website.