mrforsythexter

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mrforsythexter

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hmm this is interesting, thanks for the example. the reason i don't normally create a custom network, is that I still want it accessible from the main hosts IP (so the mariadb accessible by other machines on the network) I guess my next next is to test it in this configuration. Thank you! I will feedback / mark solved once tested (maybe a couple days)
  2. Ken-jl, are you saying the docker resolver 127.0.0.11 only works with containers not in bridge mode? I have a proftpd container, configured for mysql authenication. I have a mariadb container, called mariadb. From the proftpd container, I was expecting to be able to dig @127.0.0.11 for mariadb, and get a response back like 172.15.0.3 for example. Is this not how it should work?
  3. I think the title pretty much says it all really. I can ping 127.0.0.11 however if I dig like dig @127.0.0.11 mariadb I get nothing back, it just times out trying to connect to the DNS server. I should mention that all external DNS resolution works and is passed though to my router (when not trying to resolve a local container name directly). This seems like a basic part of Docker, but I am unsure where to look next. At this stage, I am not even sure how the image is being given my hosts DNS, the resolve.conf is empty.
  4. Thanks I have moved to another ombi docker container.
  5. Thank you for coming back, it maybe fixed.. but best I can tell, its not a stable release, so I wont be just checking that, seems to risky to me. Is there a better place for feature requests?
  6. Since allot of us maybe passing traffic through another container, this isn't that helpful. I respect you maybe trying to reduce support request on you guys, however people that are doing this type of configuration are most likley above your basic user. If the WEB-UI doesn't match your base pattern (so someone changes it away from http://[host]:[ip]/ can you please continue to show the menu item.
  7. There is no need to expand the port range in the WEB-UI. For something like freePBX this makes the list of containers hard to use. Please update to just show the range... 0.0.0.0:18000-20000 would be more than fine.
  8. @binhex that is correct, I am starting to think that a reverse proxy might be an easier idea. Not sure if its worth mentioning, but your container is running on the bridge network, not sure if I should have move it to "Custom: br0" and given it an ip on my network.
  9. It seems to be having an issue starting... Getting Stable Version () % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed Unzipping... gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now chmod: cannot access '/app/Ombi/Ombi': No such file or directory s6-applyuidgid: fatal: unable to exec /app/Ombi/Ombi: No such file or directory /start.sh exited 111 any advice?
  10. hi @binhex would have loved that to be the answer, I have checked its loaded using lsmod | grep iptable_mangle iptable_mangle 16384 2 ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangl and completed a reboot, however this is still not working for other containers which have been passed through yours. (added the port to yours, change other container to network none and added extra param --net=container:binhex-delugevpn) I can see that container is using your network (PIA), but can't then get to the webgui of this other container.
  11. This having so many posts has made it hard to find if anyone has answered this before. Great container @binhex, and great support from @SpaceInvaderOne I followed the guides to get this setup and passing other containers through this one, no problem, working great.. apart from external access. I used to be able to access the other containers externally. So lets say I have open port 3579 and it was going to a local container. That was working fine. When I route it through this container, I can access it locally using [IP]:[port], however if I try and access f
  12. Thank you, You are 100% right, something to do with kaspersky, as soon as I disabled, it worked.
  13. I did have add block, however it made no difference, I debuged the open window code to :- openWindow('/webGui/scripts/tail_log&arg1='+log, 'Log for:'+name, 600, 900) The link is.. "/webGui/scripts/tail_log&arg1=libvirt/qemu/CentOS_Transcoder.log" However, this URI doesn't work in a new window either.
  14. Here is my diagnostics if anyone can help. tower-diagnostics-20200704-1727.zip
  15. Sorry I know its not, been fighting a VM GPU passthough, and not having the logs on hand, doesn't help.. this comment didn't help anyone, was getting to my witts end. This is in the latest firefox and chrome, unraid 6.8.3 Diagnostics attached ( I will add to my other post in the hopes that someone can help there as well) tower-diagnostics-20200704-1727.zip