oicydwa

Members
  • Posts

    10
  • Joined

  • Last visited

oicydwa's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. As a point of fact though.... whenever I put in the above command it spun up the container and everything worked as expected (except I didn't install mariadb yet) I did the same for your container docker run -d --network br0 --ip=10.1.0.7 -p 80:8080 -p 81:8181 -p 443:4443 -v /docker/appdata/nginx-proxy-manager:/config --name NginxProxy jlesage/nginx-proxy-manager and your container forces 8080, 8181, and 4443.... So in the end, my biggest beef is with unraid's diminished support for macvlan, but also in part your container forcing those ports externally
  2. After I configure the macvlan interface, which took me almost 4 hours to figure out (I have a youtube video to prove it under this same name) all I do is run And I just realized why this one looks differently. Apparently someone else has a docker image of this project and I used it on my fedora docker. Yours is the only one in Unraid apps. docker run -d --network br0 --ip=10.1.0.7 -p 80:80 -p 81:81 -p 443:443 -v /home/user/npm/config.json:/app/config/production.json -v /home/user/npm/data:/data -v /home/user/npm/letsencrypt:/etc/letsencrypt --name NginxProxyManager jc21/nginx-proxy-manager:2 Regardless, It won't work either because of Unraid's limitation on configuring ports for macvlan. I have done some testing and apparently if I change the adapter to br0, I completely lose the ability to configure the ports. Which seems really dumb to me! I don't understand why they would even have macvlan as an option if you can't even configure the container at that point?!
  3. Yes. I did everything commandline, as docker cannot assign macvlan IP's and ports through portainer at all. Seems almost like docker doesn't want people using macvlan, and that doesn't make sense to me. I don't understand how 'bridge' can be called that, when it doesn't bridge to an actual device. I don't understand what benefit there is to virtualizing, if everything is only going to be accessible through that one IP. It boggles my mind. The more I research how to overcome this issue, the more I want to ditch unraid. It's go so much going for it that I love, but this one issue is a big one for me. Don't worry about it anymore. I think I'm going to just put fedora on a VM and put docker in it. Just irritates me. Thanks for your help though. NPM is a great software, I'm just frustrated with the lack of configuration for macvlan.
  4. I know how macvlan works. I just had esxi installed with docker running on fedora and all my containers were setup for macvlan. Everything was working fine, once I figured out how to do what I wanted it to do. Even had NginxProxyManager setup. However, I don't understand why the external port cannot be changed on a macvlan connection with some containers like this one on unraid. In order to run this proxy manager, I am forced to use non standard http and https ports or risk port conflicts, and standard http and https ports on this one container are the most crucial because everything else I can just proxy. However when I was running it in docker on fedora I was able to adjust the external ports just fine. I don't understand how that functionality is lost simply because of the platform I'm running it on?! <edit> As for changing the ports means changing the container, i disagree. I only want to change the external ports.
  5. I know how macvlan works. I just had esxi installed with docker running on fedora and all my containers were setup for macvlan. Everything was working fine, once I figured out how to do what I wanted it to do. Even had NginxProxyManager setup. However, I don't understand why the external port cannot be changed on a macvlan connection with some containers like this one on unraid. In order to run this proxy manager, I am forced to use non standard http and https ports or risk port conflicts, and standard http and https ports on this one container are the most crucial because everything else I can just proxy. However when I was running it in docker on fedora I was able to adjust the external ports just fine. I don't understand how that functionality is lost simply because of the platform I'm running it on?!
  6. I'm fairly certain I mentioned in a previous post that I'm using interface br0. But why would this make a difference? It is a bridged interface.
  7. That's not the problem....... I stated in my original post that everything works fine on the default ports. The problem is I cannot change the ports. When I change the host side of the port settings, it will not adjust accordingly. So.... when I change host port 8080 to 80, it is still listening on port 8080. When I open a browser and go to <ip address>:80 it does not work, but I still have to go to <ip address>:8080. This will not work for me, as I need this for internal proxying through my dns. My dns cannot tell the client 'oh by the way, you have to proxy this on port 8080'
  8. I kinda figured with all the stuff I was doing that it was a no-brainer that I of course tried that first. And I know it's not a port conflict, as I'm using br0 a true bridged interface to give it an IP on my physical network. The issue is that changing the configuration doesn't have any effect on the container. I changed the port numbers every which way I could think of, and nothing worked.
  9. So I am unable to get this addon to change used port on unraid. The container from the apps tab is requiring ports 8080/8181/4443 and I need them to be on the regular ports as I want to use this inside my network as opposed to accessing through my gateway. So I have no way to forward the ports. I have tried everything I can think of to make this change ports. Admittedly this is not the first app I have had this issue with, but this one is the most important one. I can usually work around other ports not wanting to change because this one is suppose to help me circumvent having to remember all the ports. Basically, I've configured all the ports with the default, and it works fine. I've deleted all the configs and tried adjusting the ports. They don't adjust and everything works on the default ports listed above. I deleted the default ports and assign the ports parameter manually for 80/81/443 and nothing changed. I then attempt to create those ports using the docker command that runs to start this container, assigning the ports as environment variables instead of port. This also had no effect. I then deleted all port configuration from the page, and it STILL assigned default values listed above. Every time I start anew by deleting the old config directory and trying again. At this point I'm pulling my hair out. So next I dropped to (unraid) command line and ran the docker run command to spin up this container (both my way without all the environment variables, and then the way the original command showed, but changing the ports) and it still used the default ports listed above.. I then went into docker exec into the container and manually adjusted the /etc/nginx/conf.d/default.conf, and nginx attemps to listen on that port, but it's unable to for permissions reasons, despite giving the container admin privileges. No matter what I do, I cannot get this container listening on ports 80/81/443.. Any help at this point would be greatly appreciated. This application has a beautiful UI and it's so simple to use. Thanks