Assets dont display if RasPi unable to access internet

Hi all. We have installed Anthias onto Raspberry Bullseye and connected to the internet it works fine.
Now we have to run it on our internal company network that does not have internet access, except via proxy. The system boots but hangs eventually giving some access error messages.
Is there a way to disable the need to access the internet ?
Failing that, is there a way to make it work through a proxy ?

Thanks
Hardy

@hardy, will you be able to provide the error messages?
You can configure the proxy settings similar to how you configure the proxy settings on a Linux machine.
I haven’t looked at it closely, but here are some reference/s that could keep you going:

ok. I have tried to config the proxy using raspi-config, and then in the /etc/environment file
The env file at least allows wget to work through the proxy. But our console screen is still blank.
Following also tips from here: Can’t Get Screenly to Start - Anthias - Anthias Forum I can see some logs using journalctl.

Apr 23 14:07:15 vnrp-ras1 systemd[1]: screenly-host-agent.service: Scheduled restart job, restart counter is at 31.
Apr 23 14:07:15 vnrp-ras1 systemd[1]: Stopped Screenly Host Agent.
Apr 23 14:07:15 vnrp-ras1 systemd[1]: Started Screenly Host Agent.
Apr 23 14:07:16 vnrp-ras1 python3[1043]: INFO:root:Connecting to redis…
Apr 23 14:07:16 vnrp-ras1 python3[1043]: Traceback (most recent call last):
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 559, in connect
Apr 23 14:07:16 vnrp-ras1 python3[1043]: sock = self._connect()
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 615, in _connect
Apr 23 14:07:16 vnrp-ras1 python3[1043]: raise err
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 603, in _connect
Apr 23 14:07:16 vnrp-ras1 python3[1043]: sock.connect(socket_address)
Apr 23 14:07:16 vnrp-ras1 python3[1043]: ConnectionRefusedError: [Errno 111] Connection refused
Apr 23 14:07:16 vnrp-ras1 python3[1043]: During handling of the above exception, another exception occurred:
Apr 23 14:07:16 vnrp-ras1 python3[1043]: Traceback (most recent call last):
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/home/hvn/screenly/host_agent.py”, line 53, in
Apr 23 14:07:16 vnrp-ras1 python3[1043]: subscriber_loop()
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/home/hvn/screenly/host_agent.py”, line 42, in subscriber_loop
Apr 23 14:07:16 vnrp-ras1 python3[1043]: pubsub.subscribe(CHANNEL_NAME)
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/client.py”, line 3580, in subscribe
Apr 23 14:07:16 vnrp-ras1 python3[1043]: ret_val = self.execute_command(‘SUBSCRIBE’, *iterkeys(new_channels))
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/client.py”, line 3466, in execute_command
Apr 23 14:07:16 vnrp-ras1 python3[1043]: self.connection = self.connection_pool.get_connection(
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 1192, in get_connection
Apr 23 14:07:16 vnrp-ras1 python3[1043]: connection.connect()
Apr 23 14:07:16 vnrp-ras1 python3[1043]: File “/usr/lib/python3/dist-packages/redis/connection.py”, line 563, in connect
Apr 23 14:07:16 vnrp-ras1 python3[1043]: raise ConnectionError(self._error_message(e))
Apr 23 14:07:16 vnrp-ras1 python3[1043]: redis.exceptions.ConnectionError: Error 111 connecting to 127.0.0.1:6379. Connection refused.
Apr 23 14:07:16 vnrp-ras1 systemd[1]: screenly-host-agent.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 14:07:16 vnrp-ras1 systemd[1]: screenly-host-agent.service: Failed with result ‘exit-code’.

A very quick look into docker (that I also no knowthing about), docker ps command lists nothing.
Dont know if this is any help, but I’m looking forward to some advice.

Thank you

So, I also tried the rebuild on the above mentioned post. (./screenly/bin/upgrade_containers.sh)
This fails with DNS lookups - expected with a proxy setup. So something on the docker is not observing the proxy config.

~ $ ./screenly/bin/upgrade_containers.sh
WARN[0000] /home/hvn/screenly/docker-compose.yml: version is obsolete
[+] Pulling 7/7
! anthias-celery Warning Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on 10.8.132.253:53: server misbehaving 5.3s
(and many more like this - but I can’t paste cos I’m limited to posting 2 links)

If you’re having trouble with Docker not acknowledging the proxy settings, this documentation might help: Configure Docker to use a proxy server | Docker Docs.

ok, thank you. I did find that and am working on this one.
Would be much nicer though to switch it off. I mean why once we have a running system do we need to have internet access at all ?
Can this update check or whatever it is be disabled ?

ok. So we got this working. A few things required.

  • Setup the proxy with authentication using raspi-config in the advanced settings. Set all proxies to http://userid:passwd@proxyip:port
    Also setup NTP to use an internal NTP server. (update the timesyncd.conf file)
    Then we run the screenly base install with
    bash <(curl -sL https://install-ose.srly.io)
    This should get docker installed but it wont finish due to proxy.
    So after a reboot, setup the docker proxy settings using your link above (adding the same setting for proxy as above)
    Then we can get docker to install/update the screenly with
    ./screenly/bin/upgrade_containers.sh
    A final reboot should see it working.
    Hope that helps someone else.
    Thanks for your help nicomiguelino
1 Like