I think my containers are unable to connect to the public internet.

 

I have installed Nextcloud and Pterodactyl. For each of those I've created a custom network (docker network create customname).

 

When I go to nextcloud.domain.com/settings/admin/overview I get this message:

This server has no working internet connection: Multiple endpoints could not be reached.

I never figured how to fix it, so I just use my instance like that for the time being.

This has prevented me from installing community apps, I guess when there is "no working internet connection", the community apps tab is hidden.

 

Now I'm trying to install Pterodactyl panel & node and I follow a blog post tutorial by the T.

I've created the panel, it's reachable by HTTPS (I'm using Nginx Proxy Manager on another PC in the network, it loads succesfully and I'm able to create the node setup there). I've created the correct node config, but when I start the node/wing container it fails and the logs say this:

Error response from Panel: _MissingResponseCode: No error response returned from API endpoint. (HTTP/403)

 

This leads me to think that I've botched some configuration and my docker networks don't have access to the outside internet.

My Unraid instance is not exposed to the internet, I haven't changed anything Docker network related.

 

Any tips on how I can further debug this?

Edited February 29, 20242 yr by Nedevski
clarification

Go to settings and disable your docker and VMs.  Then go into settings network and set that up either with static or DHCP addresses, gateway, DNS.  If that is not where the problem resides, the pros will want to see your diagnostics so they can delve deeper.

Updated DNS Server from 192.168.0.1 to 1.1.1.1, no change.

 

Here are my settings, diagnostics also attached below.

 

unraid-diagnostics-20240302-1052.zip

I just created a Firefox container, both with the default `bridge` network and with a custom one (simply `docker network create firefox`).

 

 

Works with both, websites load, so it has internet.

Should be a Nextcloud container specific issue then I guess.