openwisp / docker-openwisp

OpenWISP in docker. For production usage we recommend using the ansible-openwisp2 role.
https://openwisp.io/docs/dev/docker/
BSD 3-Clause "New" or "Revised" License
149 stars 75 forks source link

[error] host not found in upstream "radius" in /etc/nginx/conf.d/radius.https.conf #248

Closed eltionb closed 1 month ago

eltionb commented 2 years ago

Hello

I am getting this error on nginx container after a fresh install. Installed using auto-install.sh [emerg] 39#39: host not found in upstream "radius" in /etc/nginx/conf.d/radius.https.conf:71

I did inspect docker file but cant find radius specified as a hostname anywhere. Anyone else has any idea?

OS: Ubuntu Server 20.04.4

nemesifier commented 2 years ago

@eltionb try again with the edge images here: https://gitlab.com/openwisp/docker-openwisp/container_registry

systemcrash commented 1 year ago

Would be great to get this into 'latest', ...

benedikt-bartscher commented 1 year ago

same error here, even with edge images

jrventer commented 1 year ago

This seems to symptom of the init script for nginx requiring the NGINX_SERVER_NAME_HASH_BUCKET=32 to be increased. If you add NGINX_SERVER_NAME_HASH_BUCKET=64 in your .env file it seems to fix this issue.

Think the default value in the .env file should be updated.

fuomag9 commented 1 year ago

The issue is still present

nemesifier commented 1 year ago

I cannot replicate this issue nor find anywhere in the code where radius.https.conf is created, this was an old file.

If anyone finds it in the code please send a patch.

Here's all the occurrences of the word "radius" in the actual codebase: https://github.com/search?q=repo%3Aopenwisp%2Fdocker-openwisp%20radius&type=code

doreks commented 1 year ago

same issue here. I added into .env file line NGINX_SERVER_NAME_HASH_BUCKET=64 but the error did not desappear

nginx: [emerg] host not found in upstream "radius" in /etc/nginx/conf.d/radius.https.conf:71 2023/07/20 18:28:02 [emerg] 39#39: host not found in upstream "radius" in /etc/nginx/conf.d/radius.https.conf:71

doreks commented 1 year ago

hi, !

i have fixed the issue deploying edge docker https://groups.google.com/g/openwisp/c/s4XQ2IOdUTk?pli=1

focher commented 11 months ago

I have deployed using the edge version and still see this error. As the container keeps restarting due to the error, it's not even possible to connect to the container and diagnose the issue. Anyone have ideas?

focher commented 7 months ago

Just posting back that I did resolve the error by changing the reference in the docker-compose.yml file from "freeradius" to "radius". It looks like that error message is just being unable to resolve "radius" to the running container.

nemesifier commented 1 month ago

Should be fixed on the latest master, feel free to reopen if that's not the case.