Nginx doesn't start

[codedevian]

Expected behavior

Nginx container to fully start

Actual behavior

Nginx stops with the following error
2026/02/26 15:19:21 [emerg] 1#1: host not found in upstream "feed-key:3000" in /etc/nginx/conf.d/default.conf:6 nginx: [emerg] host not found in upstream "feed-key:3000" in /etc/nginx/conf.d/default.conf:6

Steps to reproduce

I've just used the latest compose.yaml file which includes the changes to use ngix #614 .
If I open default.conf.template and remove the feed-key upstream and location nginx then starts fine.

[bjoernricks]

For reference https://forum.greenbone.net/t/feed-key-not-found/22124

[ch-sgr]

If I open default.conf.template and remove the feed-key upstream and location nginx then starts fine.

I had to set the nginx config environment variable to 0 for the gvm-config service, too, for this to work.

[bjoernricks]

A fix will require an update for the compose file and a new version of the gvm-config container image. Both are nearly ready in the linked PR drafts. It is likely that both PRs will be finished on next Monday.

[srmo]

Same problem for me. I tried with the new compose yaml from #617 and the error is gone, but now a curl gives conenctions reset errors for non-tls and SSL errors for the tls calls (additionally, only port 9392 is mapped). I didn't incorporate any changes from greenbone/greenbone-container-images#62

It may be as well something stupid I'm doing, so, I'll just wait until both are merged and the new images are published to start with a deterministic setup

[bjoernricks]

but now a curl gives conenctions reset errors for non-tls and SSL errors for the tls calls (additionally, only port 9392 is mapped)

What do you mean by that?

The new compose file includes a https by default setup now and creates a self signed certificate. Of course this will generate an issue if you try to call curl against the web interface now, because curl on your host doesn't know anything about the self signed cert.

[sergeymeleschenko]

[bjoernricks]

This should be fixed now. It requires downloading the newest compose file and pulling the latest gvm-config container image (digest is sha256:c6f0d6c1c0d5671a7c5735b44de28ec5715cb741c717da91d931ba7f3efd5058).

[hungcon]

After pulled and re-run container with newest docker-compose file, it works but then im facing this issue. Pls help!!!

[ch-sgr]

I can confirm that it's working now :) Thanks!

[bjoernricks]

@hungcon i don't have clue what you are trying to do. by default the web interface is now only available on https://127.0.0.1.