Jump to content

redQs

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by redQs

  1. Hey Guys,

     

    i read now nearly every post about this subject...

    it still dont want to work for me...
    I got swag as a docker with a custom proxi network for bitwareden, nextcloud and vpn.

     

    i got access to my homeassistant remotlie at ha.xxxx.de:8123

    i dont get it to work with https://
     

    home assistant configuration.yaml:

    http:
      use_x_forwarded_for: true
      trusted_proxies:
        - 192.168.3.210 #unraid ip-adress
        - 172.18.0.2 #swag ip-adress

     

     

    and of corse i renamed the proxy-config file in swag:

    homeassistant.subdomain.conf

    server {
        listen 443 ssl;
        listen [::]:443 ssl;

        server_name ha.*;

        include /config/nginx/ssl.conf;

        client_max_body_size 0;


        location / {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app 192.168.3.10;
            set $upstream_port 8123;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;

        }

        location ~ ^/(api|local|media)/ {
            include /config/nginx/proxy.conf;
            include /config/nginx/resolver.conf;
            set $upstream_app 192.168.3.10;
            set $upstream_port 8123;
            set $upstream_proto http;
            proxy_pass $upstream_proto://$upstream_app:$upstream_port;
        }
    }
     

     

    as i said i can conect remot to ha.xxxx.de:8123
    so the port forwarding is working. 

     

    What could it be?..

     

    thanks for your reading this!

     

  2. 15 hours ago, John_M said:

     

    You're pointing at it!

     

    That utility is the EFI partition mounter and the volumes you're interested in are the bootloader, at the bottom, and the disk that you are in the process of making your system disk, above it. At the point you've reached the Base System has done its job and you don't need it any more.

     

    See the video at timecode 11:18.

     

    oh wow.. you are right..

    i was just confused becaus the 3. disk is missing by me but i dont even need it... 
    realy thank you :D

  3. i got problems with the openvpn-as since i upgradet to 6.7
    I was on network host.

    It works all fine since update.

    I read that i have to change to bridge.

    Than the openvpn Server startes normal.

    The think is i cant connect anymore to my vpn.

    i using port tcp 8080
    Portforworting works.

    i just got the messing:  Transport Error: TCP connect error on "mydomain.de:8080" ([myhomeipadress]:8080/tcp): System/Connection refused

     

    i just test my old linux vm with openvpn.

    There it works normal.

    sad that the docker dont work anymore for me..

×
×
  • Create New...