vfast

Members
  • Posts

    8
  • Joined

  • Last visited

vfast's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi Guys - is there anyway to define the hostname for the pihole? Seems to generate a random host name each config?
  2. Hi All I was able to resolve my issue and the above article was right. I had to revert back to my cloudkey, perform the DB removal of the AP. Readopt it and then take a new backup across to the docker. I'd still like to know how to perform mongo / DB commands in the docker correctly if someone knows... thanks
  3. Running 5.8.11569 FW on the AP. So dont think it would be that.
  4. Hi Everyone. I'm trying to make the switch over to this docker. Thanks so much for providing it. I have a moderate amount of unifi / ub knowledge and growing set of skill with unraid. Everything has gone fairly well in my moving over to the docker from a cloudkey. I simply restored the backup into the docker and things seemed to move along nicely. However the exception is that I seem to have an AP thats in Adoption limbo. In that it wont complete adoption despite my trying set-informs and reseting the AP to factory defaults(via SSH). The rest of my environment which has additional APs and Switches all adopted in and are functioning well. I have set the controller override settings to the IP of the docker (and I've had that in bridge and host mode). I've even added option 43 to my pfsense dhcp options. I think I found a related support article which describes my issue and a logical process to remove it from the controller db. https://community.ui.com/questions/AP-stuck-in-purgatory/ce5d63b4-c882-415c-bbcc-d00a0089fb8a However I tried these commands from the docker console and they dont seem to work. Can someone point me in the right direction on how to achieve removal of an AP from the controller db in the docker? Or if anyone know what else I should try. Appreciate any help 🙂
  5. Hi guys - thanks for the posts here. Helped me get Paperless running. Working great but for one issue. The time / timezone doesn't seem to be applied. Hence any documents inputed are UTC but I am +10hrs so makes searching a little hard. Any ideas on what the issue is. I run 'date' from console of docker and the timezone is correct but the time is wrong (like it's still UTC).
  6. True. Sorry noob error! Thanks for the reply however!
  7. Hi Guys - my unraid server log is getting spammed with the following: Jul 5 14:18:29 Tower nginx: 2019/07/05 14:18:29 [crit] 6547#6547: *9967 connect() to unix:/var/tmp/NginxProxyManager.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.120, server: , request: "GET /dockerterminal/NginxProxyManager/ws HTTP/1.1", upstream: "http://unix:/var/tmp/NginxProxyManager.sock:/ws", host: "tower.x.net" Jul 5 14:18:39 Tower nginx: 2019/07/05 14:18:39 [crit] 6547#6547: *10010 connect() to unix:/var/tmp/NginxProxyManager.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.120, server: , request: "GET /dockerterminal/NginxProxyManager/ws HTTP/1.1", upstream: "http://unix:/var/tmp/NginxProxyManager.sock:/ws", host: "tower.x.net" Jul 5 14:18:49 Tower nginx: 2019/07/05 14:18:49 [crit] 6547#6547: *10047 connect() to unix:/var/tmp/NginxProxyManager.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.120, server: , request: "GET /dockerterminal/NginxProxyManager/ws HTTP/1.1", upstream: "http://unix:/var/tmp/NginxProxyManager.sock:/ws", host: "tower.x.net" Jul 5 14:18:59 Tower nginx: 2019/07/05 14:18:59 [crit] 6547#6547: *10093 connect() to unix:/var/tmp/NginxProxyManager.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.0.120, server: , request: "GET /dockerterminal/NginxProxyManager/ws HTTP/1.1", upstream: "http://unix:/var/tmp/NginxProxyManager.sock:/ws", host: "tower.x.net" I have removed the NginxProxyManager docker in hope to resolve this but it continues. Could someone please point me to a resolution?