adguard nginx proxy link broke #1

Closed
opened 2023-10-25 21:50:20 -04:00 by sickprodigy · 8 comments
Owner

Adguard isn't able to connect on port 3k from nginx proxy.
Seems to be something with port 80 and how I'm only using port 443. TLS over https. Don't enforce.

Not a major issue, but rather annoying if I'm not local.

Adguard isn't able to connect on port 3k from nginx proxy. Seems to be something with port 80 and how I'm only using port 443. TLS over https. Don't enforce. Not a major issue, but rather annoying if I'm not local.
Author
Owner

Can't use it outside of home network right now anyways. Having issues with https configuration.

and with tons of other people using the DNS server.

So disabled it for everyone outside of local network until I can figure out the method I want to use for it.
I may have it enabled for a few IP's.

Possibly just wireguard in and use it all the time from locally in that position.

Can't use it outside of home network right now anyways. Having issues with https configuration. and with tons of other people using the DNS server. So disabled it for everyone outside of local network until I can figure out the method I want to use for it. I may have it enabled for a few IP's. Possibly just wireguard in and use it all the time from locally in that position.
Author
Owner

The network adguard is connecting to is called 'adguard_homelab'
It's not joining the right network, instead creating a new one.
Trying to change network name to specify specific network. See how it goes.

https://i.imgur.com/TtgysVy.png

idk, looks like it was in the same network, just had a weird label for it.

The network adguard is connecting to is called 'adguard_homelab' It's not joining the right network, instead creating a new one. Trying to change network name to specify specific network. See how it goes. https://i.imgur.com/TtgysVy.png idk, looks like it was in the same network, just had a weird label for it.
Author
Owner

Just remembered the network thing out of nowhere..

This one is working:

networks:    # specify the network 2x. In service, and in this tag area..
  homelab:
    name: homelab      # Networks can also be given a custom name
    external: true      # This option causes compose to join the above network instead of making a _default one
  mcprodnet:
    #enable_ipv6: true
    name: mcprodnet      # We will name the network instead of letting docker do something random
    driver: macvlan      # Making the above network macvlan
    driver_opts:         # driver options to use
      parent: enp3s0     # usually eth0 or eth1 but not always, used enp3s0 and enp4s0, had to delete /var/lib/docker/network/files/local-kv.db because phantom network
    ipam:
      config:
        - subnet: "192.168.86.0/24"    #Basically copy router range
          gateway: "192.168.86.1"      #host will eventually route to router, or just go direct
#        - subnet: "2605:a601:9132:d100:2::/80" # dual subnet ipv6, has to match router subnet unfortunately for external connections like samsung tv
#          gateway: "2605:a601:9132:d100:2:ffff:ffff:ffff"      #this needs to be router(ish)
#    external: true

Had to add:

external: true

to the homelab network so it would join that network instead of creating it's own. Not sure when that got changed. Need to add a git for the whole docker folder i reckon.

Just remembered the network thing out of nowhere.. This one is working: ``` networks: # specify the network 2x. In service, and in this tag area.. homelab: name: homelab # Networks can also be given a custom name external: true # This option causes compose to join the above network instead of making a _default one mcprodnet: #enable_ipv6: true name: mcprodnet # We will name the network instead of letting docker do something random driver: macvlan # Making the above network macvlan driver_opts: # driver options to use parent: enp3s0 # usually eth0 or eth1 but not always, used enp3s0 and enp4s0, had to delete /var/lib/docker/network/files/local-kv.db because phantom network ipam: config: - subnet: "192.168.86.0/24" #Basically copy router range gateway: "192.168.86.1" #host will eventually route to router, or just go direct # - subnet: "2605:a601:9132:d100:2::/80" # dual subnet ipv6, has to match router subnet unfortunately for external connections like samsung tv # gateway: "2605:a601:9132:d100:2:ffff:ffff:ffff" #this needs to be router(ish) # external: true ``` Had to add: ``` external: true ``` to the homelab network so it would join that network instead of creating it's own. Not sure when that got changed. Need to add a git for the whole docker folder i reckon.
Author
Owner

I can't port adguard to 80 and 443 is my current issue. Nginx is taking up those ports. So now I'm curious if I make nginx it's own macvlan if it will separate somehow. I think I may be mistaken because I'm having both containers join the same network. So they will try to take the same port? no, they should each have their own ip on the network so shouldn't be overlapping. Not sure what's going on.

I can't port adguard to 80 and 443 is my current issue. Nginx is taking up those ports. So now I'm curious if I make nginx it's own macvlan if it will separate somehow. I think I may be mistaken because I'm having both containers join the same network. So they will try to take the same port? no, they should each have their own ip on the network so shouldn't be overlapping. Not sure what's going on.
Author
Owner

just can't get the https link to work now. 443 works better than 80, but it still throws an error each new site I visit using it through firefox. Kind of annoying.

just can't get the https link to work now. 443 works better than 80, but it still throws an error each new site I visit using it through firefox. Kind of annoying.
Author
Owner

Alright, for some reason, website rcs1.xyz is showing google trust certificate. Is it cloudflare or my local dns showing this?

Everything appears right in adguard. but that would be more of an nginx issue i think, is it because nginx isn't setup properly?
na gotta be because cloudflare is doing something that looks like it being manipulated. Maybe need some further testing with nginx and open an issue there for it.

Alright, for some reason, website rcs1.xyz is showing google trust certificate. Is it cloudflare or my local dns showing this? Everything appears right in adguard. but that would be more of an nginx issue i think, is it because nginx isn't setup properly? na gotta be because cloudflare is doing something that looks like it being manipulated. Maybe need some further testing with nginx and open an issue there for it.
Author
Owner

Alright, so using cloudflare, you don't quite have your full encryption only. It's your encryption through a tunnel of their encryption. So it looks like a different certificate at the end. Will i need to input this certificate on adguard to get it to work properly? I don't like that idea honestly. then cloudflare can read all my adguard data basically.

With tthat in mind when you have issues locally with encryption it may not show up bc cloudflare is forcing it to work. And then everything appears working when it gets to your server.

Alright, so using cloudflare, you don't quite have your full encryption only. It's your encryption through a tunnel of their encryption. So it looks like a different certificate at the end. Will i need to input this certificate on adguard to get it to work properly? I don't like that idea honestly. then cloudflare can read all my adguard data basically. With tthat in mind when you have issues locally with encryption it may not show up bc cloudflare is forcing it to work. And then everything appears working when it gets to your server.
Author
Owner

disabled proxy services with cloudflare, haven't had issues in awhile now. So must be closed.

disabled proxy services with cloudflare, haven't had issues in awhile now. So must be closed.
Sign in to join this conversation.
No description provided.