The login page at localhost:8080 can't be reached
See original GitHub issueI followed the Installation instructions, but after running the docker-compose up -d
command, I get a “connection was reset” error in chrome, and don’t see the login page.
The output of the docker-compose up -d
command was:
Creating network "cvat_default" with the default driver
Creating cvat_db ... done
Creating cvat_redis ... done
Creating cvat ... done
And docker ps
outputs:
CONTAINER ID | IMAGE | COMMAND | CREATED | STATUS | PORTS | NAMES |
---|---|---|---|---|---|---|
ec26a5065b07 | cvat | “/usr/bin/supervisord” | 25 minutes ago | Up 25 minutes | 0.0.0.0:8080->8080/tcp, 8443/tcp | cvat |
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Localhost Refused to Connect Error: 5 Confirmed Ways to Fix It
Localhost refused to connect error can be caused by an incorrectly configured port, insufficient permissions, or an inoperative web server.
Read more >Localhost Can't be Reached, Refused to Connect on a Browser
If you are getting this error on your browser when you try to connect to localhost via browser, all you need to do...
Read more >Chrome cannot connect to http://localhost:8080 but http://127.0 ...
Using Chrome (version 58), I can successfully connect to http://127.0.0.1:8080 , but I can't connect to http://localhost:8080 - it gives me ERR ...
Read more >Localhost Refused to Connect - How to Fix the Error
1. First, stop all instances running in WAMP with the End Task button. · 2. Then, open the httpd. · 3. Locate the...
Read more >Localhost:8080 - Site can't be reached - openHAB Community
I installed the latest OpenHab on an RPI4, standalone, connected with ethernet to my router. I did login directly to the PI (connected...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
1.docker-compose down 2.docker-compose up -d fixed the problem for me. Thanks!
ooh I start it successfully again when I use the command:1.docker-compose down 2.docker-compose up -d