Unable to make this work. Website doesn't open.

[wouldntyouknow]

Describe the bug

When I try to open this on my docker instance's IP address and the assigned port nothing is opening. After a little while I am getting a "This site can’t be reached" error. The port is free, tried to play around with that but it shouldn't have an impact, everything else works. I really don't understand this as this is a really really basic compose setup.
Here is my compose file:

services:
  it-tools:
    container_name: it-tools
    image: ghcr.io/sharevb/it-tools:nightly
    pull_policy: always
    restart: unless-stopped
    ports:
      - 8820:80

This is all I see in the logs of the container:

/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2025/01/31 23:52:27 [notice] 1#1: using the "epoll" event method
2025/01/31 23:52:27 [notice] 1#1: nginx/1.26.2
2025/01/31 23:52:27 [notice] 1#1: built by gcc 13.2.1 20240309 (Alpine 13.2.1_git20240309) 
2025/01/31 23:52:27 [notice] 1#1: OS: Linux 6.11.11-1-pve
2025/01/31 23:52:27 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1024:524288
2025/01/31 23:52:27 [notice] 1#1: start worker processes
2025/01/31 23:52:27 [notice] 1#1: start worker process 29
2025/01/31 23:52:27 [notice] 1#1: start worker process 30
2025/01/31 23:52:27 [notice] 1#1: start worker process 31
2025/01/31 23:52:27 [notice] 1#1: start worker process 32

Any ideas what might be wrong? What to check?

What happened?

N/A

System information

N/A

Where did you encounter the bug?

Public app (it-tools.tech)

[Tyree]

Have you tried the original it tools repo that this is forked from? I'm curious if the problem exists with both for you.

I've used both versions and never had a problem.

[wouldntyouknow]

Have you tried the original it tools repo that this is forked from? I'm curious if the problem exists with both for you.

I've used both versions and never had a problem.

I actually have. Started with the original repo and it didn't work, afterwards I tried this fork and it didn't work either.

[Tyree]

I actually have. Started with the original repo and it didn't work, afterwards I tried this fork and it didn't work either.

Okay. Figured that might be the case. I don't think @sharevb changed any of the base setup, just added some of the requested tool PRs since development on the original repo slowed.
Might be best to post the issue there as well to see if the original developer can shed some light on things.

When I have access to my server I will check my logs to compare then to yoursv and see if anything sticks out.

[sharevb]

Hi @Tyree and @wouldntyouknow, I effectively only integrated many new tools.
By the way, I just tested your compose file with a local docker desktop + WSL, and http://localhost:8820 serves correctly it-tools.
May be a problem of firewall or docker configuration ?
Also, original project has some opened issues related to reverse proxy serving : https://github.com/CorentinTh/it-tools/issues?q=is%3Aissue%20state%3Aopen%20nginx

[wouldntyouknow]

Hi @sharevb
Yeah, I am not even at reverse proxy yet, have seen that :)
That's the strange thing, I don't even know where to start. The thing is, I have many other containers like it-tools, being a simple deplyoment, one port, a volume, that's it basically. FreshRSS, SearXNG, Guacamole come to mind. They all work. If it would be firewall or a docker config, I would assume they wouldn't work either. But they do. So I am just stumped :)
Will go to the original repo and ask as well I guess...
But by the way, great fork, would prefer using this repo.

[wouldntyouknow]

Okay, just so you know - I restored a docker backup from 5 days ago and deployed it-tools from compose again. It works now! Looks like something got b0rked somehow in my docker instance...

Update: so I restored docker, installed it-tools, worked, updated docker and docker compose - dead again, this time even my reverse proxy died. There is this update as of 01.31 for docker/compose that seems to kill it for me. If I am not upgrading, everything works fine.

[sharevb]

Hi @wouldntyouknow, thanks for all these information and good to know.