Monotlithic and DNS containers hanging on starting supervisord

[device443]

Hi,

I am using unraid and I have the DNS container and monolithic containers set to different IP's, but the containers hang on starting supervisord and never go any further than this.

I have left them running for over an hour and the same thing happens.

I have also tried running them on 2 different computers and this still happens.

I've attached the container log below.

Thank you in advance for your help.

---

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
}

Finished including /etc/nginx/sites-enabled/10_generic.conf

Including /etc/nginx/sites-enabled/20_upstream.conf

Upstream server to proxy and handle inconsistent 302 redirects

All cache traffic is passed through this proxy to allow rewriting of redirects without caching

This is particularly important for sony / ps5 as upstreams redirect between them which confuses slice map on caching

server {

Internal bind on 3128, this should not be externally mapped

listen localhost:3128 reuseport;

No access_log tracking as all requests to this instance are already logged through monolithic

access_log /data/logs/upstream-access.log cachelog;

error_log /data/logs/upstream-error.log;

Including /etc/nginx/sites-available/upstream.conf.d/10_resolver.conf

resolver 8.8.8.8 8.8.4.4 ipv6=off;

Finished including /etc/nginx/sites-available/upstream.conf.d/10_resolver.conf

Including /etc/nginx/sites-available/upstream.conf.d/20_tracking.conf

Header to track if resolved from upstream or 302 redirect

set $orig_loc 'upstream';

Finished including /etc/nginx/sites-available/upstream.conf.d/20_tracking.conf

Including /etc/nginx/sites-available/upstream.conf.d/30_primary_proxy.conf

Proxy all requests to upstream

location / {

Simple proxy the request

proxy_pass http://$host$request_uri;

Catch the errors to process the redirects

proxy_intercept_errors on;
error_page 301 302 307 = @upstream_redirect;
}

Finished including /etc/nginx/sites-available/upstream.conf.d/30_primary_proxy.conf

Including /etc/nginx/sites-available/upstream.conf.d/40_redirect_proxy.conf

Special location block to handle 302 redirects

location @upstream_redirect {

Upstream_http_location contains the Location: redirection from the upstream server

set $saved_upstream_location '$upstream_http_location';

Set debug header

set $orig_loc 'upstream-302';

Pass to proxy and reproxy the request

proxy_pass $saved_upstream_location;
}

Finished including /etc/nginx/sites-available/upstream.conf.d/40_redirect_proxy.conf

}

Finished including /etc/nginx/sites-enabled/20_upstream.conf

Including /etc/nginx/sites-enabled/30_metrics.conf

Metrics endpoint

server {
listen 8080 reuseport;

location = /nginx_status {
stub_status on;
access_log off;
}
}

Finished including /etc/nginx/sites-enabled/30_metrics.conf

}

stream {

Including /etc/nginx/stream.d/log_format.conf

log_format stream_basic '$remote_addr [$time_local] $protocol $status $ssl_preread_server_name $bytes_sent $bytes_received $session_time';

Finished including /etc/nginx/stream.d/log_format.conf

Including /etc/nginx/stream-enabled/10_sni.conf

server {
listen 443;
resolver 8.8.8.8 8.8.4.4 ipv6=off;
proxy_pass $ssl_preread_server_name:443;
ssl_preread on;

access_log /data/logs/stream-access.log stream_basic;
error_log /data/logs/stream-error.log;
}

Finished including /etc/nginx/stream-enabled/10_sni.conf

}

Finished including /etc/nginx/nginx.conf

Checking nginx config
Config check successful
Starting Supervisord

[OnesoftQwQ]

The same problem occurred on my server. It got stuck at "Starting" for about an hour and is still not progressing.

[tommytech96]

Getting the same in TrueNAS Scale ‘App ‘

[ItsMeAndeh]

I had this working on Unraid previously, recently had a hardware issue and changed my motherboard and am rebuilding the dockers etc from scratch and seem to be experiencing the same issue.

[sigmabeta]

I just tried to put up this container on my Fedora laptop and saw the same issue. Just gets stuck at Starting Supervisord.

Since there's no way to rollback to a previous version of the docker images, that makes it so functionally there's no way for a new user to start using lancache :(

[ItsMeAndeh]

I actually had a brief try looking into this to see if it was a “user error” and I’d done something wrong but if I point my desktop at the LanCache docker IP rather than the LanCacheDNS docker IP I got full network traffic and full downloads so I think at least for me it may be the DNS docker that’s not fully functioning but I’ve not had chance to look into that yet

Might be worth you trying the same to determine if it’s the Cache or DNS side of things having trouble.

[ItsMeAndeh]

Oh also both dockers logs are showing Starting Supervisord as the last message.

[Hannsre]

Do you actually have an issue with lancache not working?
These logs are perfectly normal and indicate no problem whatsoever. Check your container health and it'll most likely be up or running, whatever it is called on your system.

If you still have issues, check the logs of lancache itself, they'll belocated in the lancache root - I don't use the unraid/truenas apps, so I don't know where to look specifically for those two setups. But I'm sure they have some way of accessing the logs.

[sojab0on]

same here
host is running ubuntu server 22.04 with docker and docker-compose installed trough teh official guides

Ik docker ps booth containers show up with a timof 10 minutes
but in logs booth lancachenet/lancache-dns:latest and lancachenet/monolithic:latest show Starting Supervisord

it was a clean docker build up used the standard guide from the website

git clone https://github.com/lancachenet/docker-compose lancache

cd lancache

nano .env

sudo docker compose up -d

=> Configure your router to serve ONLY lancache-dns

Only changed the ip and cache folder in de .env
as stated in the guide

only change in network i have is a adguard network wide dns server running on port 53 so i sete the port to 54 so the container can start

even retried to run the commands on a clean ubuntu mashine still same

can seen to figure out why

[Hannsre]

but in logs booth lancachenet/lancache-dns:latest and lancachenet/monolithic:latest show Starting Supervisord

This is normal and the container is fully started.

[drKenderRendel]

The problem is, after fully installing it, my docker will refuse to give me anything but HTTP 508 Loop Error. I can bring up the nginx welcome page, but no port 80 or 443 giving me a clear lifeline. Steam considers it "offline" and it doesn't seem to let me download games. I think the DNS container works fine - I tried moving the DNS to a completely separate PC and still couldn't bring the page up. The DNS should work since even if it is the only NS I set in windows adapter settings, I can browse the web no problem - even after flushdns.

I tried 3 different VMs all having the same result no matter which method I resort to.

[sojab0on]

i gave up on using this because most services are using https delivery and lancache wont cache it even Linux clients for steam use a https delivery methode and steam wil for some reason bypass lancache on the steamdeck and other Linux Systems.
the nginx container has no webinterface running on it its more a proxy as far i saw

[Hannsre]

The problem is, after fully installing it, my docker will refuse to give me anything but HTTP 508 Loop Error. I can bring up the nginx welcome page, but no port 80 or 443 giving me a clear lifeline.

Lancache is a proxy without any kind of interface, hence why you're not seeing anything. This is normal. The 508 loop detected points towards a config issue in your setup, since requests are sent in a never ending loop. Double check your .env that there are no DNS Loops.

i gave up on using this because most services are using https delivery and lancache wont cache it even Linux clients for steam use a https delivery methode and steam wil for some reason bypass lancache on the steamdeck and other Linux Systems.

Steam, and other CDN, will fall back to HTTP once lancache is detected. There is an issue on Linux though, so also affecting the steamdeck in particular, that prevents lancache from being used. You have to enable IPv6 on the client (e.g. steamdeck), but do not assign an IP. So enable, set to manual IP instead of DHCP, leave the IP empty. Then it'll work.

[sojab0on]

for me its also some other services that for some reason wont fallback have had gog and Epic Games just downloading, had a separate gui for lancache setup to see witch clients where using it and only my Windows steam client would do it gog epic and uplay al went directly past it to the https servers from the services them self.
never saw a cache beeing build for games it tries to get from them.
can try to set ipv6 in my deck to see if it goes through it later on

[Hannsre]

I think GOG is HTTPS only, but Epic, uPlay, Xbox, Battle.net and so on should work fine. Epic Games and Battle.net even have Prefill available. You can use it to diagnose issues as well, since it does a lot of checks before running. There's one for steam as well.

The only 2 I remember not working by default are GOG and whatever the EA Games one is called now, I keep forgetting.

[sojab0on]

ea games was called origin but thing they have renamed or are in a rebranding to ea app