Not Working - 404 Error

[TrueCitrus]

I get the following error which looks it can’t find AirConnect. It is showing a 404 error. Any ideas?

[cont-init.d1 10-adduser: exited 0. [cont-init.d] 30-install: executing. --2022-11-25 07:06:29-- https://raw.githubusercontent.com/philippe44/AirConnect/master/bin/airupnp-x86-64 Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.109.133, 185.199.110.133, 185.199.111.133, Connecting to raw.githubusercontent.com (raw.githubusercontent.com) 185.199.109.133| :443... connected. HTTP request sent, awaiting response... 404 Not Found 2022-11-25 07:06:30 ERROR 404: Not Found. --2022-11-25 07:06:30-- https://raw.githubusercontent.com/philippe44/AirConnect/master/bin/aircast-x86-64 Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.109.133, 185.199.110.133, Connecting to raw.githubusercontent.com (raw.githubusercontent.com) |185.199.108.133|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2022-11-25 07:06:30 ERROR 404: Not Found. [cont-init.d] 30-install: exited 0. [cont-init.d] 99-custom-scripts: executing. [custom-init] no custom files found exiting. [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2022-11-25 07:06:30,712 CRIT Supervisor running as root (no user in config file) 2022-11-25 07:06:30,717 INFO supervisord started with id 238 2022-11-25 07:06:31,718 INFO spawnerr: command at '/bin/airupnp-x86-64' is not executable 2022-11-25 07:06:31,718 INFO spawnerr: command at '/bin/aircast-x86-64° is not executable 2022-11-25 07:06:32,719 INFO spawnerr: command at 2022-11-25 07:06:32,720 INFO spawnerr: command '/bin/airupnp-x86-64° is not executable at */bin/aircast-x86-64' is not executable 2022-11-25 07:06:34,722 INFO spawnerr: command at '/bin/airupnp-x86-64° is not executable 2022-11-25 07:06:34,723 INFO spawnerr: command at '/bin/aircast-x86-64° is not executable 2022-11-25 07:06:37,726 INFO spawnerr: command at 2022-11-25 07:06:37,727 INFO gave up: '/bin/airupnp-x86-64° is not executable airupnp-x86-64 entered FATAL state, too many start retries too quickly

[1activegeek]

It would appear you are running an outdated version of the image. Possibly VERY old as I believe even my previous version before recent changes would actually pull the package as part of the image build, vs container start. Can you try pulling the latest image and then re-creating the container?

The issue here based on what I see, is that the old version of my image would pull the actually binary from the author on container start/first run. Recently the author made changes to the naming convention of those binaries, and so this older image won't be able to have the correct binaries inside.

[TrueCitrus]

Thanks for pointing me in the right direction. I think I updated the image now and I don’t get that error anymore but it’s still not working:

[custom-init] No custom files found, skipping.. services-up: info: copying legacy longrun airconnect (no readiness no tification) [ls.io-initl done. 2022-11-27 04:24:19,773 CRIT Supervisor is running as root. Privileg es were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config fi le to avoid this message. 2022-11-27 04:24:19,779 INFO supervisord started with pid 151 2022-11-27 04:24:20,782 INFO spawned: 'aircast-linux-x86 64' with pid 156 2022-11-27 04:24:20,786 INFO spawned: 'airupnp-linux-x86 64' with pid 157 2022-11-27 04:24:21,888 INFO success: aircast-linux-x86 64 entered RU NNING state, process has stayed up for > than 1 seconds (startsecs) 2022-11-27 04:24:21,889 INFO success: airupnp-linux-x86_64 entered RU NNING state, process has stayed up for > than 1 seconds (startsecs) I AA • gnap.local

[1activegeek]

By all accounts, that looks to be operating completely correct. The last line of that log shows a successful process spawning. So the container is running, and it looks to be successful. If you are not seeing the targets on your network, then you are likely looking at a network based problem on your side. Unfortunately I can't help much there, but you can search many of the issues on the original github of the code used here. There are also a few people on here who have opened issues that were documented what their issues were when they solved the network side of things.

[1activegeek]

Stale issue with no updates. Please comment again if there is further troubleshooting needed that relates to the container.