So today I thought there was some sort of issue with Couchpatato.... it was not couchpatato.

 

What happens is that every container doesnt seem to do any HTTP(S) or SSL requests. In the beginning I thought it might be the template or something. But after I launched a few other containers, which did also not work properly, i found out that none of my docker containers are able to work with HTTPS. All the containers gives errors about connections that time out or are refused because of HTTPS. I also asked it on reddit. There people suggested I should ask Limetech.

 

Is it because I am new to unraid and currently on the trial version (would be odd).

Is something missing on the host machine (unraid).

Is it because something is wrong with my docker containers?

 

This happens if I bridge the network (to get an individual IP from my router) but also happens if I let the container have the same IP as my unraid.

 

Thanks for help in advance!

I now see that all the time in all the docker containers are off....

Time didnt fix it

I'm not really clear what you are trying to do? Unraid does not reverse proxy the containers, so if you want containers to use SSL they would have to be setup individually.

THe problem is solved by now.

 

To clearify, I was try to run a container, that needs to retrieve an RRS feed. So the container needs to connect to an HTTPS site. It's not that I was looking for securing the container. But the container needed to connect to an HTTPS site. This wasn't possible in any of my containers.

 

I'am not sure what eventually the exact problem was. But I do have some clues. When I installed unRAID on my system. The system connected on eth1. I had working internet on my system. But after I restarted for the second time I couldn't connect anymore to my unRAID system. Hooked up a monitor and saw that everything booted. But I also saw "IPV4: not set". Which I had set static. Just to get the USB out, and reset the network.cfg. Found out unRAID was trying to look to eth0 all the time. (which wasnt connected). So filled out the network.cfg and reconnected everything.  Nothing changed... unless. My docker containers. So I am assuming here, that some thing went wrong with the network configuration on unRAID.

 

I am just not quite sure what. As everything had internet (was also able to download docker templates for example) and could connect to HTTP sites from docker. So I thing the network adapters used for docker were routed at some point to eth0 (as that is the first physical NIC). But wasnt connected. Then its logically that I see a timeout.... and a message "no route to host" when I google.com inside the container.

 

I think I now was able to make the problem clear.