Take a look at this mess.

 

I was used to the port errors, because I'm running a few dockers that all want to use 8080, so I had to move some things around.  

 

But this is way, way, way more errors than I'm used to seeing, and its resulting in a yellow notification ball next to the logs.  Given the plethora of problems I have with this server, seeing yellow gives me mild arrhythmia each time I log in.

 

How to fix?

 

 

 

 

Duplicati and the slave mode:  https://forums.lime-technology.com/topic/57181-real-docker-faq/#comment-564360

 

 

Unifi host and ports not found.  Both related.  The author dictated that the app should run in bridge mode, and you've switched it to host mode

 

Nut.plg  exactly what the description says.  Switch to the version from dmacias

 

All the webUI ones:  You've outright edited the webUI on those templates to directly reference an IP address and port.  No real reason to do that (except maybe if you run Pipework).  Change it back to what its specified by the author.  The reason why is listed in the description.

 

TemplateURL missing:  Hit Apply Fix

11 minutes ago, tucansam said:

I was used to the port errors, because I'm running a few dockers that all want to use 8080

Doesn't matter.  You can have 20 applications that all want to use 8080.  So long as each of them have a unique host port (8081, 8082, whatever), each and every app can still be set internally to use 8080.

Thanks Squid.

 

I've outright edited the webui for all my dockers because when I use the default, I get "about:blank" in the browser URL every time I try to open a GUI on any of them.  If I hard-code the IP/Port, they all work.

Still broken unless I hard-code IP/Port.

And unifi can't see any access point unless its running in Host mode.

Whatever works, works.   FCP highlights what tends to trip people up.