nginx-proxy / nginx-proxy/nginx-proxy
Can GET from Google Chrome Browser but not from Firefox Browser or curl or wget
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
Step to reproduce
File system
.
├── certs/
├── docker-compose.yml
├── README.md
└── served_files/
└── index.html (content is: "<head></head><body>Index</body>")
Generate certs
openssl req -x509 \
-newkey rsa:4096 \
-sha256 \
-nodes \
-subj '/CN=localhost' \
-keyout ./certs/subdomain.localhost.key \
-out ./certs/subdomain.localhost.crt
Composition
version: '3.5'
services:
server:
environment:
- VIRTUAL_HOST=subdomain.localhost
- VIRTUAL_PORT=8888
image: rapidoid/rapidoid
volumes:
- ./served_files:/app/static
nginx_proxy:
image: jwilder/nginx-proxy:alpine
ports:
- '80:80'
- '443:443'
volumes:
- /var/run/docker.sock:/tmp/docker.sock:ro
- ./certs:/etc/nginx/certs
Build/run
docker-compose up --build
Results/Troubles
Trying to query https://subdomain.localhost/index.html with :
Google Chrome Browser
After accepting the self signed certificate, Chrome render the index.html file without any trouble.
Firefox Browser
Firefox failure, telling "Server not found".
Curl
Curl failure, telling curl: (6) Could not resolve host: subdomain.localhost
Wget
Wget failure, telling Resolving subdomain.localhost (subdomain.localhost)... failed: Name or service not known. wget: unable to resolve host address ‘subdomain.localhost’
Question
Does someone know what I am doing wrong? I only tested in Chrome until now... what a bad thing this seems to be...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the setup from docker-compose.yml with the nginx-proxy image and the mounted certs directory, then compare hostname resolution and HTTPS behavior in Chrome, Firefox, curl, and wget. Done means identifying whether the failure is in nginx-proxy or the local hostname/DNS setup and recording a verified resolution; the issue names no project source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, nginx
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100